Launch & Maintain > S3, EBS Volumes, and Snapshots > Recovering When EBS Volumes Fail

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.

Recovery Steps

  1. Shut down the Q-Cloud Protect appliance.
  2. 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..
  3. 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.
  4. 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
  5. 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.

    Important

    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.

  6. Delete the corrupted EBS volume. See Delete the corrupted EBS volume. See Delete a corrupted volume..

See Also IconSee Also