Replication Using the HotAdd Method

Updated

HotAdd replication for Amazon provides faster performance than replication using the import method. By using an access node (VSA proxy) that is running on an Amazon instance, the replication operation can write directly to Elastic Block Storage (EBS) and inject Amazon drivers that are required for destination instances.

Note: For replication of guest VMs that run Windows Server 2008 R2, validation might fail for the converted instance in AWS. To resolve this issue, set the RealTimeIsUniversal registry key on the source VM as described in the AWS article Configuring Time Settings for Windows Server 2008 and later, and then perform a new replication.

Requirements for HotAdd Replication

  • The access node for the replication operation must be an Amazon EC2 instance in the destination region. A single access node can perform recovery operations for all Amazon availability zones within a region.

  • For 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 replication.

Requirements for Replication Operations when Amazon is the Destination

For Windows guest VMs, you can copy drivers that are required for AWS instances to the access node that is used for replication. During the replication, drivers are automatically installed on the destination guest instances.

For Linux guest VMs, you must copy the required drivers to the source VMs and then perform a new replication.

HotAdd Replication Process

Windows:

  1. Create empty EBS volumes.

  2. Attach EBS volumes to access node.

    Up to 21 volumes can be attached to the access node during 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 volumes from the access node.

  6. Create the Amazon instance from the EBS volumes.

  7. Automatically log on to the instance to install PV drivers and EC2 configuration service.

Linux:

  1. Create empty EBS volumes.

    Up to 40 volumes can be attached to the access node during 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 volumes from the access node.

  5. Create the Amazon instance from the EBS volumes.