Before you upgrade Site Recovery Manager, you must perform preparatory tasks on both Site Recovery Manager sites and verify that you have certain information.

  • Make a full backup of the Site Recovery Manager database by using the tools that the database software provides. For information about how to back up the embedded database, see Back Up and Restore the Embedded vPostgres Database. Migration of data from an external database to the embedded database is not supported. Failure to back up the database results in the loss of all Site Recovery Manager data if the upgrade fails.

  • If you configured advanced settings in the existing installation, take a note of the settings that you configured in Site Recovery > Sites > Site > Manage > Advanced Settings in the vSphere Web Client.

  • Because of update release schedules, upgrading to certain Site Recovery Manager 6.0.x update releases is not supported for all 5.5.x and 5.8.x releases. For information about supported upgrade paths, see Solution Upgrade Path > VMware vCenter Site Recovery Manager in the VMware Product Interoperability Matrixes at http://partnerweb.vmware.com/comp_guide2/sim/interop_matrix.php? before you upgrade.

    Important:

    Upgrading from Site Recovery Manager 5.0.x and 5.1.x to Site Recovery Manager 6.0 is not supported. Upgrade Site Recovery Manager 5.0.x and 5.1.x to a Site Recovery Manager 5.5.x or 5.8.x release before you upgrade to Site Recovery Manager 6.0.

  • The local and remote vCenter Server instances must be running when you upgrade Site Recovery Manager.

  • Upgrade vCenter Server and install the appropriate version of Platform Services Controller on the site on which you are upgrading Site Recovery Manager.

  • Upgrade all of the vCenter Server components and Site Recovery Manager on one site before you upgrade vCenter Server and Site Recovery Manager on the other site.

  • For environments with a small number of virtual machines to protect, you can run Site Recovery Manager Server and vCenter Server on the same system. For environments that approach the maximum limits of Site Recovery Manager and vCenter Server, install Site Recovery Manager Server on a system that is different from the system on which vCenter Server is installed. If Site Recovery Manager Server and vCenter Server are installed on the same system, administrative tasks might become more difficult to perform in large environments. Furthermore, if you install Site Recovery Manager Server in a virtual machine, and this virtual machine is not the same as the one that runs vCenter Server, you can use vSphere High Availability and VMware Fault Tolerance to protect the Site Recovery Manager Server virtual machine.

  • When you install and configure Platform Services Controller, vCenter Server, and vSphere Replication, use fully qualified domain names (FQDN) whenever possible rather than IP addresses. Using FQDN rather than IP addresses allows you to change the vSphere infrastructure, for example by using DHCP, without having to redeploy or reconfigure Site Recovery Manager. You must also use FQDN if you use custom certificates, because most certificate authorities do not accept certificates that use IP addresses for the SAN or CN value.

  • The way in which you deploy Platform Services Controller, vCenter Server, and vCenter Single Sign-On on a site affects how you deploy Site Recovery Manager. For information about how the vCenter Server deployment model affects Site Recovery Manager, see Site Recovery Manager and vCenter Server Deployment Models.

  • Obtain the address of the Platform Services Controller instance for both sites. The Platform Services Controller must be running and accessible during Site Recovery Manager installation.

  • Obtain the vCenter Single Sign-On administrator user name and password for both of the local and remote sites.

  • Synchronize the clock settings of the systems on which Platform Services Controller, vCenter Server, and Site Recovery Manager Server run. To avoid conflicts in the time management across these systems, use a persistent synchronization agent such as network time protocol daemon (NTPD), W32Time, or VMware Tools time synchronization. If you run Platform Services Controller, vCenter Server, and Site Recovery Manager Server in virtual machines, set up NTP time synchronization on the ESXi host on which the virtual machines run. For information about timekeeping best practices, see http://kb.vmware.com/kb/1318.

  • Obtain the user name and password for the Site Recovery Manager database, if you are not using the embedded database.

  • If you use Site Recovery Manager with vSphere Replication, upgrade vSphere Replication before you upgrade Site Recovery Manager Server. The Site Recovery Manager installer verifies the version of vSphere Replication during installation and stops if it detects an incompatible version.

  • The Site Recovery Manager installer presents the SSL/TLS certificates of the vCenter Server components for validation when it runs. Obtain the necessary information to allow you validate the certificates for the Platform Services Controller instance on the local site and the Platform Services Controller and vCenter Server instances on the remote site.

  • 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. If you use MD5 certificates with a previous installation of Site Recovery Manager, you must obtain a new certificate with a stronger signature algorithm before you upgrade Site Recovery Manager. See Requirements When Using Custom SSL/TLS Certificates with Site Recovery Manager.

  • Download the Site Recovery Manager installation file to a folder on the machines on which to upgrade Site Recovery Manager.

  • 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.

  • 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.

    • All recovery plans are in the Ready state.

    • The protection status of all of the protection groups is OK.

    • The protection status of all of the individual virtual machines in the protection groups is OK.

    • The recovery status of all of the protection groups is Ready.

  • 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.