Loading...

Deploying Commvault to AWS Outposts

The following table lists the available packages for deployment. Click the name of the server package that you want to install.

Package

Deployment supported on

Additional deployment details

High availability deployment

  • EC2 instance running on AWS Outposts
  • EC2 instance running on AWS region
  • Commvault CommServe Primary or DR instances can be deployed to your AWS Outposts.
  • Commvault recommends using an EBS-based disk library for any on-premises data required in your CommServe (CommServe DR backups, DDB backups, and so on.)

 

  • On-premises servers
  • EC2, RDS, EKS instances running on a region in the AWS public cloud
  • EC2, RDS, EKS instances running on AWS Outposts
  • Commvault deduplication is fully supported on AWS Outposts.
  • MediaAgent grids are supported across one or multiple AWS Outposts.
  • Grids are supported across your AWS Outposts and the AWS Region (requires low-latency network to AWS region).
  • Grids are supported across your AWS Outposts and on-premises infrastructure via an AWS Outposts Local gateway, go to AWS Outposts Features on AWS Outposts documentation site.

 

Note: Commvault recommends configuring the When Resources Are Offline option for alternate data paths to ensure that the normal MediaAgent operation occurs within region or within Outposts.

  • EC2, RDS, EKS instances running on a region in the AWS public cloud.
  • Access node groups can be used to perform snapshot-based EC2 and RDS protection from the region.
  • Access node groups can be used to perform streaming protection of RDS instances (dump/export) and EKS instances from within the Outposts.
  • Commvault automatically selects the access nodes within the Outposts when spanning access node groups between the region and the Outposts.

 

Note: Commvault supports spanning an access node group between AWS Outposts and AWS region, but recommends enabling the bEnableSubnetDispatch additional setting to ensure that the access nodes outside the Outposts are used.

CommServe Sizing for AWS Outposts

Commvault recommends the following AWS Outposts infrastructure to meet Commvault CommServe hardware specifications:

Extra large

Large

Medium

Small

Supports up to 10,000 servers, or 20,000 virtual machines, or 50,000 laptops in a single CommCell environment

Supports up to 2500 servers, or 5000 virtual machines, or 10,000 laptops in a single CommCell environment

Supports up to 500 servers, or 1000 virtual machines, or 5000 laptops in a single CommCell environment.

Supports up to 25 servers, or 100 virtual machines, or 200 laptops in a single CommCell, including deduplication mode

r5a.4xlarge 16 x vCPU, 128GiB RAM

r5.2xlarge 8 x vCPU, 64GiB

r5.2xlarge 8 x vCPU, 64GiB

r5.xlarge 4 x vCPU, 32GiB

500GiB gp2 disk

300GiB gp2 disk

200GiB gp2 disk

100GiB gp2 disk

MediaAgent Sizing for AWS Outposts

Commvault recommends the following AWS Outposts infrastructure to meet Commvault Deduplication Mode:

Extra large

Large

Medium

Small

Extra small

r5a.4xlarge 16 x vCPU, 128GiB RAM

r5.2xlarge 8 x vCPU, 64GiB

r5.xlarge 8 x vCPU, 32GiB

r5.large 4 x vCPU, 16GiB

r5.large 2 x vCPU, 16GiB

400GiB gp2 (OS)

400GiB gp2 (OS)

400GiB gp2 (OS)

300GiB gp2 (OS)

200GiB gp2 (OS)

2TiB gp2 (DDB1)

1.2TiB gp2 (DDB1)

600GiB gp2 (DDB1)

400GiB gp2 (DDB1)

200GiB gp2 (DDB1)

2TiB gp2 (DDB2)

1.2TiB gp2 (DDB2)

600GiB gp2 (DDB2)

400GiB gp2 (DDB2)

200GiB gp2 (DDB2)

2TiB gp2 (index cache)

1TiB gp2 (index cache)

1TiB gp2 (index cache)

400GiB gp2 (index cache)

400GiB gp2 (index cache)

Access Node Sizing for AWS Outposts

Commvault recommends the following AWS Outposts infrastructure to meet Commvault Amazon access node hardware specifications:

Extra large

Large

Medium

Small

Extra small

r5a.4xlarge 16 x vCPU, 128GiB RAM

r5.2xlarge 8 x vCPU, 64GiB

r5.2xlarge 8 x vCPU, 64GiB

r5.xlarge 4 x vCPU, 32GiB

r5.xlarge 2 x vCPU, 16GiB

400GiB gp2 disk

400GiB gp2 disk

400GiB gp2 disk

300GiB gp2 disk

200GiB gp2 disk

Last modified: 8/28/2020 6:28:38 PM