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
The way in which you deploy Platform Services Controller, vCenter Server, and vCenter Single Sign-On
on a site affects how you deploy Site Recovery Manager. For information about how the vCenter Server
deployment model affects Site Recovery Manager, see “Site Recovery Manager and vCenter Server
Deployment Models,” on page 28.
n
Obtain the address of the Platform Services Controller instance for both sites. The
Platform Services Controller must be running and accessible during Site Recovery Manager installation.
n
Obtain the vCenter Single Sign-On administrator user name and password for both of the local and
remote sites.
n
Synchronize the clock settings of the systems on which Platform Services Controller, vCenter Server,
and Site Recovery Manager Server run. To avoid conflicts in the time management across these systems,
use a persistent synchronization agent such as network time protocol daemon (NTPD), W32Time, or
VMware Tools time synchronization. If you run Platform Services Controller, vCenter Server, and
Site Recovery Manager Server in virtual machines, set up NTP time synchronization on the ESXi host
on which the virtual machines run. For information about timekeeping best practices, see
http://kb.vmware.com/kb/1318.
n
Obtain a Windows user account with the appropriate privileges on the system on which to install and
run Site Recovery Manager Server. You can configure the Site Recovery Manager service to run under a
specified user account. The account can be a local user or a domain user that is a member of the
Administrators group on the machine on which you are installing Site Recovery Manager.
Alternatively, you can configure Site Recovery Manager to run under the Local System account during
installation.
n
Obtain the user name and password for the Site Recovery Manager database, if you are not using the
embedded database.
n
If you do not use the embedded Site Recovery Manager database, configure and start the
Site Recovery Manager database service on both sites before you install the
Site Recovery Manager Server. Each Site Recovery Manager instance requires its own database. See
Chapter 3, “Creating the Site Recovery Manager Database,” on page 17.
n
If you do not use the embedded Site Recovery Manager database, Site Recovery Manager requires a
database source name (DSN) for 64-bit open database connectivity (ODBC). You can create the ODBC
system DSN before you run the Site Recovery Manager installer, or you can create the DSN during the
installation process. For details about creating the ODBC system DSN, see “Create an ODBC System
DSN for Site Recovery Manager,” on page 20. If you use the embedded Site Recovery Manager
database, the Site Recovery Manager installer creates the necessary DSN.
n
To use Site Recovery Manager with vSphere Replication, deploy the appropriate version of
vSphere Replication on both of the protected and recovery sites before you install
Site Recovery Manager Server. The Site Recovery Manager installer verifies the version of
vSphere Replication during installation and stops if it detects an incompatible version. This verification
is not performed if you install vSphere Replication after you install Site Recovery Manager Server,
which might lead to incompatible versions. Incompatible versions of Site Recovery Manager and
vSphere Replication cause the vSphere Web Client to stop working. For information about
compatibility between vSphere Replication and Site Recovery Manager versions, see vSphere Replication
Requirements in the Compatibility Matrixes for Site Recovery Manager 6.1 at
https://www.vmware.com/support/srm/srm-compat-matrix-6-1.html.
n
If you cannot upgrade an existing incompatible version of vSphere Replication, you must unregister
vSphere Replication from both vCenter Server instances before you install Site Recovery Manager.
Incompatible versions of Site Recovery Manager and vSphere Replication cause the vSphere Web Client
to stop working. See “Unregister an Incompatible Version of vSphere Replication,” on page 41.
n
The Site Recovery Manager installer presents the SSL/TLS certificate of the Platform Services Controller
for validation when it runs. Obtain the necessary information to allow you validate the certificate.
Chapter 6 Installing Site Recovery Manager
VMware, Inc. 33