Recovering When EBS Volumes Fail
If an EBS volume attached to an instance becomes corrupted or fails, the Q-Cloud Protect appliance enters diagnostics mode and sends an alert to warn you of the issue. You can recover the data in the failed EBS volume by using the volume's EBS snapshots.
- Shut down the Q-Cloud Protect appliance.
- Recover the Q-Cloud Protect instance's failed root (/dev/sda1/) and data volumes (dev/sdf/) by using their associated EBS snapshots to create a new AMI. See Recover the Q-Cloud Protect instance's failed root (/dev/sda1/) and data volumes (dev/sdf/) by using their associated EBS snapshots to create a new AMI. See
Recover failed volumes from EBS snapshots..
- Terminate the original Q-Cloud Protect appliance to release its private IP address. You will re-assign the private IP address to the new Q-Cloud Protect instance. See EC2 Instance Issues and FAQs.
- Launch a new Q-Cloud Protect instance from the AMI containing the recovered data. See Launch a new Q-Cloud Protect instance from the AMI containing the recovered data. See
Launch the recovery instance
- Deploy Q-Cloud Protect from the new instance. See Step 2: Complete the Getting Started Wizard
This newly deployed cloud appliance will use data from the recovered EBS root and data volumes to access the replicated data stored in S3. It will function just as the original Q-Cloud Protect appliance did before entering diagnostics mode. Therefore, you will not need to reconfigure the appliance.
Because the data stored in S3 buckets is used to configure a recovered instance or to failback data to a source appliance, you should not delete S3 buckets associated with your Q-Cloud Protect appliance unless you are completely certain that you no longer need the stored data.
- Delete the corrupted EBS volume. See Delete the corrupted EBS volume. See
Delete a corrupted volume..
- On the EC2 console, select the Elastic Block Store > Snapshots menu to display the Snapshots dashboard.
- Locate the appropriate snapshot generation from which to recover the failed EBS root and data volumes.
- Select the snapshot of the root volume, and select Actions > Create Image to display the Create Image from EBS Snapshot dialog box.
- Populate the Name and Description fields to identify the new AMI that will be created from the snapshots.
- From the Architecture drop-down list, select x86_64.
- In the Root device name field, enter /dev/sda1/.
When you launch the new instance, you will give it the same name as the original instance, which then automatically attaches the root volume to the new instance.
- Leave the RAM disk ID field set to Use default.
- From the Virtualization type drop-down list, select Hardware-assisted virtualization.
- Leave the Kernel ID field set to Use default.
- Populate the Root row of the Block Device Mappings table with the same settings that were used for the original root volume, making sure the Delete on Termination is NOT selected.
- For each EBS data volume to recover, click Add New Volume to display a new Block Device Mappings row.
- In the new Block Device Mappings row, populate the following fields to configure the data volume for the instance:
Enter the ID of the snapshot from which you are recovering the data volume.
Enter the same size as was assigned to the original data volume.
Volume Type Select General Purpose (SSD).
Delete on Termination
Deselect this option.
Select to encrypt the data volume.
- Click Create to create the AMI.
- On the EC2 console, select the Images > AMIs menu to display the AMIs dashboard.
- Select the AMI created from the EBS snapshots, and click Launch to display the Launch Instance Wizard.
- Step through the wizard, making sure to apply ALL settings that were used for the original instance. See Launch .
To continue replication jobs to the new Q-Cloud Protect instance, you must assign it the original instance's IP address:
- After launching the new instance, deploy Q-Cloud Protect. See Deploy.
- In the EC2 console's Volumes dashboard, select the volume to delete.
- Click the Actions button, and select Delete Volume.
- At the prompt, confirm the deletion.