This article applies to all JSDR software versions.
Problem
Disk protection fails when attempting to add new disks to a protected VM that is part of a CFO (Continuous Failover) protected domain. In the example scenario below, newly added disks report initial sync for an extended period of time and then subsequently transition to a "cancelled" protection status without any replication status.
...
The protection status of the VM is still recoverable, but its icon turns yellow highlighting a problem with newly added disks.
...
Solution
When a CFO domain is configured, VM settings and data at the protected site must remain synchronized with the recovery site. Any issue that impedes this synchronization will generate warning alerts. Check the following to diagnose the possible cause of the problem.
Confirm the disk added to the VM at the primary site is visible on the corresponding RVM at the recovery site.
If the corresponding disk cannot be found on the RVM, ensure the MSA is operational and connected. The MSA is essential in managing the synchronization of VM settings between the RVM and the protected site VM.
After resolving any MSA issues at the recovery site, it is necessary to either:
Re-protect the virtual machine containing the newly added disk.
Or, detach then reattach the new disk to the protected VM (JSDR version 4.2.x and above).
Examples
MSA Issue
A new disk Hard disk 7 is added to a protected VM in a CFO domain.
...
Checking hardware details of the RVM at the recovery site exposes the fact that Hard disk 7 had actually not been added to the RVM. This likely indicates a problem with the MSA.
...
DRVA Issue
A new disk Hard disk 7 is added to a protected VM in a CFO domain.
...