UI Translation

Azure Site Recovery

  1. The virtual machine %VMName; has Hyper-V replication enabled. Enabling Hyper-V Recovery Manager protection on this virtual ...
  2. The virtual machine '%DraVMName;' belongs to a recovery cluster ('%DRAClusterName;'). This isn't a cluster ('%ClusterNames;') ...
  3. The virtual machine '%DraVMName;' can't be protected because the checkpoint root location '%Path;' is not on logical units ...
  4. The virtual machine '%DraVMName;' can't be protected because the configuration file '%Path;' is not on logical units that ...
  5. The virtual machine '%DraVMName;' can't be protected because the swap file root location '%Path;' not on logical units that ...
  6. The virtual machine '%DraVMName;' could not be deleted since deletion in the state of '%ReplicationMode;':'%ReplicationState;' ...
  7. The virtual machine '%DraVMName;' couldn't be protected because it has one or more passthrough disks. This isn't supported. ...
  8. The virtual machine '%DraVMName;' has a virtual hard disk '%VhdPath;' which isn't located on the logical unit associated ...
  9. The virtual machine '%DraVMName;' has no virtual disks which are backed by replication group '%ReplicationGroupName;'. This ...
  10. The virtual machine '%DraVMName;' has virtual hard disk '%VhdPath;' on logical unit '%LogicalUnitName;' which isn't part ...
  11. The virtual machine '%DraVMName;' has virtual hard disk on logical unit '%LogicalUnitName;' which has an invalid CSV path ...
  12. The virtual machine '%DraVMName;' has virtual hard disk on logical unit '%LogicalUnitName;' which is not a cluster shared ...
  13. The virtual machine '%DraVMName;' host operating system is running an operating system earlier than Windows Server 2012. ...
  14. The virtual machine '%VMName;' in cloud/site '%CloudName;' needs to be resynchronized because of consecutive replication ...
  15. The virtual machine '%VmRoleName;' couldn't be created under deployment '%DeployementName;' and cloud service '%HostedServiceName;'. ...
  16. The virtual machine couldn't be shut down. The virtual machine is in a saved or paused state, an application is preventing ...
  17. The virtual machine information could not be retrieved. The agent on the source server is not responding or could not connect ...
  18. The virtual machine is on a Hyper-V host or cluster which isn't configured for protection. Go to JOBS view in Azure portal ...
  19. The virtual machine isn't in a replicating state. The state might be set to Resynchronization Required, Saved, Paused, or ...
  20. The virtual machine state in Microsoft Azure Site Recovery couldn't be verified because the VMM/Hyper-V server replication ...
  21. The virtual machines in the recovery plan and the replication group '%ReplicationGroupName;' don't match. Some virtual machines ...
  22. The virtual machines in the recovery plan and the replication group '%ReplicationGroupName;' don't match. Some virtual machines ...
  23. The virtualMachine %VirtualMachine; couldn't be joined to replication group %ReplicationGroupName; because another join operation ...
  24. The virtualMachine %VirtualMachine; couldn't be joined to replication group %ReplicationGroupName; because the virtual machine ...
  25. The virtualMachine %VirtualMachine; couldn't join the replication group %ReplicationGroupName; because it has one or more ...
  26. The VMM server and the Hyper-V host server are in different domains and there is no trust between the two domains. -Windows ...
  27. The VMM server certificate couldn't be imported into the certificate store. Retry the last action. If the VMM server was ...
  28. The VMM server couldn't find the virtual machine information that's required to establish trust between the primary and recovery ...
  29. The VMM server has incorrect protection configuration between the primary cloud '%DraPrimaryCloudName;' and the recovery ...
  30. The VMM server might not be able to find a Hyper-V host with the required rating. The recovery cloud might not include a ...
  31. The VMM server might not be able to find the target storage pool. The replica logical unit might already exist but has been ...
  32. The VMM service can't access the import or export path (%IRFolderPath;). Error:(%Message;). During cloud configuration, the ...
  33. The VMM service couldn't provide permissions for %NtAccountName; on %IRFolderPath;. Error: %Message;. During cloud configuration, ...
  34. The VMM service doesn't have ACL modify permissions on folder %IRFolderPath;. During protection configuration, the VMM service ...
  35. The VMM service doesn't have the required privileges to modify the permissions on the import and export paths specified for ...
  36. The VMM/Hyper-V server might not be able to communicate with Microsoft Azure Site Recovery. Check the Provider errors for ...
  37. The VMM/Microsoft Azure Site Recovery service couldn't find a Hyper-V host, or the server doesn't have Internet connectivity, ...
  38. There are no servers registered to the Azure Site Recovery vault. Atleast one server needs to be registered to perform this ...
  39. There's a version mismatch between the Provider version (%VersionId;) running on the primary server and the version (%RecoveryVersionId;) ...
  40. To begin reverse replication, trust must be established from the protected location to the protecting location. Verify that ...
  41. To ensure that the VMM server has a valid vault key, run the Provider installation wizard on the VMM server and paste in ...
  42. To ensure there are enough disk drives either disable protection of existing items or deploy a new master target server. ...
  43. To resolve the issue, either perform the planned failover again, or perform an unplanned failover if the primary site isn't ...
  44. Unable to import the service authentication certificate used for Hyper-V Recovery Manager services into the certificate store. ...
  45. Unable to retrieve vault information from Azure Site Recovery. This could be due to internet connection failure or Invalid/expired ...
  46. Usage: DRConfigurator.exe /r /friendlyname value /proxyaddress value /proxyport value /proxyusername value /proxypassword ...
  47. User role (%UserRoleId;) can't be found. User roles set on primary site virtual machines must also exist on the recovery ...
  48. Validate the IP address and port and check connectivity between the host and process server. If the issue persists contact ...
  49. Verify network connectivity between the process server and target servers. Check that there's adequate bandwidth to enable ...
  50. Verify that the recovery cloud contains at least one host running a compatible version of Windows with Hyper-V Replica enabled. ...
  51. Verify that the script exists in the required path. Check that exceptions are being handled correctly using try-catch blocks. ...
  52. Verify that the VMM service can access the import or export path. If the path is shared, ensure that the VMM service account ...
  53. Verify the replication state for the virtual machine in the Microsoft Azure Site Recovery vault, and retry the operation. ...
  54. Verify the virtual machine state, check that the VMM/Hyper-V server is available, and retry the planned failover. Or perform ...
  55. Virtual machine '%VmRoleName;' couldn't be started under deployment '%DeployementName;' and cloud service '%HostedServiceName;'. ...
  56. Virtual machine deployment '%DeploymentName;' couldn't be deleted because another operation is running on the virtual machine ...
  57. Virtual machine information couldn't be retrieved from the configuration server. Check the Provider errors for more information. ...
  58. Virtual machines '%VMNames;' were not found in Azure or could not be reached for the failover operation. This can happen ...
  59. Virtual machines protected to Azure will be encrypted. Encrypted data is decrypted during failover from the Windows Hyper-V ...
  60. Virtual machines protected to Azure will be encrypted. Encrypted data is decrypted during failover from the Windows Hyper-V ...
  61. VM has stale protection settings. You'll need to manually clear protection settings before you can enable protection again. ...
  62. VMM cannot migrate or clone the virtual machine (%VMName;) because the version (%TargetHostVSVersion;) of the virtualization ...
  63. VMM/Hyper-V/Configuration server '%VMMName;' might not be running, or it couldn't communicate with Microsoft Azure Site Recovery. ...
  64. Volume %DeviceName; offset: %OffsetToRead; bytes read: %BytesRead; bytes requested: %BytesRequested; couldn't be read on ...
  65. Wait until the recovery plan operations finish, and then save it as required. Don't navigate away from the Configure page ...
  66. You have the following versions installed: %DraVersions;. Each server must have the same version of the provider installed ...
Español (España)
Spanish (Spain) Français (France)
French (France) italiano
Italian 日本語
Japanese 한국어
Korean Português
Portuguese Русский
Russian English
English (United States)