Azure Site Recovery

  1. Either the primary server couldn't send replication traffic to the recovery server, or replication was paused on the recovery ...
  2. Either the script location couldn't be reached, or you don't have the required permissions to run the script. There might ...
  3. Either the virtual machine couldn't be found on the recovery server, or check the provider error for additional information. ...
  4. Either the virtual machine is in a saved or paused state and couldn't be shut down, or virtual guest services aren't enabled ...
  5. Either the virtual machine is in a state which doesn't support test failover, or check the Provider errors for more information. ...
  6. Either the virtual machines were deleted, protection for them was disabled, or initial replication is in progress for one ...
  7. Encryption certificate with thumbprint (%Thumbprint;) is missing from (%DRAHostName;) host. Please install encryption key ...
  8. Ensure that at least one host in the cloud is zoned to the storage array before you enable protection for the virtual machine. ...
  9. Ensure that Mobility Service (InMage Scout Application Service) is running on all the protected VMs in the plan. If this ...
  10. Ensure that network connectivity exists between the Source server and the Process server. Check to see if the Mobility service ...
  11. Ensure that replication is in progress. Verify that source, process, and Master Target servers are available and connected ...
  12. Ensure that replication is in progress. Verify that source, process, and target servers are available and connected to network. ...
  13. Ensure that retention volume exists, that it's accessible, and that write operations are allowed. If an antivirus software ...
  14. Ensure that the configuration server is running, server is connected to the network. Resolve the issue and retry the operation ...
  15. Ensure that the host server is included in the recovery cloud. Verify that the replica virtual machine appears in the VMM ...
  16. Ensure that the latest version of the Provider is installed. If the replica virtual machine already exists, remove it. If ...
  17. Ensure that the Master Target's retention drive has sufficient free space, Target volumes are mounted and target server is ...
  18. Ensure that the Mobility Service (InMage Scout Application Service) is running on %HostName; and that the host is connected ...
  19. Ensure that the Mobility service (InMage Scout Application Service) is running on %HostName; and that the host is connected ...
  20. Ensure that the Mobility Service (InMage Scout VX Agent - Sentinel/Outpost) is running on %HostName; and that the host is ...
  21. Ensure that the Mobility service on Master Target server is running, server is connected to the network. Resolve the issue ...
  22. Ensure that the Mobility service(InMage Scout VX Agent - Sentinel/Outpost, InMage Scout Application Service) is running on ...
  23. Ensure that the Mobility Services (InMage Scout VX Agent - Sentinel/Outpost, InMage Scout Application Service) are running ...
  24. Ensure that the Mobility services (InMage Scout VX Agent - Sentinel/Outpost, InMage Scout Application Service) are running ...
  25. Ensure that the process server services (cxprocessserver, tmansvc, INMAGE-AppScheduler, InMage System Job Service, InMage ...
  26. Ensure that the protecting location is ready and accessible over the network from the protected location. Resolve the issue, ...
  27. Ensure that the script is in the specified location, and that it has the necessary permissions to run. If the script isn't ...
  28. Ensure that the snapshot interval isn't set to non-zero if the recovery points setting is zero. Then retry the operation. ...
  29. Ensure that the VMM/Hyper-V server is connected, that the VMM/Microsoft Azure Site Recovery service on the server is running, ...
  30. Ensure that Windows PowerShell remoting is enabled for the Hyper-V host server and is accessible from the VMM Server to view ...
  31. Ensure VMware tools is running on the virtual machine, disable protection on this protected item and try the enable protection ...
  32. Ensure you have the latest versions of the Mobility service and process server that are supported by the configuration server. ...
  33. Extend the disk to increase its size (http://go.microsoft.com/fwlink/?LinkID=525316), or free up the space on the volume ...
  34. Extend the retention drive to increase it's capacity or free up the space by deleting unwanted files or stale retention files. ...
  35. Failback for the virtual machine (ID: %HyperVVmId;) didn't succeed, or it was canceled outside the Microsoft Azure console. ...
  36. Failed to install registration certificate. Make sure you have appropropriate permissions to access machine certificate store. ...
  37. Failed to resolve the protection unit of the protected virtual machine %VMName; based on recovery point objective %RecoveryPointObjective;], ...
  38. Failover couldn't be started for the physical or virtual machine '%VmRoleName;'. The machine name contains unsupported characters. ...
  39. File system used blocks information at block number: %Start;, count requested: %Count;, for volume %DeviceName; couldn't ...
  40. Fix any issues in the Event Viewer logs (Applications and Service Logs - MicrosoftAzureRecoveryServices) on the Hyper-V host ...
  41. Fix any issues in the Event Viewer logs (Applications and Service Logs - MicrosoftAzureRecoveryServices) on the Hyper-V host ...
  42. Fix any issues in the Event Viewer logs (Applications and Service Logs - MicrosoftAzureRecoveryServices) on the Hyper-V host ...
  43. Fix any issues in the Event Viewer logs (Applications and Service Logs - MicrosoftAzureRecoveryServices) on the Hyper-V host ...
  44. Fix any virtual machine state issues in the Hyper-V Manager console, and fix any Hyper-V host errors. Then retry the operation. ...
  45. Fix the virtual machine state by enabling resynchronization, or resume the replication from the Hyper-V Manager console and ...
  46. For the missing subnets on the primary VM network, the first available subnet on the recovery VM network will be configured ...
  47. Go to the virtual machine properties page to select the network adapters to be used or to increase the role size of this ...
  48. If the job was running for a long time, check whether there's a related job currently in progress. If there is one, wait ...
  49. If the key isn't working download a new registration key from the quick start page in the Azure Site Recovery portal and ...
  50. If the recovery site virtual machine is available, trigger a failover of the virtual machine or remove the virtual machine ...
  51. If the source is experiencing high change rate, please wait for the change rate to return to normal for the consistency points ...
  52. If the volume is Resynchronizing, please wait for the volume to reach the Ok replication status for the recovery window information ...
  53. If you recently added a network adapter, configuration settings might not be updated with the latest information. Try the ...
  54. If you're using offline initial replication, verify that the host has the required permissions to access the offline import ...
  55. In the VMM database, the subscription ID for the provider for Hyper-V Recovery Manager is not valid. The subscription ID ...
  56. Information about '%DeploymentName;' deployment in hosted service '%HostedServiceName;' couldn't be retrieved. The deployment ...
  57. Information about virtual machine deployment '%DeploymentName;' couldn't be retrieved. The deployment was deleted, or it's ...
  58. Information about virtual machine disk '%DiskName;' couldn't be retrieved. The disk was deleted, or it's currently inaccessible. ...
  59. Initial replication for the virtual machine (ID: %HyperVVmId;) failed, or it was canceled outside the Microsoft Azure console. ...
  60. Initiate the failover on the virtual machine from Microsoft Azure Site Recovery, or retry the operation from the Hyper-V ...
  61. Invalid input when building disk resource. Both replication group %RGName; and recovery point objective %RecoveryPointObjective; ...
  62. Kerberos authentication isn't supported by the current version '%VersionId;' of the Provider installed on VMM/Hyper-V server. ...
  63. Low disk space under cache folder %DirLocation; on host %HostName;(%IPAddress;). Volume capacity (bytes): %VolumeSize; Free ...
  64. Make sure that the Hyper-V Replica Broker resource is dependent on a Network Name resource which was acting as its Client ...
  65. Make sure that the Hyper-V Replica Broker resource is dependent on a single Network Name resource which was acting as its ...
  66. Make sure the volume is accessible. You can use chkdsk (dd for linux) in read-only mode to check for errors or the Event ...
  67. Make sure the volume is accessible. You can use chkdsk (dd for linux) in read-only mode to check for errors or the Event ...
  68. Make sure virtual machines are committed and reverse replicated. If they're not replicating, resynchronize them in the Hyper-V ...
  69. Make sure you have enough bandwidth between the process and target servers to enable a drain of differential synchronization ...
  70. Make sure you have enough bandwidth between the process and target servers to enable a drain of resynchronization cache folder. ...
  71. Manually update the name of the target Azure virtual machine in the Configure page for the machine, and retry the operation. ...
  72. Microsoft update is already opted in. To turn Microsoft Update off please change Microsoft update settings in Control Panel. ...
  73. Microsoft Update offers security and important updates for Windows and other Microsoft software. Including Microsoft Azure ...
  74. Migrate the recovery VM to a host with version newer than or equal to %TargetHostVSVersion; or select the most suitable host ...
  75. More than 15 minutes of logs are pending and not applied for virtual machine '%VMName;' in cloud/site '%CloudName;'. Replication ...