The components that make up the VMware Site Recovery service—vCenter Server, vSphere Web Client, Site Recovery Manager Server, vSphere Replication Appliance, and vSphere Replication Server—must have different ports open. You must ensure that all required network ports are open for VMware Site Recovery to function properly. Site Recovery Manager and vSphere Replication do not have public IP addresses. You must use a VPN or Direct Connect to access the HTML 5 user interface. We recommend that you use the private IP address as the resolution address for the vCenter Server FQDN if you are using a VPN. Site Recovery Manager does not fully support policy-based IP customization for Linux VMs with multiple NICs if the NICs have mixed DHCP and static IP settings. Site Recovery Manager only adjusts NICs with static IP addresses for which there is a corresponding IP subnet mapping rule and can remove some configuration settings for other NICs configured with DHCP. A known issue with this scenario has been observed for Red Hat Enterprise Linux 6.x/7.x and CentOS 6.x/7.x, where SRM customization removes the /etc/sysconfig/network-scripts/ifcfg-ethX files for DHCP-configured NICs and successfully adjusts the rest with static IP settings based on the corresponding IP subnet mapping rule. Site Recovery Manager 8.2 is compatible with vSphere 6.0 Update 3, vSphere 6.5, vSphere 6.5 Update 1, vSphere 6.5 Update 2, vSphere 6.7, vSphere 6.7 Update 1, vSphere 6.7 Update 2 and supports ESXi versions supported by vCenter Server 6.7. To use Site Recovery Manager, some ports must be open. Workaround: Rebuild your recovery plan, reconfigure the desired recovery settings, and re-export your configuration. Do not delete recovery plans if you want to export and import virtual machine recovery settings. If you are deploying additional vSphere Replication servers, ensure that the subset of ports required by the vSphere Replication servers is open on those servers.
If you have a virtual machine with multiple disks that vSphere Replication replicates to different vSphere Virtual Volumes datastores at the secondary site, a test restore operation fails. During a test recovery, vSphere Replication attempts to create linked clones for vSphere Virtual Volumes replica disks, but the operation fails because linked clones are not supported on different datastores. vSphere Replication creates linked clones only during a test recovery. Scheduled recovery, unplanned recovery, and reprotection completed successfully. Workaround: There is no workaround for incorrect object names in inventory mappings. Review the historical report of the failed test or recovery workflow that led to the creation of placeholder mappings. For example, if you know the inventory of the protected site, you can determine the datacenter, folder, and resource pool of the protected site that contained the protected virtual machine that could not be restored because of a missing mapping. Specific ports must be open for Site Recovery Manager Server instances on protected and recovery sites. The socket::getaddrinfo($server, $port) API fails with the error “nodename nor servname provided or not known”. Site Recovery Manager cannot detect older versions of VMware Tools installed on virtual machines that reside in vSphere Virtual Volumes storage on the first restore attempt. You may encounter the following errors, depending on the version of VMware Tools installed on the restored virtual machines.
Vim::Fault::OperationNotSupportedByGuest: “The guest operating system does not support the operation.” Vim::Fault::InvalidGuestLogin: “Guest OS authentication failed with the specified credentials. Site Recovery Manager requires certain ports to be open on vCenter Server, Platform Services Controller, and ESXi Server. If you include protected virtual machines in recovery plans, delete all recovery plans that contain those virtual machines, and export your configuration using the VMware Site Recovery Manager 8.2 Configuration Import/Export tool, the virtual machine recovery settings for those virtual machines are exported, but you cannot import them later. When you try to import your settings, you see errors such as: Error importing VM settings for servers with GUID `6f81a31e-32e0-4d35-b329-783933b50868`. The rest of the exported configuration is imported correctly. Site Recovery Manager uses network ports that you can configure to communicate with clients and other servers. You must ensure that firewalls do not block the ports used by Site Recovery Manager. For an up-to-date list of supported storage arrays and supported SRAs, refer to the Site Recovery Manager Storage Partner Compatibility Guide. The components that make up a Site Recovery Manager deployment—vCenter Server, vSphere Client, Site Recovery Manager Server, vSphere Replication Appliance, and vSphere Replication Server—must have different ports open.
You must ensure that all required network ports are open for Site Recovery Manager to function properly. Site Recovery Manager Server communicates with Platform Services Controller, vCenter Server, ESXi hosts, and arrays at the local site. You must ensure that network firewall policies allow traffic to the network ports of all components of the local site. For a list of default ports used by all VMware products, see kb.vmware.com/kb/1012382. If you use Site Recovery Manager to protect datastores on arrays that support thin swapping, such as Clariion, performing disaster recovery in the event of a partial failure of the protected site or performing a forced restore might fail when the recovery plan is rerun to complete operations on the protected site. Such an error occurs when the protected site is back online, but Site Recovery Manager cannot shut down the protected virtual machines. This error typically occurs when some arrays make LUNs protected read-only, preventing ESXi from completing I/O for powered on protected virtual machines. When you try to export the report from the Recovery Plan History or Recovery Steps screen using the MS Edge browser, you get the following error in the Developer Console. XML5610 ERROR: Quotation marks expected.
Error error: Invalid argument. This is a known Microsoft Edge browser issue with XSLTProcessor, which is used to convert server XML to HTML. The Site Recovery user interface may inadvertently attempt to connect to a transitively known Platform Services Controller from a paired site, but may not be relevant or accessible to Site Recovery Manager or vSphere Replication at the current site. For more information, refer to the appropriate troubleshooting sections in the Site Recovery Manager 8.2 Administrator`s Guide. If you deployed Site Recovery Manager and vCenter Server in Enhanced Linked Mode and run the Site Recovery Manager installer in edit mode, the Site Recovery Manager solution users are re-created, which requires a reconfiguration of the SRM partition. Workaround: Start Site Recovery Manager Server and disable virtual machine recovery. The following versions of the recovery plan suggest in the same step Configure storage for the same virtual machine with the error The specified key, name, or identifier already exists. If you look in the vCenter Server inventory, you see two virtual machines with the same name as the failed virtual machine, one of which is in the Discovered Virtual Machines folder.
