This article applies to all JSDR software versions
\uD83E\uDD14 Problem
When attempting to add a new disk to a protected virtual machine (VM), the protection of these disks failed. This issue is predominantly noticed when a CFO (Continuous Failover) is configured for the corresponding protected domain.
\uD83C\uDF31 Solution
When a CFO domain is configured, any modifications to the VM settings at the protected site need to be synchronized with the recovery site. If any issues impede this synchronization, it is anticipated that the primary site may generate warning reports.
In this scenario, the newly added disk will report initial sync for an extended duration and subsequently transition to a "cancelled" protection state.
Click on the details of the protected VM that is indicating a yellow tag (as shown in the image above).
Verify and confirm that the recently added VM disk at the primary site is visible on the corresponding RVM at the recovery site(VM edit settings of RVM).
If it's not, ensure that the MSA is in good health. The MSA must be in good health to facilitate effective synchronization of VM settings between the RVM and the production site VM.
After resolving the MSA issues at the recovery site, it is necessary to either reprotect the virtual machines that hold newly added disks or detach and reattach the new disks to the protected VM.
Note: This behavior is observed in a JetStream-protected environment where a CFO is involved.
Recovery DRVA plays a crucial role in synchronizing VM data between the protected VM and RVM. It's important to note that any issues with DRVA will not affect the protection of the new VM disk.
Any issue with Recovery DRVA will report "error retrieving protected domain details from DR virtual appliance" Protected domain recovery not running on CFO recovery Domain