There's a version mismatch between the Provider version (%VersionId;) running on the primary server and the version (%RecoveryVersionId;) running on the secondary (recovery) server.
The VMM service doesn't have the required privileges to modify the permissions on the import and export paths specified for ...
The VMM/Hyper-V server might not be able to communicate with Microsoft Azure Site Recovery. Check the Provider errors for ...
The VMM/Microsoft Azure Site Recovery service couldn't find a Hyper-V host, or the server doesn't have Internet connectivity, ...
There are no servers registered to the Azure Site Recovery vault. Atleast one server needs to be registered to perform this ...
There's a version mismatch between the Provider version (%VersionId;) running on the primary server and the version (%RecoveryVersionId;) ...
To begin reverse replication, trust must be established from the protected location to the protecting location. Verify that ...
To ensure that the VMM server has a valid vault key, run the Provider installation wizard on the VMM server and paste in ...
To ensure there are enough disk drives either disable protection of existing items or deploy a new master target server. ...
To resolve the issue, either perform the planned failover again, or perform an unplanned failover if the primary site isn't ...