You perform several tasks to upgrade Site Recovery Manager to version 5.1.

You must perform the upgrade tasks in order. Complete all of the upgrade tasks on the protected site first, then complete the tasks on the recovery site.

Due to update release schedules, upgrading to certain 5.1.x releases is not supported for all 5.0.x releases. Check 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, to ensure that your upgrade path is supported.

Important

Upgrade versions of Site Recovery Manager earlier than 5.0 to a Site Recovery Manager 5.0.x release before you upgrade to 5.1.x. Upgrading vCenter Server directly from 4.1.x to 5.1 is a supported upgrade path. However, upgrading Site Recovery Manager directly from 4.1.x to 5.1 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.1 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.1 instance.

1

Before you can upgrade Site Recovery Manager to version 5.1, you must perform preparatory tasks.

2

You can upgrade the Site Recovery Manager Server on the same host as an existing Site Recovery Manager Server installation.

3

You can upgrade Site Recovery Manager and migrate the Site Recovery Manager Server to a different host than the previous Site Recovery Manager Server installation.

4

You must upgrade the Site Recovery Manager client plug-in for all vSphere Client instances that you use to manage Site Recovery Manager.

5

You must configure the upgraded components to establish a working Site Recovery Manager installation.

6

You can upgrade vSphere Replication by using either vSphere Update Manager or by using the virtual appliance management interfaces (VAMI) of the vSphere Replication management server and vSphere Replication servers.