Verify that your environment meets the system requirements for protecting Amazon EC2 instances with Commvault.
Deployment and Scaling
A single access node can service multiple regions and availability zones.
You can scale access nodes vertically or horizontally to achieve additional throughput based on data volume.
Amazon EC2 access nodes can be deployed either in the same region, availability zone, or AWS account as the protected data or in an alternate region, availability zone, or AWS account as the protected data.
Amazon Elastic Block Store (Amazon EBS) direct API restores provide optimal restore performance across regions, availability zones, and accounts.
In a deployment that uses resources from an admin account, the access node can be in the admin account. For more information, see Using Resources from an AWS Admin Account.
For the following operations, the access node can be an Amazon EC2 instance or an external machine:
VM conversion and restores
IntelliSnap backups and restores from IntelliSnap jobs
You can configure an access node on a Linux instance using one of the following methods:
Deploy an AWS Marketplace AMI.
From AWS Marketplace AMI, you can deploy the Commvault Cloud Access Node BYOL to serve as a Linux access node and as a File Recovery Enabler for Linux. This AMI contains all of the components that are required to support Linux operations in the Commvault environment. For more information, see Deploying a Commvault Linux MediaAgent from AWS.
Use one of the following Linux distributions:
Amazon Linux 2 (preferred)
RHEL 8.5, 8.3, 8.2, 8.1, 8.0, 7.9, 7.8, 7.7, 7.6, 7.5, 7.4
Note: For RHEL 8 instances, to install operating system packages that must enable automatic installation of Mono, register the instances with Red Hat.
Configure an Amazon Linux instance that uses a 64-bit ARM processor with the required software.
When you use an AWS instance with the 64-bit ARM processor as a Linux access node for VSA, you can back up instances or restore full instances, but you cannot restore guest files.
The following features are not supported when using a Linux access node. Use a Windows access node for these operations.
Full instance restores (import method)
Conversion from another hypervisor to Amazon EC2 (import method)
Conversion from another hypervisor to Amazon EC2 (import method) is not supported when using a Linux access node to convert a Windows guest VM
Live sync replication (import method)
For cross-hypervisor restores or replication from VMware to Amazon, you can use an access node that runs on Windows or Linux. If you use an access node that runs on Linux, for both Windows and Linux guest VMs, the drivers must be installed on the source before performing the backup. Otherwise, the replication operation fails. You cannot use a Linux access node for the import method.
All Windows-compatible processors are supported.
Microsoft Windows Server 2019 Editions
Microsoft Windows Server 2016 Editions
Microsoft Windows Server 2012 R2 Editions
This access node can contain a deduplication database (DDB) for writing index data.
IntelliSnap and streaming
This access node can contain a DDB for index data and streamed data.
The following processor architectures are supported:
x64 (Linux, Windows)
A minimum of 100 GB disk space recommended.
Minimum of 4 GB RAM required beyond the requirements of the operating system and running applications.
Amazon EC2 Instance Families
The Virtual Server Agent (VSA) package is supported on Amazon Linux 2 and Graviton2 EC2 instance families that include the following:
Amazon EC2 cost and performance optimized (A1)
Amazon EC2 general purpose (M6g, M6gd, T4g)
Amazon EC2 compute optimized (C6g, C6gd, C6gn)
Amazon EC2 memory optimized (R6g, R6gd, X2gd)
Commvault requires certain IAM permissions to perform data management operations in the AWS cloud. For more information about the required IAM permissions, see Amazon Web Services User Permissions for Backups and Restores.
Amazon EC2 access nodes that run on Amazon EC2 instances must meet the following additional requirements:
Windows Server instances where the Virtual Server Agent is installed must upgrade to the latest paravirtual (PV) driver.
EBS optimized, high IOPS volume.
For streaming backups and backup copies, if the access node used for backups and restores is running on an Amazon EC2 instance, the access node must be available in the same user account as the instance being backed up or restored. This requirement does not apply to IntelliSnap backups.
The Virtual Server Agent requires Layer 3 network connectivity to the upstream MediaAgent on port 8403. If the MediaAgent and the access node are in different accounts or in different Virtual Private Clouds (VPCs), you can configure Amazon VPC peering as described in the AWS article VPC peering basics.
The access node machine must be able to connect to ec2.amazonaws.com, or the regional equivalent if the AWS account is restricted to specific regions. To route communications through an HTTP or HTTPS proxy, provide proxy information in the CommServe Control Panel, on the HTTP Proxy tab of the Internet Options dialog box. To use an HTTPS proxy, you must provide authentication details.
Nutanix Cloud Clusters (NC2) with Amazon EC2
Commvault supports data protection and management for Nutanix Cloud Clusters (NC2) on Amazon EC2.
System Requirements for Virtual Server Agent with Amazon Web Services in the Expert documentation