> CommCell Console > Backup and Restore Agents > Virtualization > Virtual Server Agent > Cross-Hypervisor Restores (Virtual Machine Conversion) > Converting from VMware or Hyper-V to Amazon

VM Conversion from VMware or Hyper-V to Amazon EC2

HotAdd Restores

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

HotAdd restores are used for the following operations:

  • Restores

  • Live sync operations

  • Conversion from VMware to Amazon

Supported 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

  • 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

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.

HotAdd Restore Process

  1. Create empty EBS volumes.

  2. Attach EBS volumes to access node.

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

    • Linux: 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.

  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.

    • If the guest VM is restored in the same zone as the access node with credentials, CvDriverInject.sh is used for driver injection.

    • If restored in a different zone without credentials, customization is handled via Customizer node logic.

    Use a Windows access node for Windows VMs and a Linux access node for Linux VMs.

  5. Detach volumes from the access node.

  6. Create or reuse an instance based on the type of replication:

    • In case of a full replication, a new instance is created from the EBS volumes.

    • In case of an incremental replication, the EBS volumes are attached to the existing destination instance.

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

×

Loading...