VMM cannot migrate or clone the virtual machine (%VMName;) because the version (%TargetHostVSVersion;) of the virtualization software on the destination host (%VMHostName;) does not meet the requirements for the version of the virtualization software on the recovery host (%ReplicaHostVSVersion;).
Virtual machines '%VMNames;' were not found in Azure or could not be reached for the failover operation. This can happen ...
Virtual machines protected to Azure will be encrypted. Encrypted data is decrypted during failover from the Windows Hyper-V ...
Virtual machines protected to Azure will be encrypted. Encrypted data is decrypted during failover from the Windows Hyper-V ...
VM has stale protection settings. You'll need to manually clear protection settings before you can enable protection again. ...
VMM cannot migrate or clone the virtual machine (%VMName;) because the version (%TargetHostVSVersion;) of the virtualization ...
VMM/Hyper-V/Configuration server '%VMMName;' might not be running, or it couldn't communicate with Microsoft Azure Site Recovery. ...
Volume %DeviceName; offset: %OffsetToRead; bytes read: %BytesRead; bytes requested: %BytesRequested; couldn't be read on ...
Wait until the recovery plan operations finish, and then save it as required. Don't navigate away from the Configure page ...
You have the following versions installed: %DraVersions;. Each server must have the same version of the provider installed ...