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
If you are using array-based replication, the same replication technology must be available at both sites,
and the arrays must be paired.
n
If you are using vSphere Replication, you require a vSphere Replication appliance on both sites. The
vSphere Replication appliances must be connected to each other.
n
The vSphere Replication appliances must be of the same version.
n
The vSphere Replication version must be compatible with the version of Site Recovery Manager. 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
The recovery site must have hardware, network, and storage resources that can support the same
virtual machines and workloads as the protected site. You can oversubscribe the recovery site by
running additional virtual machines there that are not protected. In this case, during a recovery you
must suspend noncritical virtual machines on the recovery site.
n
The sites must be connected by a reliable IP network. If you are using array-based replication, ensure
that your network connectivity meets the arrays' network requirements.
n
The recovery site should have access to comparable public and private networks as the protected site,
although not necessarily the same range of network addresses.
Bidirectional Protection
You can use a single set of paired Site Recovery Manager sites to protect virtual machines in both directions.
Each site can simultaneously be a protected site and a recovery site, but for a different set of virtual
machines.
You can implement bidirectional protection by protecting datastore groups or storage policies by using
array-based replication or by protecting individual virtual machines by using vSphere Replication. If you
are using array-based replication, each of the array’s LUNs replicates in only one direction. Two LUNs in
paired arrays can replicate in different directions from each other.
Heterogeneous Configurations on the Protected and Recovery Sites
Some components in the Site Recovery Manager and vCenter Server installations must be identical on each
site. Because the protected and recovery sites are often in different physical locations, some components on
the protected site can be of a different type to their counterparts on the recovery site.
Although components can be different on each site, you must use the types and versions of these
components that Site Recovery Manager supports. See the Compatibility Matrixes for Site Recovery Manager 6.1
at https://www.vmware.com/support/srm/srm-compat-matrix-6-1.html for information.
Table 1‑1. Heterogeneity of Site Recovery Manager Components Between Sites
Component Heterogeneous or Identical Installations
Site Recovery Manager Server Must be the same version on both sites.
vCenter Server and Platform Services Controller Must be the same version on both sites. The
Site Recovery Manager version must be compatible with
the vCenter Server and Platform Services Controller
version.
vSphere Replication Must be the same version on both sites. The
vSphere Replication version must be compatible with the
Site Recovery Manager version and the vCenter Server
version.
vCenter Server Appliance or standard vCenter Server
instance
Can be different on each site. You can run a vCenter Server
Appliance on one site and a standard vCenter Server
instance on the other site.
Chapter 1 Overview of VMware Site Recovery Manager
VMware, Inc. 11