5.5
Table Of Contents
- Site Recovery Manager Installation and Configuration
- Contents
- About Site Recovery Manager Installation and Configuration
- Overview of VMware vCenter Site Recovery Manager
- Site Recovery Manager System Requirements
- Creating the SRM Database
- SRM Authentication
- Installing SRM
- Upgrading SRM
- Configuring Array-Based Protection
- Installing vSphere Replication
- Deploy the vSphere Replication Appliance
- Configure vSphere Replication Connections
- Reconfigure the vSphere Replication Appliance
- Reconfigure General vSphere Replication Settings
- Change the SSL Certificate of the vSphere Replication Appliance
- Change the Password of the vSphere Replication Appliance
- Change Keystore and Truststore Passwords of the vSphere Replication Appliance
- Configure vSphere Replication Network Settings
- Configure vSphere Replication System Settings
- Reconfigure vSphere Replication to Use an External Database
- Use the Embedded vSphere Replication Database
- Deploy an Additional vSphere Replication Server
- Register an Additional vSphere Replication Server
- Reconfigure vSphere Replication Server Settings
- Unregister and Remove a vSphere Replication Server
- Uninstall vSphere Replication
- Unregister vSphere Replication from vCenter Server if the Appliance Was Deleted
- Upgrading vSphere Replication
- Creating SRM Placeholders and Mappings
- Installing SRM to Use with a Shared Recovery Site
- Limitations of Using SRM in Shared Recovery Site Configuration
- SRM Licenses in a Shared Recovery Site Configuration
- Install SRM In a Shared Recovery Site Configuration
- Install SRM Server on Multiple Protected Sites to Use with a Shared Recovery Site
- Install Multiple SRM Server Instances on a Shared Recovery Site
- Install the SRM Client Plug-In In a Shared Recovery Site Configuration
- Connect to SRM in a Shared Recovery Site Configuration
- Connect the SRM Sites in a Shared Recovery Site Configuration
- Configure Placeholders and Mappings in a Shared Recovery Site Configuration
- Use Array-Based Replication in a Shared Recovery Site Configuration
- Use vSphere Replication in a Shared Recovery Site Configuration
- Troubleshooting SRM Installation and Configuration
- Cannot Restore SQL Database to a 32-Bit Target Virtual Machine During SRM Upgrade
- SRM Server Does Not Start
- vSphere Client Cannot Connect to SRM
- Site Pairing Fails Because of Different Certificate Trust Methods
- Error at vService Bindings When Deploying the vSphere Replication Appliance
- OVF Package is Invalid and Cannot be Deployed
- vSphere Replication Appliance or vSphere Replication Server Does Not Deploy from the SRM Interface
- Connection Errors Between vSphere Replication and SQL Server Cannot be Resolved
- 404 Error Message when Attempting to Pair vSphere Replication Appliances
- vSphere Replication Service Fails with Unresolved Host Error
- Increase the Memory of the vSphere Replication Server for Large Deployments
- vSphere Replication Appliance Extension Cannot Be Deleted
- Uploading a Valid Certificate to vSphere Replication Results in a Warning
- vSphere Replication Status Shows as Disconnected
- vSphere Replication Server Registration Takes Several Minutes
- vSphere Replication is Inaccessible After Changing vCenter Server Certificate
- Index
Figure 1‑1. SRM Site Pairing and Recovery Process
apps
OS
apps
OS
apps
OS
apps
OS
apps
OS
apps
OS
Site A
Protected
site goes
offline
Replica
virtual
machines
power on
Virtual machines replicate from site A to site B
Site B
apps
OS
apps
OS
apps
OS
apps
OS
apps
OS
apps
OS
Protection group
Bidirectional Protection
You can use a single set of paired SRM 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 using either array-based replication or 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.
For information about the numbers of virtual machines for which you can establish bidirectional protection
between two sites, see http://kb.vmware.com/kb/2034768.
Heterogeneous Configurations on the Protected and Recovery Sites
The configurations of the SRM and vCenter Server installations can be different on each of the protected and
recovery sites.
Some components in the SRM 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 SRM supports. See the Site Recovery Manager Compatibility Matrixes for information.
Table 1‑1. Heterogeneity of SRM Components Between Sites
Component Heterogeneous or Identical Installations
SRM Server Must be the same version on both sites. The SRM version
must be the same as the vCenter Server version.
vCenter Server Must be the same version on both sites.
vSphere Replication Must be the same version on both sites. The
vSphere Replication version must be the same as the SRM
version and the vCenter Server version.
Authentication method Must be the same on both sites. If you use autogenerated
certificates to authenticate between the SRM Server
instances on each site, you must use autogenerated
certificates on both sites. If you use custom certificates that
are signed by a certificate authentication service, you must
use such certificates on both sites. Similarly, the
authentication method that you use between SRM Server
and vCenter Server must be the same on both sites. If you
use different authentication methods on each site, site
pairing fails.
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 vCenter Site Recovery Manager
VMware, Inc. 11