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‑4. SRM Architecture with Array-Based Replication and vSphere Replication
SRM plug-in
vSphere Client
Protected Site
SRM plug-in
vSphere Client
Recovery Site
ESXi
Server
VR Agent
ESXi
Server
VR Agent
vCenter Server
VMFS
VMFS
Storage
VMFS
VMFS
Storage
Array based replication
ESXi
Server
VR Agent
SRM Server
VR Appliance
Network
File Copy
ESXi
SRM Server
Additional
VR Server
Network
File Copy
ESXi
VR Appliance
vSphere replication
SRA
vCenter Server
SRA
SRM and vCenter Server
SRM Server operates as an extension to the vCenter Server at a site. Because the SRM Server depends on
vCenter Server for some services, you must install and configure vCenter Server at a site before you install
SRM.
SRM takes advantage of vCenter Server services, such as storage management, authentication,
authorization, and guest customization. SRM also uses the standard set of vSphere administrative tools to
manage these services.
You can use SRM and vSphere Replication with the vCenter Server Appliance or with a standard
vCenter Server installation. You can have vCenter Server Appliance on one site and a standard
vCenter Server installation on the other.
How Changes to vCenter Server Inventory Affect SRM
Because SRM protection groups apply to a subset of the vCenter Server inventory, changes to the protected
inventory made by vCenter Server administrators and users can affect the integrity of SRM protection and
recovery. SRM depends on the availability of certain objects, such as virtual machines, folders, resource
pools, and networks, in the vCenter Server inventory at the protected and recovery sites. Deletion of
resources such as folders or networks that are referenced by recovery plans can invalidate the plan.
Renaming or relocating objects in the vCenter Server inventory does not affect SRM, unless it causes
resources to become inaccessible during test or recovery.
SRM can tolerate certain changes at the protected site without disruption.
n
Deleting protected virtual machines.
n
Deleting an object for which an inventory mapping exists.
Site Recovery Manager Installation and Configuration
18 VMware, Inc.