Backups for Amazon Web Services Instances


The Commvault software protects Amazon EC2 instances by creating an Amazon hypervisor and associated VM groups, which identify the instances to back up. A VM group has an associated backup plan that defines the backup schedule, storage location, and retention. The plan associated with the AWS hypervisors and VM groups manages scheduled backups. You can also perform on-demand backups.

Commvault can orchestrate the creation of cloud-native Amazon EBS snapshots and Amazon EC2 AMIs as a rapid recovery point when you enable IntelliSnap backup on the VM group. During an IntelliSnap backup, the Commvault software orchestrates and manages the creation of an Amazon Machine Image (AMI) and the associated Amazon EBS snapshots, which are retained per the retention settings in the backup plan. If an Amazon EC2 instance fails to create an Amazon Machine Image (AMI) during an IntelliSnap backup of a VM group, the backup job is marked as completed with errors.

To back up Amazon EC2 instances that have UEFI boot mode enabled, there must be at least one UEFI-enabled AMIs present in the AWS account performing the backup. If a UEFI boot enabled AMI is not present, the backup will fail.

For more information, see the following:

Amazon EC2 Backup Using Amazon EBS Direct APIs

Commvault uses Amazon EBS direct APIs to perform Change Block Tracking (CBT) backups of Amazon EC2 instances and associated Amazon EBS volumes. Amazon EBS direct APIs accelerate back up activity by identifying changes between two Amazon EBS snapshots by using the API. You can use Amazon EBS direct APIs or Change Block Tracking with streaming backups, and with the backup copy operation of IntelliSnap backups. By default, CBT is enabled when you create a new AWS hypervisor VM group. You can also enable CBT for existing VM groups. For more information about CBT for AWS, see Changed Block Tracking for AWS.