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
After you have installed Site Recovery Manager, if vCenter Server migrates to a different
Platform Services Controller or if the address of the Platform Services Controller changes, you can
reconfigure Site Recovery Manager with the new Platform Services Controller address. For example, you
can change from an embedded Platform Services Controller to an external Platform Services Controller. For
information about changing Platform Services Controller, see Reconfigure vCenter Server with Embedded
Platform Services Controller to vCenter Server with External Platform Services Controller in vSphere
Installation and Setup.
You change the Platform Services Controller address by running the Site Recovery Manager installer in
Modify mode.
Sharing Platform Services Controller Instances Across Site Recovery Manager
Sites
A single point of failure is created if you share a Platform Services Controller instance between the protected
and recovery sites. If the shared Platform Services Controller goes offline, neither the protected site nor the
recovery site will function, making recovery impossible.
Concurrent Installations of Site Recovery Manager in an Enhanced Linked
Mode Environment
In an Enhanced Linked Mode environment, do not install Site Recovery Manager under more than one
Platform Services Controller at the same time. A conflict can arise in the creation of the solution user that
Platform Services Controller creates at the domain level for Site Recovery Manager authentication with
vCenter Server if the following conditions exist:
n
If the installation of one Site Recovery Manager Server instance overlaps with the installation of another
Site Recovery Manager Server instance under two different Platform Services Controller instances.
n
Those Platform Services Controller instances are in Enhanced Linked Mode.
The conflict does not prevent installation, but it does cause one of the Site Recovery Manager Server
instances to fail to start, with the error message Failed to start service. The message Failed to start
Authorization Manager appears in the event log for that Site Recovery Manager Server instance.
Site Recovery Manager in a Two-Site Topology with One vCenter Server
Instance per Platform Services Controller
The most common deployment for Site Recovery Manager is to have two sites with one vCenter Server
instance per Platform Services Controller.
In this configuration, the Platform Services Controller instances can be either external to vCenter Server or
embedded in the vCenter Server instances.
The Platform Services Controller instances can belong to vCenter Single Sign-On domains that are either in
Enhanced Linked Mode or are not in Enhanced Linked Mode.
Chapter 6 Installing Site Recovery Manager
VMware, Inc. 29