To resolve the issue, either perform the planned failover again, or perform an unplanned failover if the primary site isn't available.
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 ...
Unable to import the service authentication certificate used for Hyper-V Recovery Manager services into the certificate store. ...
Unable to retrieve vault information from Azure Site Recovery. This could be due to internet connection failure or Invalid/expired ...
Usage: DRConfigurator.exe /r /friendlyname value /proxyaddress value /proxyport value /proxyusername value /proxypassword ...
User role (%UserRoleId;) can't be found. User roles set on primary site virtual machines must also exist on the recovery ...