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
For information about the loads that a vSphere Replication management server and a vSphere Replication
server can support, see http://kb.vmware.com/kb/2034768.
vSphere Replication does not require storage arrays. The vSphere Replication storage replication source and
target can be any storage device, including, but not limited to, storage arrays. You can use Virtual SAN
(VSAN) storage with vSphere Replication.
NOTE vSphere 5.5 includes Virtual SAN as an experimental feature. You can perform testing with Virtual
SAN, but it is not supported for use in a production environment. See the release notes for this release for
information about how to enable Virtual SAN.
You can configure vSphere Replication to regularly create and retain snapshots of protected virtual
machines on the recovery site. Taking multiple point-in-time (MPIT) snapshots of virtual machines allows
you to retain more than one replica of a virtual machine on the recovery site. Each snapshot reflects the state
of the virtual machine at a certain point in time. You can select which snapshot to recover when you use
vSphere Replication to perform a recovery.
vSphere Replication is compatible with vSphere Storage vMotion and vSphere Storage DRS on the protected
site. You can use Storage vMotion and Storage DRS to move the disk files of a virtual machine that
vSphere Replication protects, with no impact on replication.
Figure 1‑3. SRM Architecture with 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
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
vCenter Server
Site Recovery Manager Installation and Configuration
14 VMware, Inc.