6.1

Figure 6‑3. Site Recovery Manager in a Single Site Topology with a Shared Platform Services Controller
vCenter
Server 1
Platform Services
Controller 1
SRM
Server
1
Protected Site
Single Site
Key:
Site Recovery Manager site pair
Connection from Site Recovery Manager
to Platform Services Controller
Connection from Platform Services
Controller to vCenter Server
vCenter
Server 2
SRM
Server
2
Recovery Site
Prerequisites and Best Practices for Site Recovery Manager Server
Installation
Before you install Site Recovery Manager Server, you must perform several tasks and verify that you have
certain information.
n
Install the appropriate version of Platform Services Controller and vCenter Server on both sites. You
cannot mix Site Recovery Manager, Platform Services Controller, or vCenter Server versions across
sites. For information about compatibility between vCenter Server and Site Recovery Manager versions,
see vCenter Server 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
For environments with a small number of virtual machines to protect, you can run
Site Recovery Manager Server and vCenter Server on the same system. For environments that approach
the maximum limits of Site Recovery Manager and vCenter Server, install
Site Recovery Manager Server on a system that is different from the system on which vCenter Server is
installed. If Site Recovery Manager Server and vCenter Server are installed on the same system,
administrative tasks might become more difficult to perform in large environments. Furthermore, if you
install Site Recovery Manager Server in a virtual machine, and this virtual machine is not the same as
the one that runs vCenter Server, you can use vSphere High Availability and VMware Fault Tolerance
to protect the Site Recovery Manager Server virtual machine.
n
When you install and configure Platform Services Controller, vCenter Server, and vSphere Replication,
use fully qualified domain names (FQDN) whenever possible rather than IP addresses. Using FQDN
rather than IP addresses allows you to change the vSphere infrastructure, for example by using DHCP,
without having to redeploy or reconfigure Site Recovery Manager. You must also use FQDN if you use
custom certificates, because most certificate authorities do not accept certificates that use IP addresses
for the SAN or CN value.
Site Recovery Manager Installation and Configuration
32 VMware, Inc.