Either replication traffic couldn't be sent to the recovery server, or the recovery server couldn't process the replication traffic because of storage issues.
Either completion of test failover was left unattended for more than two weeks, or the operation failed because of an internal ...
Either completion of the manual action was left unattended for more than three days, or the operation failed because of an ...
Either Hyper-V host cluster %DRAClusterName; contains at least one static network adapter, or no connected adapters are configured ...
Either replication traffic couldn't be sent successfully to the recovery server, or the recovery server couldn't process ...
Either replication traffic couldn't be sent to the recovery server, or the recovery server couldn't process the replication ...
Either the current replication state of the virtual machine doesn't support this operation, the recovery site configuration ...
Either the primary server couldn't send replication traffic to the recovery server, or replication was paused on the recovery ...
Either the script location couldn't be reached, or you don't have the required permissions to run the script. There might ...
Either the virtual machine couldn't be found on the recovery server, or check the provider error for additional information. ...