Processing for Using Resources from an Admin Account

When you configure a hypervisor to use service account resources, most backup processes that are initiated from the member account hypervisor use resources from the service account and most of the processing is performed in the service account, with minimal effect on the member account. When using resources from a service account, you must add JSON permissions to both the service account and the member accounts.

AWS account terms are defined as follows:

• Service account: A hypervisor that is added to Commvault and that contains shared backup resources such as access nodes and cloud libraries.

• Member account (also called workload account): An organizational account with workloads to protect. Member accounts are accessed by service accounts for the purposes of backup and recovery.

Streaming Backup Processes

Streaming backup processes use the following steps:

1. On the member account:

   1. Create an Amazon Machine Image (AMI) from the source Amazon EC2 instance.

   2. Share the AMI to the service account.

2. On the service account:

   1. Create Amazon EBS volumes from the AMI.

   2. Attach Amazon EBS volumes to the proxy, create an Amazon EC2 instance, and back up the Amazon EC2 instance and Amazon EBS volumes.

   3. Detach the Amazon EBS volumes, and then delete them.

   4. Delete the AMI.

IntelliSnap Backup Processes

IntelliSnap backup processes are unchanged for operations that use resources from a service account.

IntelliSnap backup processes use the following steps:

1. For each Amazon EC2 instance, create an AMI.

   This operation creates crash-consistent snapshots of Amazon EBS volumes.

2. Write the Amazon EC2 instance configuration file and the Amazon EC2 instance metadata to the backup index.

Backup Copy Processes

Backup copy operations use the following steps:

1. On the member account, share snapshots with the service account.

2. On the service account:

   1. Create Amazon EBS volumes.

   2. Attach the Amazon EBS volumes to the proxy.

   3. Back up the Amazon EBS volumes.

   4. Detach the Amazon EBS volumes.

   5. Unshare the snapshots.

HotAdd Restore Processes

HotAdd restore operations use the following steps:

1. On the service account:

   1. Create empty Amazon EBS volumes.

   2. Attach the Amazon EBS volumes to the proxy and create an Amazon EC2 instance.

   3. Restore data.

   4. Detach the Amazon EBS volumes.

   5. Create a snapshot of the Amazon EBS volumes, and then delete the Amazon EBS volumes.

   6. Share snapshots to the member account.

2. On the member account:

   1. Create Amazon EBS volumes from snapshots.

   2. Create the Amazon EC2 instance, and then attach the Amazon EBS volumes.

Import Restore Processes

Import restore operations use the following steps:

1. On the service account:

   1. Initialize the cloud file system.

   2. Attach the Amazon S3 prefix to the proxy.

   3. Share the Amazon S3 bucket to the member account.

   4. Restore data as Virtual Hard Disk (VHD) pages in Amazon S3.

   5. Merge the VHDs.

   6. Launch the AWS VM Import task to create an AMI.

   7. Share the AMI to the member account.

2. On the member account, restore the Amazon EC2 instance from the AMI.

Live Browse and File Recovery Processes

For streaming backups, live browse and file recovery operations are unchanged for operations that use resources from a service account.

Agentless File Recovery Processes from Streaming Backups

Agentless file recovery operations use the following steps:

1. Restore files to the local proxy.

2. Share the Amazon S3 bucket to the member account.

3. Upload to the Amazon S3 bucket.