If you installed vSphere Replication 1.0 as part of a previous SRM 5.0 installation, you must upgrade vSphere Replication to version 5.1.

The quickest way to upgrade vSphere Replication is to use vSphere Update Manager. If you cannot use Update Manager, you can upgrade vSphere Replication by using the VAMI of the vSphere Replication management server and vSphere Replication server. Upgrading vSphere Replication by using the VAMI requires more steps than upgrading by using Update Manager.

vSphere Replication has no earlier releases as a standalone appliance. You might have installed an earlier version of vSphere Replication as part of an SRM installation.

vSphere Replication 1.0 was delivered with SRM 5.0.

vSphere Replication 1.0.1 was delivered with SRM 5.0.1.

You can upgrade vSphere Replication 1.0 and all 1.0.x versions to vSphere Replication 5.1. The upgrade preserves the configuration from the previous installation, including the database configuration, vSphere Replication site pairings, registered vSphere Replication servers, and configured replications.

Note

After you upgrade vSphere Replication, the port on which the vSphere Replication appliance publishes the VAMI changes from 8080 to 5480.

If you deploy vSphere Replication on a vCenter Server instance that already has SRM vSphere Replication, you cannot discover the existing SRM vSphere Replication appliances through the vCenter Extension Manager. All replications that you already configured are set to an error state. If you deployed vSphere Replication 5.1 by mistake, you must shut down the vSphere Replication appliance and restart the existing SRM vSphere Replication appliance. Then you can return the virtual machines to green status using the multiple virtual machine configuration wizard in SRM.

vSphere Replication 5.1 is also available as a standalone extension of vCenter Server, that is independent of SRM. If you installed the standalone version of vSphere Replication 5.1 and then install SRM 5.1, all existing pairings and replications are immediately accessible through the SRM user interface, except for pairings and replications in a single vCenter Server. Pairings and replications in a single vCenter Server are visible only in the vSphere Replication user interface.

Migration of the vSphere Replication database is not supported. If you upgrade vSphere Replication 5.1 to SRM 5.1, vSphere Replication uses the embedded database. The standalone version of vSphere Replication 5.1 and SRM 5.1 can coexist and work together in the same infrastructure. For example, you can replicate 100 virtual machines with vSphere Replication but choose to protect only 50 of them with SRM. You can manage all of the replications by using either the vSphere Replication interface in the vSphere Web Client or by using the SRM interface. Some limitations apply to the management of the replications, depending on which interface you use.

You cannot manage replications in a single vCenter Server instance in the SRM interface.

You cannot use the vSphere Replication interface in the vSphere Web Client to manually recover virtual machines that SRM protects.

You cannot deploy additional vSphere Replication servers by using the vSphere Replication interface in the vSphere Web Client.

You can obtain update releases of vSphere Replication 5.1 by using Update Manager or by using the VAMI of the vSphere Replication appliance.