Before you can upgrade Site Recovery Manager, you must perform preparatory tasks.
About this task
Site Recovery Manager 5.0.x uses a 32-bit open database connectivity (ODBC) database source name (DSN), but Site Recovery Manager 5.5 requires a 64-bit DSN to connect to the Site Recovery Manager database. If you are upgrading from Site Recovery Manager 5.0.x, you must create a 64-bit DSN. See Create an ODBC System DSN for Site Recovery Manager.
Due to update release schedules, upgrading to certain 5.5.x releases is not supported for all 5.0.x and 5.1.x releases. Check http://partnerweb.vmware.com/comp_guide2/sim/interop_matrix.php? before you upgrade, to ensure that your upgrade path is supported.in the VMware Product Interoperability Matrixes atImportant:
Upgrade versions of Site Recovery Manager earlier than 5.0 to a Site Recovery Manager 5.0.x release before you upgrade to Site Recovery Manager 5.5.x. Upgrading vCenter Server directly from 4.1.x to 5.5 is a supported upgrade path. However, upgrading Site Recovery Manager directly from 4.1.x to 5.5.x is not a supported upgrade path. When upgrading a vCenter Server 4.1.x instance that includes a Site Recovery Manager installation, you must upgrade vCenter Server to version 5.0.x before you upgrade Site Recovery Manager to 5.0.x. If you upgrade vCenter Server from 4.1.x to 5.5 directly, when you attempt to upgrade Site Recovery Manager from 4.1.x to 5.0.x, the Site Recovery Manager upgrade fails. Site Recovery Manager 5.0.x cannot connect to a vCenter Server 5.5 instance.
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.
If you configured advanced settings in the existing installation, take a note of the settings that you configured before upgrading.
The local and remote vCenter Server instances must be running when you upgrade 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.
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 to fail.
- Log in to the machine on the protected site on which you have installed Site Recovery Manager.
- Back up the Site Recovery Manager database by using the tools that the database software provides.
- (Optional) : If you are upgrading from Site Recovery Manager 5.0.x, create a 64-bit DSN.
- Upgrade the vCenter Server instance to which Site Recovery Manager connects to vCenter Server 5.5.
If you are upgrading from vCenter Server and Site Recovery Manager 4.1.x, you must upgrade the vCenter Server and Site Recovery Manager Server instances in the correct sequence before you can upgrade to Site Recovery Manager 5.5.
- Upgrade vCenter Server from 4.1.x to 5.0.x.
- Upgrade Site Recovery Manager from 4.1.x to 5.0.x.
- Upgrade vCenter Server from 5.0.x to 5.5.