Before you configure replication for virtual machines, consider any restrictions or hypervisor-specific issues that might affect replication operations.
General Considerations
-
During a replication operation, you can only modify destination network settings for Windows VMs. Linux VMs are replicated without network connections.
-
If you select a specific VM for replication, the GUID of the source VM is used to identify the VM for replication. If the GUID of the source VM changes, the VM is not replicated. This situation can occur when a VM with the same name is added on the hypervisor for the source VM. To resolve this issue, remove the VM from the replication group and then add it back.
Amazon Considerations
-
Virtual machines must have been backed up at least once to be added to a replication group.
-
After you replicate instances to Amazon using the HotAdd method, a Windows instance restarts when a user logs on to the instance for the first time. The restart is required to initialize drivers that are added to the instances during the operation.
-
When you replicate to Amazon, the import method is used if you use a proxy that is not an Amazon instance, if the proxy and destination site are in a different region or zone, or if you do not provide guest credentials for the guest instance.
-
For replication from an Amazon source site to an Amazon destination site, you must use a VSA proxy (access node) that is deployed as an Amazon instance.
-
Each replication job from Amazon to Amazon recreates destination instances completely, even when the replication job is for an incremental backup of a source instance.
-
You cannot restore to an Amazon EC2 guest instance that uses a non-volatile memory express (NVMe) host controller. This restriction applies for full instance restores, conversion to an Amazon EC2 instance, and replication to an Amazon EC2 destination instance.