Azure Site Recovery
- The differential sync cache folder for the volumes %SrcHostName; %SrcVolume; => %DestHostName; %DestVolume; has exceeded ...
- The disk '%DiskName;' couldn't be deleted. The disk is being used by a virtual machine, or another operation is currently ...
- The DRA server is already registered in vault {0}. Either select the registration key associated with this vault, or unregister ...
- The first time you open the Microsoft Azure Site Recovery console after the Provider reinstall, the Repair Provider job runs ...
- The highly available virtual machine '%DraVMName;' on cluster '%DRAClusterName;' has one or more virtual disks that aren't ...
- The host operating system of the virtual machine isn't supported. The operating system must be Windows Server 2012 R2 or ...
- The host operating system of the virtual machine isn't supported. The operation system must be Windows Server 2008 R2 or ...
- The host operating system of the virtual machine isn't supported. The operation system must be Windows Server 2012 and later ...
- The Hyper-V host and its protected virtual machines couldn't be configured to use settings that are applicable for the upgraded ...
- The last successful replication for virtual machine '%VMName;' in cloud/site '%CloudName;' was more than 30 minutes ago. ...
- The last successful replication for virtual machine '%VMName;' in cloud/site '%CloudName;' was more than an hour ago. Replication ...
- The last successful replication for virtual machine '%VMName;' in cloud/site '%CloudName;' was more than an hour ago. Replication ...
- The last successful replication for virtual machine '%VMName;' in cloud/site '%CloudName;' was more than five minutes ago. ...
- The last successful replication for virtual machine '%VMName;' in cloud/site '%CloudName;' was more than five minutes ago. ...
- The last successful replication for virtual machine '%VMName;' in cloud/site '%CloudName;' was more than ten minutes ago. ...
- The last successful replication for virtual machine '%VMName;' in cloud/site '%CloudName;' was more than ten minutes ago. ...
- The last successful replication for virtual machine '%VMName;' in cloud/site '%CloudName;' was more than two hours ago. Replication ...
- The latest version of the Provider is installed on this server and the server is registered.{0}Would you like to register ...
- The memory size on virtual machine '%DraVMName;' was changed from %OldValue; MB to %NewValue; MB during failover. In Hyper-V, ...
- The Microsoft Azure Recovery Services Agent isn't installed on the Hyper-V host server %HostName;. Install the agent on the ...
- The Microsoft Azure Site Recovery Provider might not be the latest version. Check the Provider error for more information. ...
- The Mobility service couldn't be installed on the virtual/physical machine. Either the Process Server is not available or ...
- The Mobility service on %HostName; hasn't communicated for more than %TimeoutThreshold; seconds. No protected items are affected. ...
- The Mobility service on %HostName; hasn't communicated for more than %TimeoutThreshold; seconds. No protected items are affected. ...
- The Mobility service on %HostName; hasn't communicated for more than %TimeoutThreshold; seconds. Replication of the following ...
- The Mobility service on %HostName; hasn't communicated for more than %TimeoutThreshold; seconds. Replication of these volumes ...
- The Mobility service on %HostName;(%IPAddress;) couldn't communicate with the process server at IP address: %Ip;, Port: %Port;, ...
- The older version of the scout agent could not be uninstalled from the virtual machine. The PS is down, the provided credentials ...
- The operating system (%VmOsType;) of the machine doesn't match the operating system (%MtOsType;) of the Master Target server ...
- The operation failed because replication information isn't up to date. The virtual machine has been added to different replication ...
- The operation failed because replication information isn't up to date. The virtual machine might have been enabled for protection ...
- The operation isn't supported by the current version '%CurrentVersionId;' of Microsoft Azure Recovery Services Agent installed ...
- The operation isn't supported by the current version '%VersionId;' of the Microsoft Azure Site Recovery Provider installed ...
- The operation timed out. The VMM/Hyper-V/Configuration server couldn't communicate with the vault, connection to the Hyper-V ...
- The operation to disable protection failed because the virtual machine data couldn't be removed after protection was disabled. ...
- The passive stamp details for the '%ServiceName;' service with stamp id '%StampId;' couldn't be retrieved from the Provisioning ...
- The process server hasn't received any replication data from source %SrcVolume; of host %SrcHostName; in the past %TimeInMinutes; ...
- The processor count on virtual machine '%DraVMName;' was changed from %OldValue; to %NewValue; during failover. In Hyper-V ...
- The properties of the virtual machine can't be configured. Ensure that the virtual machine is configured for protection successfully. ...
- 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 ...
- The replication group isn't in a protected state. The virtual machine couldn't be added to an unprotected replication group. ...
- The replication group of virtual machine %VirtualMachine; couldn't be changed from %ReplicationGroupName; to %NewReplicationGroupName;. ...
- The replication group was reassigned to a different cloud, but an attempt was made to enable protection for it an older cloud. ...
- The replication state for the primary virtual machine on the VMM/Hyper-V server is '%PrimaryState;' and '%RecoveryState;' ...
- The replication state for the primary virtual machine on the VMM/Hyper-V server is '%PrimaryState;' and '%RecoveryState;' ...
- The replication state of primary virtual machine '%VMName;' ('%ID;') on the VMM/Hyper-V server is '%PrimaryState;'. Operations ...
- The replication state of recovery virtual machine '%VMName;' ( '%ID;' ) on the VMM/Hyper-V server is '%RecoveryState;'. Operations ...
- The replication state of the virtual machine on the Hyper-V host isn't synchronized with the Microsoft Azure Site Recovery ...
- The requested operation '%Operation;' cannot be performed on the replication group '%Name;'as it does not have any storage ...
- The requested operation '%Operation;' cannot be performed on the replication group as it is not participating in a group ...
- The requested operation '%TaskDescription;' failed with status '%Status;'. Detailed error message: '%DetailedErrorMessage;'. ...
- The requested recovery point objective (RPO) isn't supported by the storage array. Requested RPO value: %RpoValue; second(s), ...
- The resynchronization cache folder for the replicating volumes %SrcHostName; (%SrcVolume;) => %DestHostName; (%DestVolume;) ...
- The RPO has exceeded the configured SLA threshold of %RPOSLAThreshold; seconds for protected volume %SrcHostName; %SrcVolume; ...
- The selected azure vm size %VMSize; is not supported by the subscription or location of storage account or affinity group. ...
- The selected Azure VM size has CPU or Memory capacity less than the CPU or Memory of the VM On prem. This may affect the ...
- The storage arrays are not managed by the same provider type and no Storage Replica capable Storage Spaces array is present ...
- The storage arrays couldn't be paired because storage array '%ArrayName;' that contains storage pool '%PoolName;' isn't a ...
- The storage logical unit '%LogicalUnitName;' couldn't be mounted as a CSV in cluster '%DRAClusterName;'. Virtual machines ...
- The storage pools couldn't be paired because storage array '%ArrayName;' is a SAN array and storage array '%TargetArrayName;' ...
- The storage provider was removed and re-added with an updated provider address in SCVMM. Keep the provider management address ...
- The subnet might not exist in the given Azure virtual network. Specify a valid subnet in the network and retry the operation. ...
- The subscription limit for the cloud service was reached. Maximum limit: %MaxHostedServiceCount;. Attempted: %AttemptedHostedServiceCount;. ...
- The subscription limit for the storage service was reached. Maximum limit: %MaxStorageServiceCount;. Attempted: %AttemptedStorageServiceCount;. ...
- The version of Microsoft Azure Recovery Services Agent installed couldn't be found on the Hyper-V host server %HostName;. ...
- The virtual machine %DraVMName; is in state %DraVmState;. Network settings can't be applied to the virtual machine in this ...
- The virtual machine %VMName; cannot be deployed outside of a cloud because it requires Hyper-V protection. Hyper-V protected ...