Azure Site Recovery

  1. The differential sync cache folder for the volumes %SrcHostName; %SrcVolume; => %DestHostName; %DestVolume; has exceeded ...
  2. The disk '%DiskName;' couldn't be deleted. The disk is being used by a virtual machine, or another operation is currently ...
  3. The DRA server is already registered in vault {0}. Either select the registration key associated with this vault, or unregister ...
  4. The first time you open the Microsoft Azure Site Recovery console after the Provider reinstall, the Repair Provider job runs ...
  5. The highly available virtual machine '%DraVMName;' on cluster '%DRAClusterName;' has one or more virtual disks that aren't ...
  6. The host operating system of the virtual machine isn't supported. The operating system must be Windows Server 2012 R2 or ...
  7. The host operating system of the virtual machine isn't supported. The operation system must be Windows Server 2008 R2 or ...
  8. The host operating system of the virtual machine isn't supported. The operation system must be Windows Server 2012 and later ...
  9. The Hyper-V host and its protected virtual machines couldn't be configured to use settings that are applicable for the upgraded ...
  10. The last successful replication for virtual machine '%VMName;' in cloud/site '%CloudName;' was more than 30 minutes ago. ...
  11. The last successful replication for virtual machine '%VMName;' in cloud/site '%CloudName;' was more than an hour ago. Replication ...
  12. The last successful replication for virtual machine '%VMName;' in cloud/site '%CloudName;' was more than an hour ago. Replication ...
  13. The last successful replication for virtual machine '%VMName;' in cloud/site '%CloudName;' was more than five minutes ago. ...
  14. The last successful replication for virtual machine '%VMName;' in cloud/site '%CloudName;' was more than five minutes ago. ...
  15. The last successful replication for virtual machine '%VMName;' in cloud/site '%CloudName;' was more than ten minutes ago. ...
  16. The last successful replication for virtual machine '%VMName;' in cloud/site '%CloudName;' was more than ten minutes ago. ...
  17. The last successful replication for virtual machine '%VMName;' in cloud/site '%CloudName;' was more than two hours ago. Replication ...
  18. The latest version of the Provider is installed on this server and the server is registered.{0}Would you like to register ...
  19. The memory size on virtual machine '%DraVMName;' was changed from %OldValue; MB to %NewValue; MB during failover. In Hyper-V, ...
  20. The Microsoft Azure Recovery Services Agent isn't installed on the Hyper-V host server %HostName;. Install the agent on the ...
  21. The Microsoft Azure Site Recovery Provider might not be the latest version. Check the Provider error for more information. ...
  22. The Mobility service couldn't be installed on the virtual/physical machine. Either the Process Server is not available or ...
  23. The Mobility service on %HostName; hasn't communicated for more than %TimeoutThreshold; seconds. No protected items are affected. ...
  24. The Mobility service on %HostName; hasn't communicated for more than %TimeoutThreshold; seconds. No protected items are affected. ...
  25. The Mobility service on %HostName; hasn't communicated for more than %TimeoutThreshold; seconds. Replication of the following ...
  26. The Mobility service on %HostName; hasn't communicated for more than %TimeoutThreshold; seconds. Replication of these volumes ...
  27. The Mobility service on %HostName;(%IPAddress;) couldn't communicate with the process server at IP address: %Ip;, Port: %Port;, ...
  28. The older version of the scout agent could not be uninstalled from the virtual machine. The PS is down, the provided credentials ...
  29. The operating system (%VmOsType;) of the machine doesn't match the operating system (%MtOsType;) of the Master Target server ...
  30. The operation failed because replication information isn't up to date. The virtual machine has been added to different replication ...
  31. The operation failed because replication information isn't up to date. The virtual machine might have been enabled for protection ...
  32. The operation isn't supported by the current version '%CurrentVersionId;' of Microsoft Azure Recovery Services Agent installed ...
  33. The operation isn't supported by the current version '%VersionId;' of the Microsoft Azure Site Recovery Provider installed ...
  34. The operation timed out. The VMM/Hyper-V/Configuration server couldn't communicate with the vault, connection to the Hyper-V ...
  35. The operation to disable protection failed because the virtual machine data couldn't be removed after protection was disabled. ...
  36. The passive stamp details for the '%ServiceName;' service with stamp id '%StampId;' couldn't be retrieved from the Provisioning ...
  37. The process server hasn't received any replication data from source %SrcVolume; of host %SrcHostName; in the past %TimeInMinutes; ...
  38. The processor count on virtual machine '%DraVMName;' was changed from %OldValue; to %NewValue; during failover. In Hyper-V ...
  39. The properties of the virtual machine can't be configured. Ensure that the virtual machine is configured for protection successfully. ...
  40. The protection state for the replication group '%ReplicationGroupName;' managed by VMM '%VMMName;' couldn't be updated. No ...
  41. The recovery cluster to be used for failover of storage replication group '%ReplicationGroupName;' couldn't be determined. ...
  42. The recovery plan has invalid actions. Check that Automation runbooks have only been added to recovery plans that fail over ...
  43. The recovery point objective (RPO) value specified is out of range. Requested RPO value: %RpoValue; second(s). Minimum supported ...
  44. The recovery server has an existing virtual machine '%DraVMName;' with the same Hyper-V virtual machine ID. This might be ...
  45. The registration key has expired. Download a new registration key from Azure Site Recovery and select it. The downloaded ...
  46. The replication group '%ReplicationGroupName;' contains more logical units than expected, including:'%LogicalUnitName;'. ...
  47. The replication group '%ReplicationGroupName;' doesn't contain the logical unit '%LogicalUnitName;'. Check the replication ...
  48. The replication group cannot be removed as one or more objects such as cloud, VM, template, or host disk are associated with ...
  49. The replication group isn't in a protected state. The virtual machine couldn't be added to an unprotected replication group. ...
  50. The replication group of virtual machine %VirtualMachine; couldn't be changed from %ReplicationGroupName; to %NewReplicationGroupName;. ...
  51. The replication group was reassigned to a different cloud, but an attempt was made to enable protection for it an older cloud. ...
  52. The replication state for the primary virtual machine on the VMM/Hyper-V server is '%PrimaryState;' and '%RecoveryState;' ...
  53. The replication state for the primary virtual machine on the VMM/Hyper-V server is '%PrimaryState;' and '%RecoveryState;' ...
  54. The replication state of primary virtual machine '%VMName;' ('%ID;') on the VMM/Hyper-V server is '%PrimaryState;'. Operations ...
  55. The replication state of recovery virtual machine '%VMName;' ( '%ID;' ) on the VMM/Hyper-V server is '%RecoveryState;'. Operations ...
  56. The replication state of the virtual machine on the Hyper-V host isn't synchronized with the Microsoft Azure Site Recovery ...
  57. The requested operation '%Operation;' cannot be performed on the replication group '%Name;'as it does not have any storage ...
  58. The requested operation '%Operation;' cannot be performed on the replication group as it is not participating in a group ...
  59. The requested operation '%TaskDescription;' failed with status '%Status;'. Detailed error message: '%DetailedErrorMessage;'. ...
  60. The requested recovery point objective (RPO) isn't supported by the storage array. Requested RPO value: %RpoValue; second(s), ...
  61. The resynchronization cache folder for the replicating volumes %SrcHostName; (%SrcVolume;) => %DestHostName; (%DestVolume;) ...
  62. The RPO has exceeded the configured SLA threshold of %RPOSLAThreshold; seconds for protected volume %SrcHostName; %SrcVolume; ...
  63. The selected azure vm size %VMSize; is not supported by the subscription or location of storage account or affinity group. ...
  64. 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 ...
  65. The storage arrays are not managed by the same provider type and no Storage Replica capable Storage Spaces array is present ...
  66. The storage arrays couldn't be paired because storage array '%ArrayName;' that contains storage pool '%PoolName;' isn't a ...
  67. The storage logical unit '%LogicalUnitName;' couldn't be mounted as a CSV in cluster '%DRAClusterName;'. Virtual machines ...
  68. The storage pools couldn't be paired because storage array '%ArrayName;' is a SAN array and storage array '%TargetArrayName;' ...
  69. The storage provider was removed and re-added with an updated provider address in SCVMM. Keep the provider management address ...
  70. The subnet might not exist in the given Azure virtual network. Specify a valid subnet in the network and retry the operation. ...
  71. The subscription limit for the cloud service was reached. Maximum limit: %MaxHostedServiceCount;. Attempted: %AttemptedHostedServiceCount;. ...
  72. The subscription limit for the storage service was reached. Maximum limit: %MaxStorageServiceCount;. Attempted: %AttemptedStorageServiceCount;. ...
  73. The version of Microsoft Azure Recovery Services Agent installed couldn't be found on the Hyper-V host server %HostName;. ...
  74. The virtual machine %DraVMName; is in state %DraVmState;. Network settings can't be applied to the virtual machine in this ...
  75. The virtual machine %VMName; cannot be deployed outside of a cloud because it requires Hyper-V protection. Hyper-V protected ...