Not concurrently. Cloud Block Storage is not a shared storage offering. You may attach multiple volumes to a single Cloud Server instance, but you may not attach multiple Cloud Servers to a single Cloud Block Storage volume.
Cloud Block Storage: FAQs
Once you have created a volume, you can increase its size using the API by either of two methods:
- Cloning from a source volume to a new larger volume, or
- Creating a new larger volume from an existing volume snapshot.
Alternatively, in order to move to a larger or smaller volume size, you might need to create a new volume of the desired size and then copy your data from the original volume to the new volume. Please note that you will be required to resize your file system when moving to a smaller volume (if supported by your operating system).
When you copy your data within the same data center via the internal ServiceNet network, there is no charge for bandwidth.
No. Cloud Block Storage volumes are available to newer Cloud Servers platforms, but not first-generation Cloud Servers.
You can verify a volume’s capacity and available space using basic system commands available via their Cloud Server operating system:
- In Linux CLI: From a terminal window, run the “df -h” command and note the Size, Used, Avail, and Capacity of the storage volume
- Windows Explorer: Right-click on drive icon and select "Properties," and note Capacity, Free space, and Used space
There is no limit. You may create an unlimited number of Snapshots.
Yes. However at some point the cost benefit of utilizing multiple less expensive SATA volumes in a RAID configuration will be outweighed by the benefit of utilizing a single higher I/O SSD volume. If you want to increase the I/O performance of your storage volumes, we encourage you to use higher performing SSD volumes for increased disk I/O.
Cloud Block Storage is charged by gigabytes of storage used per month, not the IOPs, which can be difficult to predict. The price differs for standard volumes, SSD volumes, and snapshots.
Prices vary by region and are detailed on the following pages:
A volume clone is a usable copy of the source volume; it can be attached to a server and used immediately. A volume snapshot cannot be directly used as a volume; you must create a volume from the snapshot and then attach that volume to your server. Snapshots are stored redundantly in Cloud Files. However, creating a volume from a snapshot is a slower process than creating a volume from a clone. If your application is time sensitive, consider using volume cloning.
For instructions on volume cloning, see How to Create a Clone of a Cloud Block Storage Volume for instructions on volume cloning.
Although you cannot change the type of a Cloud Block Storage volume after it has been provisioned, you can create a copy of that volume and switch volume types by using the cloning or snapshot method outlined in the following articles:
You can create a copy of a Cloud Block Storage volume using two methods:
- Cloning Method (Volume-to-volume)
This is direct copy from your existing volume to a new blank volume on another storage node. Volume data is copied directly between CBS storage nodes over our high-speed local storage network. This method is recommended if you want to make quick copies of your volume data and use them immediately after creation.
- Snapshot Method (Volume-to-Snapshot-to-Volume)
This method requires the intermediate step of creating a volume snapshot. You first create snapshot from your existing volume, which gets stored in Cloud Files. Second, you create a new volume using your snapshot as the source. This process requires writing snapshot data in and out of Cloud Files so it can take longer than the Cloning Method. This method is recommended if you don’t require quick access to your copied volumes and want the added durability, and lower price, of having your volume snapshot stored in Cloud Files.
Yes. Using the API, you can rename an existing volume using the cinder rename command to update the display-name of the volume.
Yes. Using the API, you can query the progress of a snapshot creation using the snapshot-show command.
The percentage complete value will show up under the os-extended-snapshot-attributes:progress property.
Yes, you can. After you have attached and mounted your Cloud Block Storage Volume, you can add it to your current Cloud Backup Schedule. Edit the Backup Schedule and browse to the drive letter of your Volume or to individual files on the drive. Save your Schedule as normal.
Rackspace Cloud Block Storage provides persistent block-level storage volumes for use with Rackspace next generation Cloud Servers. Volumes can be created and deleted independently of the Cloud Servers they are attached to. Rackspace Cloud Block Storage customers can create volumes ranging from 100 GB to 1 TB in size and choose from either SATA or SDD volume types.
Cloud Block Storage provides persistent data storage for next generation Cloud Servers. Persistent storage can exist independent of your server, even after the server has been deleted. The local storage bundled with Cloud Servers is ephemeral and exists only as long as the Cloud Server exists. When the server is deleted, so is its local storage.
We recommend that you unmount and detach Cloud Block Storage volumes before deleting the server.
The minimum size for a Cloud Block Storage volume is 50 GB for an SSD volume or 75GB for an SATA volume. The maximum volume size is 1TB.
Depending on your Cloud Server’s operating system, you can have up to a maximum of 14 Cloud Block Storage volumes attached to a single server.
The limit for Volumes and storage is 10 TB total stored or 50 volumes per region (whichever is reached first).
No problem. We'll be happy to accommodate any size storage requests for Cloud Block Storage. Simply ask for an increase to your storage quota via a support request and include the desired storage amount (TBs or volume count), storage type (SATA or SSD), and region (DFW, ORD, IAD, LON, SYD, HKG). Please contact your account team for further details.
Yes. Details regarding the Cloud Block Storage SLA can be found here: http://www.rackspace.com/cloud/legal/sla.
Cloud Block Storage is an excellent option for you if you:
- Want more control over your storage or application infrastructure
- Are looking for a high performance storage option (SSD)
- Would like to add additional storage to your servers without paying for additional compute resources
You might not be a good fit for the Cloud Block Storage service if you:
- Are leveraging First Generation Cloud Servers
- Are not comfortable with low-level system administration tasks, such as installing file systems, mounting and partitioning storage volumes, or installing your own applications on top of a raw storage device
- Are looking for a fully managed storage or database solution
Cloud Block Storage (CBS) is not meant as a direct replacement of any existing Rackspace products (shared or dedicated). CBS allows Rackspace Cloud customers to add “a la carte” storage to their existing next generation Cloud Servers and should be considered a complementary cloud-based storage offering that rounds out our entire storage portfolio.
Cloud Block Storage back-end storage volumes employ a RAID (Redundant Array of Independent Disks) level 10 configuration. RAID 10 provides high availability by combining features of RAID level 0 and RAID level 1 in which data is stripped and mirrored to provide a very high level of reliability and performance.
The hardware RAID level 10 employed by Cloud Block Storage nodes provides protection against disk failures on the storage nodes themselves. However customers are strongly encouraged to implement a RAID level 1 (mirror) configuration across multiple volumes to protect against data loss in the event of a storage node failure.
For your security, the used portions of the physical disk are overwritten with zeroes before the deleted volume's disk space is reallocated to the shared pool of disk resources. At this point, your data cannot be recovered and is not visible to other customers.