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
Installing SRM to Use with a Shared
Recovery Site 11
With SRM, you can connect multiple protected sites to a single recovery site. The virtual machines on the
protected sites all recover to the same recovery site. This configuration is known as a shared recovery site, a
many-to-one, or an N:1 configuration.
In the standard one-to-one SRM configuration, you use SRM to protect a specific instance of vCenter Server
by pairing it with another vCenter Server instance. The first vCenter Server instance, the protected site,
recovers virtual machines to the second vCenter Server instance, the recovery site.
Another example is to have multiple protected sites that you configure to recover to a single, shared
recovery site. For example, an organization can provide a single recovery site with which multiple protected
sites for remote field offices can connect. Another example for a shared recovery site is for a service provider
that offers business continuity services to multiple customers.
In a shared recovery site configuration, you install one SRM Server instance on each protected site. On the
recovery site, you install multiple SRM Server instances to pair with each SRM Server instance on the
protected sites. All of the SRM Server instances on the shared recovery site connect to the same
vCenter Server instance. You can consider the owner of an SRM Server pair to be a customer of the shared
recovery site.
You can use either array-based replication or vSphere Replication or a combination of both when you
configure SRM Server to use a shared recovery site.
Example: Using SRM with Multiple Protected Sites and a Shared
Recovery Site
An organization has two field offices and a head office. Each of the field offices is a protected site. The head
office acts as the recovery site for both of the field offices. Each field office has an SRM Server instance and a
vCenter Server instance. The head office has two SRM Server instances, each of which is paired with an
SRM Server in one of the field offices. Both of the SRM Server instances at the head office extend a single
vCenter Server instance.
n
Field office 1
n
SRM Server A
n
vCenter Server A
n
Field office 2
n
SRM Server B
n
vCenter Server B
n
Head office
n
SRM Server C, that is paired with SRM Server A
VMware, Inc.
83