UI Translation

Azure Site Recovery

  1. A certificate with subject name '%DRACertificateSubjectName;' couldn't be generated. Retry the last action. If the VMM server ...
  2. A cluster without HyperV cluster broker role enabled or HyperV cluster broker with invalid Client Access Point name found. ...
  3. A configuration operation of adding to cloud or connecting to VM network couldn't complete during the test failover of virtual ...
  4. A connection to the storage account '%StorageAccountName;' failed because of invalid credentials or an invalid storage account ...
  5. A consistency file replication job failed. Date: %Date; Configuration server: %ServerIP; Error: %ErrorMessage; code: %ExitCode; ...
  6. A default network adaptor has been selected for use during failover. Verify settings and check that the select default adapter ...
  7. A disk couldn't be added to virtual machine '%VMRoleName;' in service '%HostedServiceName;'. Azure error message: '%ErrorMessage;'. ...
  8. A failure threshold for processing an incoming event from Microsoft Azure Site Recovery Provider was reached, and the event ...
  9. A library share couldn't be located on the target VMM server for storing a virtual machine template for classification mapping. ...
  10. A protection file replication job failed. Date: %Date; Configuration server: %ServerIP; Error : %ErrorMessage; code : %ExitCode; ...
  11. A recovery file replication job failed. Date: %Date; Configuration server: %ServerIP; Error: %ErrorMessage; code : %ExitCode; ...
  12. A recovery point objective (RPO) value cannot be specified as the RPO value type (discrete or range) is not exposed by the ...
  13. A serious error occurred for target %DeviceName; on %HostName;(%IPAddress;), because resynchronization bitmaps are invalid. ...
  14. A target cluster with ID '%ObjectId;' couldn't be found in VMM. Storage logical units and recovery virtual machines that ...
  15. A type network of type %NetworkIsolationType; couldn't be created because the VM network of the replica virtual machine doesn't ...
  16. A virtual machine could not be added to the replication group '%ReplicationGroupName;' as replication relationship is reversed. ...
  17. A virtual machine is trying to join a different replication group from that which it initially belonged to. Remove the virtual ...
  18. A virtual machine network couldn't be attached during test failover of virtual machines in replication group %ReplicationGroupName;. ...
  19. A virtual machine on the Hyper-V host has a replication state that isn't synchronized with the Microsoft Azure Site Recovery ...
  20. A VM network couldn't be created for test failover using a logical network of type %NetworkIsolationType; because there's ...
  21. A VM network couldn't be created for test failover using a logical network of type No Isolation because an existing VM network ...
  22. Account (%NtAccountName;) couldn't access folder %IRFolderPath;. The required permissions couldn't be granted. During protection ...
  23. An action from Microsoft Azure Site Recovery Provider to delete an adapter on virtual machine %VMName; (%ID;) couldn't be ...
  24. An error occurred when creating the retention folder %DirLocation; on %HostName;(%IPAddress;). Error: %Error;. Replication ...
  25. An initial replication notification event was received but was ignored because initial replication has since been restarted. ...
  26. An unplanned failover operation might be in progress, or the VMM server can't communicate with the Microsoft Azure Site Recovery ...
  27. An update from Microsoft Azure Site Recovery Provider for virtual machine %VMName; (%ID;) adapter couldn't be processed. ...
  28. An update from Microsoft Azure Site Recovery Provider for virtual machine %VMName; (%ID;) couldn't be processed. Failure ...
  29. Automatically configuring Hyper-V Replica broker resource on a cluster with a static IP network adapter, or if all cluster ...
  30. Automatically configuring Hyper-V Replica broker resource on a cluster with a static IP network adapter, or on a cluster ...
  31. Automatically configuring Hyper-V Replica broker resource on a cluster with a static IP network adapter, or without all cluster ...
  32. Automation runbook '%RunbookName;' stopped running because the Azure Automation Account was not reachable. It is either deleted ...
  33. Azure Site Recovery expects the primary virtual machine '%VMName;' ('%ID;') to be in state '%ExpectedPrimaryState;', but ...
  34. Azure Site Recovery expects the recovery virtual machine '%VMName;' ('%ID;') to be in state '%ExpectedRecoveryState;', but ...
  35. Azure Site Recovery provider will be associated with Hyper-V. You can enable protection for VMs under Hyper-V on this machine ...
  36. Azure Site Recovery provider will be associated with InMage. You can enabled protection for VMs under CS server on this machine ...
  37. Blob %Blob; couldn't be deleted because it has snapshots associated with it, and it's being used by another resource. This ...
  38. Blob %Blob; couldn't be deleted. The blob is being used by another resource, or another operation is currently running on ...
  39. Cannot establish replication relationship for replication group %Name; because a target storage logical unit has not been ...
  40. Cannot establish replication relationship for replication group %Name; because a target storage pool has not been supplied ...
  41. Cannot establish replication relationship for replication group %Name; because no storage logical units have been supplied. ...
  42. Cannot establish replication relationship for replication group %Name; because no target replication group has been supplied. ...
  43. Cannot establish replication relationship for replication group %Name; because the source storage array does not have a replica ...
  44. Changing protection requirement directly is not allowed for the virtual machine %VMName; as it is on the replication group ...
  45. Check if the Azure Automation account exists. Ensure that the Service is up via the Azure service dashboard. Retry the operation ...
  46. Check if the volumes are online and accessible. Also check if they were mounted earlier and now have been unmounted. No action ...
  47. Check network connectivity between the source and process servers. Check that the Mobility service (InMage Scout VX Agent ...
  48. Check that the date and timezone settings on the device from which you are accessing Microsoft Azure Site Recovery match ...
  49. Check that the Mobility service (InMage Scout VX Agent - Sentinel/Outpost) is running on %HostName; and that the host is ...
  50. Cleanup couldn't be performed on the recovery side because no replication group information was available in Microsoft Azure ...
  51. Cloud service '%HostedServiceName;' couldn't be deleted. The cloud service is in use, or another operation is currently running ...
  52. Cloud/site information couldn't be found. The cloud/site may have been unpublished from SCVMM/Azure Site Recovery Manager ...
  53. Configure one disk with the setting 'Contains the operating system for the virtual machine' in the Hardware Configuration ...
  54. Configure protection for the cloud/site, and retry the operation. 2. Manually clear protection settings of the virtual machine ...
  55. Configure the Operating System settings in the General tab of the virtual machine properties in the VMM/Azure Site Recovery ...
  56. Could not determine Client Access Point for the %BrokerResourceName; resource on the cluster %HostClusterName; as %BrokerResourceName; ...
  57. Could not determine Client Access Point for the %BrokerResourceName; resource on the cluster %HostClusterName; as %BrokerResourceName; ...
  58. Could not migrate reserved virtual machine %VMName; to destination host %Name; because destination host is not part of virtual ...
  59. Could not migrate reserved virtual machine %VMName; to destination host %Name; because destination host is not zoned to storage ...
  60. Couldn't create snapshot for the logical units or failed to create test virtual machines. Check the Provider errors for more ...
  61. Couldn't verify whether the current host server or cluster certificate is signed with the current VMM signing certificate. ...
  62. Delete the virtual machine from the Microsoft Azure Site Recovery vault and enable protection for it again using the VMM ...
  63. Disable protection on the virtual machine and enable it again. This will rerun initial replication of the virtual machine. ...
  64. Disabling protection for the virtual machine didn't remove the replication settings from the replica virtual machine. Check ...
  65. Disk '%DiskName;' under virtual machine'%VmRoleName;' and cloud service '%HostedServiceName;' couldn't be attached. Azure ...
  66. Do one of the following and retry the test failover: 1. Provide a different logical network to use for the test. 2. Complete ...
  67. Do one of the following and retry the test failover: 1. Specify a different logical network to use for the test failover. ...
  68. Either (1) the virtual machine isn't located in a protected VMM cloud/site, or (2) The virtual machine is already protected, ...
  69. Either a connection couldn't be established to host server '%VMHostID;' or the virtual machine '%VMName;' ('%ID;') in cloud/site ...
  70. Either completion of test failover was left unattended for more than two weeks, or the operation failed because of an internal ...
  71. Either completion of the manual action was left unattended for more than three days, or the operation failed because of an ...
  72. Either Hyper-V host cluster %DRAClusterName; contains at least one static network adapter, or no connected adapters are configured ...
  73. Either replication traffic couldn't be sent successfully to the recovery server, or the recovery server couldn't process ...
  74. Either replication traffic couldn't be sent to the recovery server, or the recovery server couldn't process the replication ...
  75. Either the current replication state of the virtual machine doesn't support this operation, the recovery site configuration ...
Español (España)
Spanish (Spain) Français (France)
French (France) italiano
Italian 日本語
Japanese 한국어
Korean Português
Portuguese Русский
Russian English
English (United States)