If the job was running for a long time, check whether there's a related job currently in progress. If there is one, wait for it to complete and retry the operation. Alternatively, check whether the job's waiting for a server task to complete, and the server isn't responding. If this occurs, check the server connection.
Fix any virtual machine state issues in the Hyper-V Manager console, and fix any Hyper-V host errors. Then retry the operation. ...
Fix the virtual machine state by enabling resynchronization, or resume the replication from the Hyper-V Manager console and ...
For the missing subnets on the primary VM network, the first available subnet on the recovery VM network will be configured ...
Go to the virtual machine properties page to select the network adapters to be used or to increase the role size of this ...
If the job was running for a long time, check whether there's a related job currently in progress. If there is one, wait ...
If the key isn't working download a new registration key from the quick start page in the Azure Site Recovery portal and ...
If the recovery site virtual machine is available, trigger a failover of the virtual machine or remove the virtual machine ...
If the source is experiencing high change rate, please wait for the change rate to return to normal for the consistency points ...
If the volume is Resynchronizing, please wait for the volume to reach the Ok replication status for the recovery window information ...