# Considerations for VMware Replication

Before you configure replication for VMs, consider any restrictions or hypervisor-specific issues that might affect replication operations.

## General Considerations

- During a replication operation, you can modify destination network settings only 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 the issue, remove the VM from the replication group and then add it back.

- For VMware destinations, replication is not supported with user-created checkpoints on the source Hyper-V VM.

- For VMware destinations, replication is not supported on the source Hyper-V VM with configuration version 5.

Important

Commvault will create a snapshot on the destination VM to maintain an expected level of integrity on the VM and its disk. Do not create snapshots of destination VMs after replication operations. If a snapshot exists, subsequent replication operations will fail.

## VMware Considerations

- For replicated VMs using source snapshots, failback operations are supported only when replication is configured in the Command Center.

- Periodic replication is not supported for the Cisco HyperFlex and Tintri snap engines.

- For VSA snap engine (VVol) replication, the failback operation is a full resync to the source.

- Incremental failback resync operations are supported only from streaming VMware backups.

- If the source VM that is being replicated is the same client as the vCenter hypervisor client, then the DR failover operation cannot be performed for the replication pair. Since the vCenter is running inside the source VM, the source VM will be shut down and the vCenter will be down during failover operations.

×

Loading...