The primary and secondary sites for replication must have the required VMware environment, and must include Commvault components to manage operations and data movement. The requirements are slightly different for on-premises deployments and VMware Cloud on AWS.
For an on-premises deployment, you can create a hypervisor configuration using the vCenter or a standalone ESX host. For a destination site that is a VMware Cloud on AWS deployment, you can only use the VMware vCenter as the destination hypervisor.
If the destination site is a VMware Cloud on AWS deployment, the access node must be a virtual machine in the VMware Cloud.
The following table shows the components that must be present on the primary and destination sites:
Software | On-premises deployment | VMware Cloud on AWS |
---|---|---|
vCenter Server |
|
|
Datastore | On ESX host that is accessible from the vCenter. | vSAN support is included with VMware Cloud on AWS. |
Network | For replication from an on-premises VMware deployment to VMware Cloud on AWS, deploy a network gateway. For best results, use the Elastic Network Interface (ENI) to write data to AWS S3 libraries. Using the ENI Network Tunnel avoids incurring unnecessary traffic costs. | |
MediaAgent | Install on virtual machines running in the VMware Cloud. | |
Virtual Server Agent (VSA) | To create access nodes (VSA proxies), install the VSA package on physical or virtual machines. | Install on virtual machines running in the VMware Cloud. |
File Recovery Enabler for Linux (FREL) | Linux machines that have the MediaAgent and VSA packages installed are automatically configured to support file recovery for Linux guest VMs. | Use virtual machines running in the VMware Cloud. |
VAIO filters (required for continuous replication) | Install on source and destination ESX clusters. |