The recovery server has an existing virtual machine '%DraVMName;' with the same Hyper-V virtual machine ID. This might be leftover from a previous failed attempt to join the virtual machine to the replication group.
The protection state for the replication group '%ReplicationGroupName;' managed by VMM '%VMMName;' couldn't be updated. No ...
The recovery cluster to be used for failover of storage replication group '%ReplicationGroupName;' couldn't be determined. ...
The recovery plan has invalid actions. Check that Automation runbooks have only been added to recovery plans that fail over ...
The recovery point objective (RPO) value specified is out of range. Requested RPO value: %RpoValue; second(s). Minimum supported ...
The recovery server has an existing virtual machine '%DraVMName;' with the same Hyper-V virtual machine ID. This might be ...
The registration key has expired. Download a new registration key from Azure Site Recovery and select it. The downloaded ...
The replication group '%ReplicationGroupName;' contains more logical units than expected, including:'%LogicalUnitName;'. ...
The replication group '%ReplicationGroupName;' doesn't contain the logical unit '%LogicalUnitName;'. Check the replication ...
The replication group cannot be removed as one or more objects such as cloud, VM, template, or host disk are associated with ...