HotAdd Backup Process for Amazon EC2 Instances Including Amazon VPC Resources

When Amazon VPC protection is enabled, the HotAdd backup operation includes the following stages:

For each instance, create an AMI.

This operation creates crash-consistent snapshots of instance volumes.
Write the instance configuration file, the network configuration JSON file, and the instance metadata to the backup index.
Create volumes from the snapshots.
Attach volumes to the VSA proxy.

For the m7a.48xlarge instance type, up to 128 EBS volumes can be attached to the access node. For most Nitro instances, up to 28 EBS volumes can be attached.

With Windows instance, the attached EBS volumes occupy the following device slots:
- xvd[f-z]
- xvda[b-z]
- xvdb[a-z]
- xvdd[a-x]
- /dev/sd[f-z]
- xvdc[a-z]
With Linux instances, the attached EBS volumes occupy the following device slots:
- /dev/sd[f-z]
- /dev/xvda[a-z]
- /dev/xvdb[a-z]
- /dev/xvdc[a-z]
- /dev/xvdd[a-x]
- /dev/xvd[e-z]
Back up the volumes, using CRC for incremental changes and directing data through the MediaAgent for the storage policy that is associated with the backup.
Unmount, detach, and delete the snapshots, and de-register the AMI.

The snapshots created for instances that were deleted or removed from the subclient must be cleaned up manually.
Delete the AMI.
If CBT is enabled, retain the most recent AMI (tagged with CV_CBT_Snap).

Related Pages