# Replication Using the Commvault HotAdd Transport Mode

## HotAdd Restores

The Commvault HotAdd transport mode performs restores for Amazon faster than traditional restores. By using an access node that is running on an Amazon instance, the restore operation can write directly to Elastic Block Storage (EBS) and inject Amazon drivers that are required for destination instances.

Note

Commvault supports the automatic injection of drivers on the source VMs. For more information, see VM Conversion to Amazon EC2 Using Commvault Hotadd.

The Commvault HotAdd transport mode used for the following operations:

- Restores

- Replication operations

- Conversion from VMware to Amazon EC2, for the following VMware guest operating systems:

### Linux

UEFI | BIOS
--- | ---
Alma Linux 8.4 Alma Linux 9.6 Amazon Linux 2.x CentOS 9.x Oracle Linux 7.x Oracle Linux 9.x Red Hat Enterprise Linux (RHEL) 8.x Red Hat Enterprise Linux (RHEL) 9.x Rocky Linux 8.x Rocky Linux 9.x Ubuntu 18.04 Ubuntu 22.04 Ubuntu 24.04 | CentOS 7.x Oracle Linux 7.8 Oracle Linux 8.6 Oracle Linux 9.x Red Hat Enterprise Linux (RHEL) 7.x Red Hat Enterprise Linux (RHEL) 8.x Red Hat Enterprise Linux (RHEL) 9.x Rocky Linux 8.x Rocky Linux 9.x Ubuntu 18.04 Ubuntu 22.04 Ubuntu 24.04

Note

AmazonSSMAgent is not supported for the following Linux systems:

- Oracle 8 UEFI

- Redhat 8 UEFI

- Redhat 8 BIOS

### Windows

BIOS and UEFI

- Microsoft Windows Server 2016 (Standard, Datacenter) (64-bit only)

- Microsoft Windows Server 2019 (Standard, Datacenter) (64-bit only)

- Microsoft Windows Server 2022 (Standard, Datacenter) (64-bit only)

- Microsoft Windows Server 2025 (Standard, Datacenter) (64-bit only)

- Microsoft Windows Server 2025 with legal notice (Standard, Datacenter) (64-bit only)

## Supported Volume and File System Types

### Windows

Instances with volumes that use Master Boot Record (MBR) and GUID Partition Table (GPT) partitioning are supported.

### Linux

Linux VMs that use one of the following for the root file system: ext2, ext3, ext4, Btrfs, JFS, or XFS.

## Restore Process Using the Commvault HotAdd Transport Mode

### Windows

1. Create empty EBS volumes.

2. Attach EBS volumes to access node.

   Up to 21 volumes can be attached to the VSA proxy during cross-hypervisor restores or live sync replication, occupying device slots xvdf - xvdz.

3. Restore data to EBS volumes.

   A snapshot of the EBS volumes is taken and retained as an integrity snapshot for reference during the next incremental replication.

4. Inject AWS components and drivers.

5. Detach and delete volumes from the access node.

6. The DR VM configuration is written to a JSON file and uploaded to a S3 bucket.

   The JSON file is available inside the cv-vmconfig-container folder under the S3bucket named as gx-restore-region_name-account_id. Where region_name is the name of the AWS region and account_id is the AWS account for the virtualization client.

7. An integrity snapshot is retained.

### Linux

1. Create empty EBS volumes.

   Up to 40 volumes can be attached to the VSA proxy during cross-hypervisor restores or live sync replication, occupying device slots xvdf - xvdz, or if the slots start with xvd, then xvdba - xvdbz, or a combination of both.

2. Attach EBS volumes to access node.

3. Restore data to EBS volumes.

   A snapshot of the EBS volumes is taken and retained as an integrity snapshot for reference during the next incremental replication.

4. Detach and delete volumes from the access node.

5. The DR VM configuration is written to a JSON file and uploaded to a S3 bucket.

   The JSON file is available inside the cv-vmconfig-container folder under the S3bucket named as gx-restore-region_name-account_id. Where region_name is the name of the AWS region and account_id is the AWS account for the virtualization client.

6. An integrity snapshot is retained.

## Related Topics

For information about installing drivers manually, see Preparing the Source VM for Conversion to an Amazon EC2 Instance.

×

Loading...