6.1

n
If you use custom certificates, obtain an appropriate certificate file. Custom certificates must use at least
the SHA1, or preferably SHA256, thumbprint algorithm. This release of Site Recovery Manager does
not support certificates that use the MD5 thumbprint algorithm. See “Requirements When Using
Custom SSL/TLS Certificates with Site Recovery Manager,” on page 25.
n
Download the Site Recovery Manager installation file to a folder on the machines on which to upgrade
Site Recovery Manager.
n
Verify that no reboot is pending on the Windows machine on which to install
Site Recovery Manager Server. Verify that no other installation is running, including the silent
installation of Windows updates. Pending reboots or running installations can cause the installation of
Site Recovery Manager Server or the embedded Site Recovery Manager database to fail.
n
IMPORTANT Verify that there are no pending cleanup operations on recovery plans and that there are no
configuration issues for the virtual machines that Site Recovery Manager protects.
n
All recovery plans are in the Ready state.
n
The protection status of all of the protection groups is OK.
n
The protection status of all of the individual virtual machines in the protection groups is OK.
n
The recovery status of all of the protection groups is Ready.
n
Optimize the Adobe Flash Player settings in your browser to increase the amount of storage space that
the vSphere Web Client can use. Performing a recovery with Site Recovery Manager can sometimes
exceed the default amount of storage space that Flash Player is permitted to consume. For information
about how to optimize the Flash Player settings for Site Recovery Manager in the vSphere Web Client,
see http://kb.vmware.com/kb/2106096.
In-Place Upgrade of Site Recovery Manager Server
An in-place upgrade provides a quick way to upgrade Site Recovery Manager Server without changing the
information that you provided for the previous installation.
With an in-place upgrade, you upgrade Site Recovery Manager Server on the same host machine as an
existing Site Recovery Manager Server installation. To upgrade Site Recovery Manager and migrate the
Site Recovery Manager Server to a different host machine, see “Upgrade Site Recovery Manager Server with
Migration,” on page 62.
NOTE If you are updating Site Recovery Manager 6.1 to a 6.1.x update release or to a 6.1.x.x patch release,
you must perform in-place upgrade. You cannot perform upgrade with migration if you are updating
Site Recovery Manager 6.1 to a 6.1.x update release or to a 6.1.x.x patch release.
When you upgrade Site Recovery Manager Server, you provide the address of the
Platform Services Controller that the upgraded vCenter Server instance uses. If the address of the
Platform Services Controller changed during upgrade, you provide the new address when you upgrade
Site Recovery Manager Server. For the subsequent steps of the upgrade, the Site Recovery Manager installer
reuses information about vCenter Server connections, certificates, and database configuration from the
previous Site Recovery Manager installation. The installer populates the text boxes in the installation wizard
with the values from the previous installation.
To change installation information, for example, database connections, certificate location, or administrator
credentials, you must run the installer in modify mode after you upgrade an existing
Site Recovery Manager Server.
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.
During upgrade, you cannot change the vCenter Server instance to which Site Recovery Manager connects.
To connect to a different vCenter Server instance, you must install a new Site Recovery Manager Server.
Chapter 8 Upgrading Site Recovery Manager
VMware, Inc. 59