Azure Site Recovery

  1. More than 20% of the replication cycles for virtual machine '%VMName;' in cloud/site '%CloudName;' have been missed. Replication ...
  2. More than 24 hours of logs are pending and not applied for virtual machine '%VMName;' in cloud/site '%CloudName;'. Replication ...
  3. More than 30 minutes of logs are pending and not applied for virtual machine '%VMName;' in cloud/site '%CloudName;'. Replication ...
  4. More than 60 minutes of logs are pending and not applied for virtual machine '%VMName;' in cloud/site '%CloudName;'. Replication ...
  5. More than two replication cycles were missed for virtual machine '%VMName;' in cloud/site '%CloudName;'. Replication traffic ...
  6. Multi VM consistency cannot be enabled as there are protected Linux physical or virtual machines in this protection group. ...
  7. Network adapters on the primary virtual machine ('%VMNics;') aren't synchronized with Microsoft Azure Site Recovery vault. ...
  8. Network adapters on the recovery virtual machine ('%VMNics;') aren't synchronized with the Microsoft Azure Site Recovery ...
  9. No communication from Mobility service on %HostName; since more than %TimeoutThreshold; seconds. Replication of the following ...
  10. No communication from Mobility service on %HostName; since more than %TimeoutThreshold; seconds.Replication of the following ...
  11. No site with the specified site ID - %SiteId; exists in Microsoft Azure Site recovery. Ensure the site is created before ...
  12. No synchronization percentage is available on the replicating logical unit '%LogicalUnitName;'. Initial replication can't ...
  13. On the VMM/Hyper-V/Configuration server, restart the VMM/Microsoft Azure Site Recovery service to restart the failed job. ...
  14. One or more jobs on VMM/Hyper-V/Configuration server '%Name;' failed after the VMM/Hyper-V/Configuration server was upgraded ...
  15. One or more logical units are already part of VMM replication group '%ReplicationGroupName;'. If you moved the logical units ...
  16. One or more test virtual machines created for test failover of replication group %ReplicationGroupName; couldn't be started. ...
  17. One or more virtual machines ('%VMNames;') managed by Microsoft Azure Site Recovery aren't members of replication group '%ReplicationGroupName;'. ...
  18. Protection can't be enabled with the virtual machine in its current state. Check the Provider errors for more information. ...
  19. Protection could not be disabled on the virtual machine. The agents on the PS or MT are unable to reach the Configuration ...
  20. Protection could not be enabled on the virtual machine. Disable protection failed with provider error: '%ProviderError;'. ...
  21. Protection could not be enabled on the virtual machine. The agent on the MT is not running or there are connectivity issues ...
  22. Protection couldn't be enabled because multiple hosts containing virtual machines with same Hyper-V ID %DRAVmId; exist in ...
  23. Protection couldn't be enabled because multiple virtual machines with the same Hyper-V Id %DRAVmId; exist on host %HostName;. ...
  24. Protection couldn't be enabled on the virtual machine because it's located in a cluster but isn't configured as highly available. ...
  25. Protection couldn't be enabled on the virtual machine because the virtual machine is in a cluster but isn't configured as ...
  26. Protection for a newly added Hyper-V host or cluster couldn't be configured. Check the Provider error for more information. ...
  27. Protection for replication group '%ReplicationGroupName;' couldn't be disabled because it contains one or more protected ...
  28. Protection for replication group '%replicationGroupName;' couldn't be enabled because storage pool '%PoolName;' isn't managed ...
  29. Protection for replication group '%replicationGroupName;' couldn't be enabled because the array '%ArrayName;' isn't paired ...
  30. Protection for replication group '%ReplicationGroupName;' in cloud '%CloudName;' couldn't be enabled because it's already ...
  31. Protection for the replication group '%ReplicationGroupName;' couldn't be enabled because it doesn't contain any logical ...
  32. Protection for the replication group '%ReplicationGroupName;' couldn't be enabled because it's no longer in the cloud '%CloudName;'. ...
  33. Provided Registration key requires higher version of provider to be installed. Please download latest provider from Azure ...
  34. Proxy could not be set for the Microsoft Azure Recovery Services Agent. You can setup the proxy manually by running the Set-OBMachineSettings ...
  35. Refresh storage provider in SCVMM and then try again. Also ensure that the latest version of the storage provider that supports ...
  36. Registration of the provider for Hyper-V Recovery Manager is not done, or registration information is not valid. The initialization ...
  37. Registration was successful but setup failed to start Microsoft Azure Site Recovery Service on this machine. Please try starting ...
  38. Registration was successful but setup failed to start System Center Virtual Machine Manager on this machine. Please try starting ...
  39. Remove the virtual machine from the Microsoft Azure Site Recovery vault, and then re-enable protection for the virtual machine. ...
  40. Removing replication group or switching with replication group %RGName; directly is not allowed for the virtual machine %VMName;]. ...
  41. Repairing replication isn't supported with the virtual machine in its current state. Check the Provider errors for more information. ...
  42. Replication capabilities exposed by storage array '%StorageArrayName;' don't indicate a supported means for enabling replication ...
  43. Replication errors occurred for virtual machine '%VMName;' in cloud/site '%CloudName;' because of issues with connectivity ...
  44. Replication for following volume is paused due to resize of source Device(s) %SrcVolume;. Source host: %SrcHostName; Source ...
  45. Replication for following volume is paused due to resize of source LUN of ID %LunId;. Source host: %SrcHostName; Source IP ...
  46. Replication for following volume is paused due to resize of source volume %SrcVolume; from %OldVolumeSize; to %NewVolumeSize;. ...
  47. Replication for the source volume was paused because of insufficient disk space on retention volume %VolumeName;. Source ...
  48. Replication is already enabled for group '%ReplicationGroupName;' and it's acting as a target replica group. You can only ...
  49. Replication is already enabled for replication group '%ReplicationGroupName;' and it's acting as a source group. Replication ...
  50. Replication settings for one or more protected items associated with this protection group couldn't be updated. Check the ...
  51. Replication settings for one or more virtual machines associated with this cloud/site couldn't be updated. Check the Provider ...
  52. Resolve any differences between the files. Then, disable and re-enable protection for the virtual machine, and restart the ...
  53. Resolve any outstanding virtual machine failover errors and ensure that failover completed. Then try the data encryption ...
  54. Resolve the issue by creating an IP address pool for the VM network that corresponds to the replica virtual machine. Then ...
  55. Resynchronization is required for replicating volumes %SrcHostName; %SrcVolume; -> %DestHostName; %DestVolume; for plan %PlanName;]. ...
  56. Resynchronization was paused either manually, or due to problems with virtual machine '%VMName;' in cloud/site '%CloudName;'. ...
  57. Resynchronize the virtual machine to fix the state, or resume replication from the Hyper-V Manager console. Then retry the ...
  58. Retry the commit operation. If this doesn't resolve the issue, try to complete the commit operation in the Hyper-V Manager ...
  59. Reverse replication fails if the protecting location isn't ready to receive the replication data from the protected location. ...
  60. Runbook '%RunbookNames;' has additional parameters which aren't available during failover. Available parameters: '%ParameterNames;'. ...
  61. Running out of free space on retention folder : %RetentionFolderName; Free Space : %FreeSpace; on %HostName;(%IPAddress;). ...
  62. See "Installing Microsoft Azure Site Recovery Provider" in the Microsoft Azure Site Recovery Provider Setup help for information ...
  63. Select the virtual machine in Azure Site Recovery's Protected Items view and manually configure the name of the target Azure ...
  64. Setup failed to stop Microsoft Azure Site Recovery Service on this machine. Please try manually shutting down the service ...
  65. Setup failed to stop System Center Virtual Machine Manager on this machine. Please try manually shutting down the service ...
  66. Setup was unable to access {0} registry key in {1} registry hive. Please ensure the key exists and is accessible by the user. ...
  67. Specify how the Provider running on the server connects to the Azure Site Recovery portal. If you're using a proxy that requires ...
  68. Specify where you want to install the Microsoft Azure Site Recovery Provider. This setup will install Azure Site Recovery ...
  69. Target volume %DestDeviceName; couldn't be unmounted on %HostName;(%IPAddress;). Replication won't continue with this target ...
  70. The application-consistent snapshot interval can't be a non-zero value when the additional recovery points value is zero. ...
  71. The application-consistent snapshot interval is set to a non-zero value when the additional recovery points value is set ...
  72. The array '%StorageArrayName;' does not expose the right set of capabilities to indicate whether target elements or target ...
  73. The array(s) ('%ArrayName;') are not Storage Spaces array. Clouds with Storage Spaces array can be paired using Storage Replica ...
  74. The Azure virtual network might not exist. Specify a valid virtual network for the virtual machine and retry the operation. ...
  75. The cloud operation could not be completed as the storage array '%ArrayUniqueId;' is found to be associated with more than ...