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
Overview of
VMware vCenter Site Recovery
Manager 1
VMware vCenter Site Recovery Manager (SRM) is a business continuity and disaster recovery solution that
helps you to plan, test, and run the recovery of virtual machines between a protected vCenter Server site
and a recovery vCenter Server site.
You can configure SRM to work with several third-party disk replication mechanisms by configuring array-
based replication. Array-based replication surfaces replicated datastores to recover virtual machine
workloads. You can also use host-based replication by configuring SRM to use VMware vSphere Replication
to protect virtual machine workloads.
You can use SRM to implement different types of recovery from the protected site to the recovery site.
Planned Migration
The orderly evacuation of virtual machines from the protected site to the
recovery site. Planned Migration prevents data loss when migrating
workloads in an orderly fashion. For planned migration to succeed, both
sites must be running and fully functioning.
Disaster Recovery
Similar to planned migration except that disaster recovery does not require
that both sites be up and running, for example if the protected site goes
offline unexpectedly. During a disaster recovery operation, failure of
operations on the protected site are reported but otherwise ignored.
SRM orchestrates the recovery process with the replication mechanisms, to minimize data loss and system
down time.
n
At the protected site, SRM shuts down virtual machines cleanly, if the protected site is still running.
n
SRM powers on the replicated virtual machines at the recovery site according to a recovery plan.
A recovery plan specifies the order in which virtual machines start up on the recovery site. A recovery plan
specifies network parameters, such as IP addresses, and can contain user-specified scripts that SRM can run
to perform custom recovery actions.
SRM lets you test recovery plans. You conduct tests by using a temporary copy of the replicated data in a
way that does not disrupt ongoing operations at either site.
n
About Protected Sites and Recovery Sites on page 10
In a typical SRM installation, the protected site provides business-critical datacenter services. The
recovery site is an alternative facility to which SRM can migrate these services.
n
Using Array-Based Replication with SRM on page 12
When you use array-based replication, one or more storage arrays at the protected site replicate data
to peer arrays at the recovery site. With storage replication adapters (SRAs), you can integrate SRM
with a wide variety of arrays.
VMware, Inc.
9