You can deploy Commvault software components using on-premises equipment or by installing software on Amazon EC2 instances. You can use either of the following basic deployment models:
Install the CommServe software on a server in your on-premises environment, and then deploy Amazon EC2 instances that have the Virtual Server Agent (VSA) package or MediaAgent package installed.
Install the CommServe software, VSA package, and MediaAgent package on Amazon EC2 instances. The instances where the VSA and MediaAgent software runs can be in different availability zones or regions than the instance where the CommServe software runs.
In smaller deployments, all Commvault components can be installed on a single backup server, while in larger deployments each component resides on a separate instance.
Instances that have the Virtual Server Agent package installed act as access nodes (also called VSA proxies) to manage data protection operations. To back up the Amazon EC2 instances, you must deploy an access node in each region where your Amazon EC2 instances reside. You can deploy additional access nodes as needed to handle your planned workload.
Instances that have the MediaAgent package installed manage data movement between instances that are backed up and the storage where backups are stored. A MediaAgent does not have to be co-located with instances or the CommServe host, but data movement is faster when the MediaAgent is in the same region as the instances that are being backed up. You can enable power management for MediaAgents in AWS, to power on MediaAgents automatically when they are needed and turn them off when operations are complete.
In any deployment, the CommServe host, MediaAgents, and access nodes must be able to communicate with each other.
The following operations require that both the VSA package and the MediaAgent package be installed on the same instance:
IntelliSnap backups and backup copies
Live browse from streaming backups or IntelliSnap backups
Full VM restores from IntelliSnap backups
High Availability and Disaster Recovery
Commvault uses backup data to support continued operations when an outage occurs, including the option to recover from a specific point in time (a specific backup job). You only need to protect the CommServe host and your Amazon EC2 instances. Access nodes and MediaAgents can be deployed as new instances, and do not need to be backed up or recovered from backups.
You can use either of the following methods to restore backup infrastructure after an outage:
Perform ongoing backups on the primary site, and copy backup data to one or more secondary sites on a periodic basis. If an outage occurs for the primary site, use the backup data at a secondary site to restore instances.
Use Live Sync replication to create and maintain one or more warm recovery sites that are regularly updated with data from ongoing backups of the primary site. Use orchestration features to perform planned or unplanned failovers, suspend backups for the primary site during a failover, back up data on the secondary site, and perform a failback when the primary site is restored to service.
You can recover from on-premises sites to cloud sites, from cloud sites to on-premises sites, or to a different availability zone or region within the same cloud environment. The most important element in your recovery design is to ensure that the primary site and secondary site are separate, so that they are not both affected by a single outage.
For components that reside in AWS, use the following best practices:
For an AWS region, configure a standby CommServe host in a different availability zone than the availability zone where the production CommServe host resides.
Store the backups that are used for disaster recovery in S3 buckets that are configured for cross-region replication. These buckets add the ability to recover from an AWS region failure.
For higher uptime and reliability, you can configure EC2 instances that run the CommServe and MediaAgent components to use the AWS automatic recovery feature.
The following topics provide information about the Commvault software:
To see a list of Commvault features that support Amazon capabilities, see Amazon.
For information about the deployment of Commvault software components, see Deployment.
For deployment information for the Virtual Server Agent with Amazon, see Deployment - Virtual Server Agent for Amazon.
To review the requirements for protection of Amazon EC2 instances using the Virtual Server Agent, including Amazon regions, see System Requirements.
For information about network requirements, see Best Practices for Network Security.
For information about Commvault support for cloud storage, see Cloud Storage.
For information about automatic power management, see Cloud MediaAgent Power Management.
For information about backups of Amazon EC2 instances, see Backups.
For information about restoring Amazon EC2 instances, see Restores.
For information about Live Sync replication, see Replication.
For information about CommCell disaster recovery, see CommCell Disaster Recovery.
For information about CommServe recovery, see CommServe Recovery.
The following AWS documentation pages provide information about Amazon features:
For information on EC2 instance automated recovery, go to Recover Your Instance.
For more information about using Amazon CloudWatch alarms to recover an instance, see Adding Recover Actions to Amazon CloudWatch Alarms.