If a failback task becomes stuck due to some uncommon error scenarios (e.g., MSA unable to contact a DRVA), a generic error message could be shown without obvious meaning to the user. In such a case, contact JetStream Software to understand the cause of the problem. (DRBC-4305)
While running a Test Failover runbook in manual mode, the runbook groups dialog box may show an empty group of independent protected VMs. This can be safely ignored. (DRBC-4694)
While running Continuous Failover (rehydration), if the protected site goes down the GUI will still display the graceful "Planned Failover" option. If this option is selected, Planned Failover will fail; however, the user will still be able to select the correct "Force Failover" option which will work. (DRBC-5139)
If the remote site is upgraded to version 4.1.16 while Continuous Failover is in progress and there are disk configuration changes at the primary site after the upgrade, Continuous Failover may fail. In such cases, Continuous Failover should be restarted.
If recovery fails or is cancelled, and MSA is not able to remove some of the Representation VMs (RVMs), it might not delete some other related RVMs created for the same domain. It is ok to delete all of them manually. (DRBC-7178)
When finalizing failover for VMs from a CFO domain. If DRS moves the restored VM to a different host, it may fail automatic application of the expected network configuration of such VMs. Network (re)configuration for such VMs must be performed manually. (DRBC-7310)