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
Creating SRM Placeholders and
Mappings 10
When you use SRM to configure the protection for virtual machines, you reserve resources on the recovery
site by creating placeholders. You map the resources of the protected virtual machines to resources on the
recovery site.
n
About Placeholder Virtual Machines on page 79
When you add a virtual machine or template to a protection group, SRM creates a placeholder virtual
machine at the recovery site.
n
About Inventory Mappings on page 80
You must create inventory mappings so that SRM can create placeholder virtual machines.
n
About Placeholder Datastores on page 81
For every virtual machine in a protection group, SRM creates a placeholder virtual machine at the
recovery site. You must identify a datastore on the recovery site in which SRM can store the
placeholder virtual machines.
n
Configure Datastore Mappings for vSphere Replication on page 82
You configure datastore mappings to determine which datastores vSphere Replication uses to store
replicated virtual machine disks and configuration files at the recovery site.
About Placeholder Virtual Machines
When you add a virtual machine or template to a protection group, SRM creates a placeholder virtual
machine at the recovery site.
SRM reserves a place for protected virtual machines in the inventory of the recovery site by creating a subset
of virtual machine files. SRM uses that subset of files as a placeholder to register a virtual machine with
vCenter Server on the recovery site. The presence of placeholder in the recovery site inventory provides a
visual indication to SRM administrators that the virtual machines are protected. The placeholders also
indicate to vCenter Server administrators that the virtual machines can power on and start consuming local
resources when SRM tests or runs a recovery plan.
When you recover a protected virtual machine by testing or running a recovery plan, SRM replaces its
placeholder with the recovered virtual machine and powers it on according to the settings of the recovery
plan. After a recovery plan test finishes, SRM restores the placeholders and powers off the virtual machines
as part of the cleanup process.
VMware, Inc.
79