Step 4: Add Storage
Q-Cloud Protect AMIs include pre-configured storage to meet minimum operation requirements. You can configure additional storage for an instance on Step 4: Add Storage of the Launch Instance Wizard by increasing the amount of storage allocated to the EBS volume. From this page, you can also review the instance's current storage configuration.
* Although the Step 4: Add Storage page states that you can attach additional EBS volumes to your instance and edit the root volume, we strongly recommend against doing so. See * Although the Step 4: Add Storage page states that you can attach additional EBS volumes to your instance and edit the root volume, we strongly recommend against doing so. See Storage Recommendations for more information. for more information.
The following information provides our recommendations for configuring additional storage for your Q-Cloud Protect instance.
GB versus GiB
Although the Q-Cloud Protect appliance reports measurements in units of MB, GB, and TB, AWS reports measurements in units of MiB, GiB, and TiB. When calculating the EBS volume's storage capacity, you will need to convert measurements between the cloud appliance and AWS interfaces, as appropriate.
To convert GB to GiB, multiply by .93.
GB x .93 = GiB
Do not select the Delete on Termination option. By making sure not to select this option, the volumes will persist if the instance is inadvertently terminated. You can then use the persisting volumes to relaunch the instance.
The static root volume is pre-configured with 320 GiB of Magnetic storage, which contains OS and initial configuration data for the instance. This data does not affect the deduplication storage pool.
We recommend against changing the size or type of the root volume. The root volume does not require any additional storage beyond the amount that has been pre-configured for it.
The data volume is pre-configured with 256 GiBof General Purpose (SSD) for its base configuration. We recommend configuring enough additional storage to accommodate data being replicated to the cloud appliance in the short term plus additional storage capacity for future growth. See Calculate EBS Volume Requirements.
When you configure additional storage, do not add a new EBS volume. Instead, add the storage to the existing EBS volume.
In addition, we recommend against changing the type of EBS volume.
Depending on your storage needs, perform one or both of the following tasks.
- From the Launch Instance Wizard, display Step 4: Add Storage.
- Review the following information about the currently configured storage:
The type of volume, either Root or EBS.
The device name assigned to the volume.
- Root volume device name: /dev/sda1
- EBS volume device name: /dev/sdb
The ID of the EBS snapshot of the volume. See S3, EBS Volumes, and Snapshots.
The currently configured storage size of the volume.
The pre-assigned volume type:
- Magnetic type for the Root volume
- General Purpose (SSD) type for the EBS volume
We do not recommend changing the volume type.
The requested number of I/O operations per second that the volume can support.
Delete on Termination
Do not select this option. By making sure not to select this option, the volumes will persist if the instance is inadvertently terminated. You can then use the persisting volumes to relaunch the instance.
The encryption setting for the volume.
- Click Next: Tag Instance to proceed to the next step. See Step 5: Tag Instance.