Search the VMware Knowledge Base (KB)
View by Article ID

Performing a Recovery using the Web Client in VMware vCenter Site Recovery Manager 5.8 reports the error: Failed to connect Site Recovery Manager Server(s) (2093902)

  • 7 Ratings


When performing a Recovery using the Web Client in VMware vCenter Site Recovery Manager (SRM) 5.8, you experience these symptoms: 

  • Unable to see previously configured Array Managers, Protection Groups or Recovery Plans in the SRM plug-in in the vSphere Web Client
  • The protected site and recovery site vCenter servers are configured in Linked Mode
  • Unable to perform a recovery using the Web Client because there are no Recovery Plans visible in the user interface
  • The protected site is offline or the vSphere Web Client server is unable to communicate with the vCenter Server Inventory Service on the protected site
  • The vSphere Web Client displays an error similar to:

    Failed to connect Site Recovery Manager Server(s).
    Failed to retrieve pairs from Site Recovery Manager Server at https://<vc hostname>:8095/dr.


When vCenter Server is configured in Linked Mode and the protected site is offline with inventory service offline, no Array Manager. Protection Groups or Recovery Plans are displayed when the protected site is offline.

Impact: The user is unable to perform a recovery at the recovery site, in the event of a DR scenario.


This is a known issue affecting VMware vCenter Site Recovery Manager (SRM) 5.8.0.
This issue is resolved in SRM 5.8.1, available at VMware Downloads. For more information, see the Site Recovery Manager 5.8.1 Release Notes.
If you are unable to upgrade to SRM 5.8.1 or later, work around this issue by using one of these options to perform the recovery:
  • Use PowerCLI to do the SRM recovery directly from the command line.

    Use PowerCLI to perform the Recovery using the SRM API.  For more information, see Automating Failover with SRM and PowerCLI
    The attached can be used to automate the failover process.
  1. Download and install PowerCLI 5.8, available at VMware download center.
  2. PowerCLI can be installed on the SRM server, the vCenter server or a client machine. The server where PowerCLI is installed must be able to access the SRM server over port 9007.
  3. Download the attached file and extract the Recovery.ps1 file on the server where you installed PowerCLI to the C:\Program Files (x86)\VMware\Infrastructure\vSphere PowerCLI directory. Adjust this path if you have installed PowerCLI to a different location.
  4. Launch PowerCLI by navigating to Start > All Programs > VMware > VMware vSphere PowerCLI > VMware vSphere PowerCLI.
  5. Run this command to execute the script:


  6. Follow the prompts to initiate the SRM Recovery.

    Note: This script does not handle your recovery plan, if there are prompts for user intervention. This does not provide a way to dismiss the prompts to continue the failover.
  • Temporarily disable vCenter Server Linked Mode.

    Perform these steps to break the vCenter Server Linked Mode configuration on the recovery site vCenter Server:
  1. On the recovery site vCenter Server, navigate to Start > All Programs > vCenter Server Linked Mode Configuration.
  2. Click Next, select Modify Linked Mode configuration and then click Next.
  3. Ensure that the checkbox Isolate this vCenter Server instance from Linked Mode group is selected and then click Next.
  4. Click Continue to isolate the vCenter Server.
  5. When the wizard is complete, check that the Site Recovery Manager service is still running and start it if necessary.
  6. Log out of the vSphere Web Client and again log in. You should now see the Array Managers, Protection Groups and Recovery Plans and should be able to run the Recovery.

Additional Information

For more information about using vCenter Server 5.5 in Linked mode, see the Creating vCenter Server Linked Mode Groups section in the vSphere 5.5 Installation and Setup guide.


Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.


  • 7 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)

Please enter the Captcha code before clicking Submit.
  • 7 Ratings