Multi-AZ and Multi-Region Architecture for Protecting AWS Resources


In alignment with the Reliability pillar of the AWS Well-Architected Framework, Commvault recommends deploying Commvault software across multiple availability zones (multi-AZ) or across AWS Regions where high availabilIty and Disaster Recovery coverage is needed.

This page describes best practices for Commvault components when designing your Commvault in AWS data management architecture.

Failure Management: Back Up Data

For a multi-Region deployment, all Commvault components with persistent data or "state" must be protected to allow recovery and continued operation from the alternate Region. When you design multi-Region data management architectures, consider the following requirements:

  • Store Commvault Disaster Recovery backups both within the Primary and Secondary AWS Region to permit recovery of the CommServe server.

  • Backup and Archive data stored in Commvault Cloud Libraries (that is, Amazon S3 buckets) must be fully or partially replicated to the alternate Region or Regions to allow recovery operations from the Secondary Region.

  • Perform in-Region backups of deduplication databases (DDBs) on MediaAgents, and replicate the DDBs to the Secondary Region to reduce DDB reconstruction time after a failover event.

Note: Access nodes do not persist any data that is required during a failover event. You can re-provision or auto-scale access nodes in the new Region as required.

Failure Management: Fault Isolation

  • Deploy your CommServe server, MediaAgents, and access nodes groups across Availability Zones (AZs) to eliminate zonal single points of failure.

  • Deploy your CommServe server across AWS Regions to remove Regional single points of failure. This approach requires an auxiliary copy of critical data to an in-region Amazon S3 Cloud Library to allow continued recovery.

    Note: Commvault does not support deploying MediaAgent grids or Access Node groups across Regions.

  • Optionally, you can deploy the CommServe server, MediaAgents, and access node groups across the AWS Region and on-premises when connected via redundant AWS Direct Connect links.