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
An upgrade without migration provides a quick way to upgrade the SRM Server to a new release without
changing any of the information that you provided for the current installation. To change any installation
information, for example, database connections, the authentication method, certificate location, or
administrator credentials, you must run the installer in modify mode after you upgrade an existing
SRM Server.
If you connect SRM to a vCenter Server instance that is already running vSphere Replication as a registered
extension, you must still select the Install vSphere Replication option. Selecting this option installs
components that SRM requires to work with vSphere Replication. You can also install vSphere Replication
after you install SRM by running the installer again in Repair mode.
If existing configuration information is invalid for the upgrade, the upgrade fails. For example, the upgrade
fails if the database is not accessible at the same DSN, or if vCenter Server is not accessible at the same port.
IMPORTANT If you created custom permissions that you assigned to the SRM 5.0 service instance, you must
upgrade the SRM Server with migration. If you upgrade the SRM Server without migration, custom
permissions are lost. See “Upgrade the SRM Server with Migration,” on page 44.
Prerequisites
n
You completed the tasks in “Prepare for SRM Upgrade,” on page 42.
n
Log into the SRM host to upgrade. Log in using an account with sufficient privileges. This is often an
Active Directory domain administrator, but can also be a local administrator.
n
Download the SRM installation file to a folder on the SRM Server host.
Procedure
1 Double-click the SRM installer icon, select an installation language, and click OK.
2 If you are upgrading from SRM 5.0.x, click OK to confirm that you created a 64-bit ODBC DSN to
connect SRM to the existing database.
This prompt does not appear when you upgrade from SRM 5.1.
3 Follow the prompts and accept the license agreement.
4 Click Change to change the folder in which to install SRM, select a target volume, and click Next.
The default installation folder for SRM is C:\Program Files\VMware\VMware vCenter Site Recovery
Manager. If you use a different folder, the pathname cannot be longer than 170 characters including the
end slash, and cannot include non-ASCII characters.
5 Select whether to install vSphere Replication and click Next.
6 Provide the username and password for vCenter Server and click Next.
You cannot change the vCenter Server instance to which SRM connects. To connect to a different
vCenter Server instance, you must install a new SRM Server.
7 (Optional) If you are using credential-based authentication, verify the vCenter Server certificate and
click Yes to accept it.
If you are using certificate-based authentication, there is no prompt to accept the certificate.
8 Click Yes to confirm that you want to overwrite the existing SRM extension on this vCenter Server
instance.
Chapter 6 Upgrading SRM
VMware, Inc. 43