HotAdd Restore Process (Using Amazon Proxy) Where Proxy and Destination Instance are in Different Availability Zones

A HotAdd restore performed using an Amazon proxy in a different availability zone includes the following stages:

1. Create empty EBS volumes.

2. Attach EBS volumes to the access node.

   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.

   The attached EBS volumes occupy the following device slots:

   Linux	Windows
   /dev/sd[f-z]	xvd[f-z]
   /dev/xvda[a-z]	xvda[b-z]
   /dev/xvdb[a-z]	xvdb[a-z]
   /dev/xvdc[a-z]	xvdc[a-z]
   /dev/xvdd[a-x]	xvdd[a-x]
   /dev/xvd[e-z]	/dev/sd[f-z]

3. Restore data received from the MediaAgent into the attached volumes.

4. Detach the volumes.

5. Create EBS snapshots from volumes.

   Encryption depends on the source EBS Volumes and encryption by default is enabled on the account and region.

   Note

   Commvault software performs the following steps:

   1. Adds the EBS Volume Encryption Key: Uses the EBS volume encryption key.

   2. Checks Encryption Status: Determines if the snapshot is unencrypted and encryption by default is enabled on the account and the region, or if the snapshot is encrypted and shared as part of cross account.

      Commvault software utilizes GetEbsEncryptionByDefault and GetEbsDefaultKmsKeyId encryption preferences on your account to ensure all created EBS volumes and snapshots are encrypted with your preferred KMS key.

   3. Verifies Volume Size: Checks the volume size for the following:

      • If the volume size is less than 16TB, Commvault software creates a new volume using the existing encrypted snapshot copy.

      • If the volume size is greater than 16TB, Commvault software creates an encrypted snapshot copy and then creates a new volume using the encrypted snapshot copy.

6. Delete the volumes that were created in the zone where the VSA proxy resides.

7. In the destination zone, create volumes (including inheriting encryption from the snapshot).

8. Create a new instance from the source AMI, or from an AMI that matches the operating system and type of the target instance.

9. Stop the recovery EC2 instance.

10. Detect and terminate the recovery instance OS volume, and attach the restored OS volume.

11. Attach the restored data volumes.

12. Delete the volumes that were created in step 5.