Known Issues for Continuous Replication

This page lists known issues with this release.

General

Continuous replication cannot be configured on VMs with existing snapshots because it fails to attach VAIO plugin (VMware limitation). After the replication is configured, however, the source VM can be snapped as well as backed up. The destination VM cannot be backed up or snapped.
Linked clone VMs cannot be replicated with continuous replication.
Ensure that VSA proxies and ESXi hosts have the correct time synchronization. If not, replication might remain in a starting state or replication might fail with the error "Failed to initialize data rehydrator on source". The BlrSvc.log might contain the following error:
```
ESX and local time differ too much. Please enable NTP synchronization.
```

Source VMs with Integrated Drive Electronics (IDE) disks cannot be replicated. (VMware limitation)
As a workaround, see the VMware KB article Converting a virtual IDE disk to a virtual SCSI disk (1016192).
VMs that have shared SCSI controller disks cannot be replicated with continuous replication.
Replication is not supported for VMs with disks on an NVME controller.
Replication is not supported for VMs with independent, non-persistent disks.
Disk mode on the VMs on the destination site will be changed to dependent during replication.
You should not change the disk mode to independent persistent on the VM on the destination site before any Auto Recovery operations. You can change it after performing a successful failover.
Disk mode on source or production VMs will become dependent after failback. You can manually change this after failback.
Application-consistent recovery points are supported for VMs with independent persistent disks.

All VMs configured for replication must use shared cluster storage. If any VM uses local storage, VMs cannot be migrated with vMotion and the ESXi host cannot be placed into maintenance mode to install plug-ins. (VMware’s vMotion limitation)