6.1
Table Of Contents
- Site Recovery Manager Installation and Configuration
- Contents
- About VMware Site Recovery Manager Installation and Configuration
- Updated Information
- Overview of VMware Site Recovery Manager
- Site Recovery Manager System Requirements
- Creating the Site Recovery Manager Database
- Site Recovery Manager Authentication
- Creating SSL/TLS Server Endpoint Certificates for Site Recovery Manager
- Installing Site Recovery Manager
- Site Recovery Manager and vCenter Server Deployment Models
- Site Recovery Manager in a Two-Site Topology with One vCenter Server Instance per Platform Services Controller
- Site Recovery Manager in a Two-Site Topology with Multiple vCenter Server Instances per Platform Services Controller
- Site Recovery Manager in a Single Site Topology with a Shared Platform Services Controller
- Prerequisites and Best Practices for Site Recovery Manager Server Installation
- Install Site Recovery Manager Server
- Connect the Site Recovery Manager Server Instances on the Protected and Recovery Sites
- Establish a Client Connection to the Remote Site Recovery Manager Server Instance
- Install the Site Recovery Manager License Key
- Site Recovery Manager Server Does Not Start
- Unregister an Incompatible Version of vSphere Replication
- Site Recovery Manager and vCenter Server Deployment Models
- Modifying and Uninstalling Site Recovery Manager
- Modify a Site Recovery Manager Server Installation
- Reconfigure the Connection Between Sites
- Break the Site Pairing and Connect to a New Remote Site
- Repair a Site Recovery Manager Server Installation
- Rename a Site Recovery Manager Site
- Uninstall Site Recovery Manager
- Uninstall and Reinstall the Same Version of Site Recovery Manager
- Upgrading Site Recovery Manager
- Information That Site Recovery Manager Upgrade Preserves
- Types of Upgrade that Site Recovery Manager Supports
- Upgrade Site Recovery Manager
- Order of Upgrading vSphere and Site Recovery Manager Components
- Prerequisites and Best Practices for Site Recovery Manager Upgrade
- In-Place Upgrade of Site Recovery Manager Server
- Upgrade Site Recovery Manager Server with Migration
- Configure and Verify the Upgraded Site Recovery Manager Installation
- Revert to a Previous Release of Site Recovery Manager
- Installing Site Recovery Manager to Use with a Shared Recovery Site
- Shared Recovery Sites and vCenter Server Deployment Models
- Limitations of Using Site Recovery Manager in Shared Recovery Site Configuration
- Site Recovery Manager Licenses in a Shared Recovery Site Configuration
- Install Site Recovery Manager In a Shared Recovery Site Configuration
- Use vSphere Replication in a Shared Recovery Site Configuration
- Install Site Recovery Manager Server on Multiple Protected Sites to Use with a Shared Recovery Site
- Install Multiple Site Recovery Manager Server Instances on a Shared Recovery Site
- Connect the Site Recovery Manager Sites in a Shared Recovery Site Configuration
- Use Array-Based Replication in a Shared Recovery Site Configuration
- Configure Placeholders and Mappings in a Shared Recovery Site Configuration
- Upgrade Site Recovery Manager in a Shared Recovery Site Configuration
- Index
n
Each Site Recovery Manager Server instance on the protected site and on the shared recovery site
requires its own database.
n
A single shared recovery site can support a maximum of ten protected sites. You can run concurrent
recoveries from multiple sites. See http://kb.vmware.com/kb/2119336 for the number of concurrent
recoveries that you can run with array-based replication and with vSphere Replication.
n
In a large Site Recovery Manager environment, you might experience timeout errors when powering on
virtual machines on a shared recovery site. See “Timeout Errors when Powering on Virtual Machines
on a Shared Recovery Site,” on page 74.
n
When connecting to Site Recovery Manager on the shared recovery site, every customer can see all of
the Site Recovery Manager extensions that are registered with the shared recovery site, including
company names and descriptions. All customers of a shared recovery site can have access to other
customers’ folders and potentially to other information at the shared recovery site. For information
about permissions in a shared recovery site setup, see Managing Permissions in a Shared Recovery Site
Configuration in Site Recovery Manager Administration.
Timeout Errors when Powering on Virtual Machines on a Shared Recovery Site
In a large Site Recovery Manager environment, you might encounter timeout errors when powering on
virtual machines on a shared recovery site.
Problem
When you power on virtual machines on a shared recovery site, you see the error message Error:Operation
timed out:900 seconds.
Cause
This problem can occur if a single vCenter Server instance manages a large number of virtual machines on
the shared recovery site, for example 1000 or more.
Solution
1 Increase the remoteManager.defaultTimeout timeout value on the Site Recovery Manager Server on the
recovery site.
For example, increase the timeout from the default of 300 seconds to 1200 seconds. For information
about how to increase the remoteManager.defaultTimeout setting, see Change Remote Manager Settings
in Site Recovery Manager Administration.
2 Go to C:\Program Files\VMware\VMware vCenter Site Recovery Manager\config on the
Site Recovery Manager Server host machine on the recovery site.
3 Open vmware-dr.xml in a text editor.
4 Set the timeout for reading from the vSphere Web Client.
Set the timeout to 900 seconds (15 minutes) by adding a line to the <vmacore><http> element.
<vmacore>
<http>
<defaultClientReadTimeoutSeconds>900</defaultClientReadTimeoutSeconds>
</http>
</vmacore>
5 Restart the Site Recovery Manager Server service.
Site Recovery Manager Installation and Configuration
74 VMware, Inc.