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
Upgrading vSphere Replication 9
If you installed vSphere Replication as part of a previous SRM installation, you must upgrade
vSphere Replication after you upgrade SRM.
If you upgrade SRM, vSphere Replication is not upgraded automatically. You must upgrade
vSphere Replication as a separate process from upgrading SRM.
The quickest way to upgrade vSphere Replication is to use vSphere Update Manager. If you cannot use
Update Manager, you can upgrade vSphere Replication by using the virtual appliance management
interface (VAMI) of the vSphere Replication appliances. Upgrading vSphere Replication by using the VAMI
requires more steps than upgrading by using Update Manager.
You might have installed an earlier version of vSphere Replication as part of an SRM installation, or you
might have installed the standalone version of vSphere Replication.
n
vSphere Replication 1.0.x was delivered with SRM 5.0.x.
n
vSphere Replication 5.1.x was delivered with SRM 5.1.x and is also available as a standalone product,
independently of SRM.
You can upgrade vSphere Replication 1.0.x and 5.1.x to vSphere Replication 5.5. The upgrade preserves the
configuration from the previous installation, including the database configuration, certificates,
vSphere Replication site pairings, registered vSphere Replication servers, and configured replications.
In SRM 5.0 the vSphere Replication management server and the vSphere Replication server are separate
appliances. In SRM 5.1 and later and vSphere Replication 5.1 and later, vSphere Replication is a single
appliance named the vSphere Replication appliance, that contains both the vSphere Replication
management server and a vSphere Replication server.
When upgrading vSphere Replication 1.0.x to vSphere Replication 5.5, the upgrade process upgrades the
vSphere Replication management server to the combined vSphere Replication 5.5 appliance. As a
consequence, an upgraded installation of vSphere Replication uses the vSphere Replication server that is
embedded in the combined appliance. If your infrastructure uses more than one vSphere Replication server,
you must upgrade them to vSphere Replication 5.5 and reregister them with the vSphere Replication
appliance.
NOTE After you upgrade vSphere Replication 1.0.x, the port on which the vSphere Replication appliance
publishes the VAMI changes from 8080 to 5480.
VMware, Inc.
73