VCF Protection and Recovery 9.1: Transition from standalone SRM and VR 9.0.2
search cancel

VCF Protection and Recovery 9.1: Transition from standalone SRM and VR 9.0.2

book

Article ID: 444864

calendar_today

Updated On:

Products

VMware Live Recovery

Issue/Introduction

Upgrading to vCenter 9.1 requires transitioning disaster recovery environments to the unified VCF Protection and Recovery 9.1 appliance. Standalone Site Recovery Manager (SRM) and vSphere Replication (VR) appliances are deprecated in version 9.1. This article describes the decommissioning of legacy appliances and fresh installation of the unified platform for minimal footprint environments.

Environment

  • vCenter Server: 8.0 U3 (Source) / 9.1 (Target)
  • VMware Live Site Recovery (SRM): 9.0.2 (Build 24639340)
  • vSphere Replication (VR): 9.0.2 (Build 24628338)
  • Unified Appliance: VCF Protection and Recovery 9.1

Resolution

Fixed in release 9.1 and higher. See Download Broadcom products, patches and software for steps to download this release.

For environments with a minimal footprint (e.g., single VM replication and no existing Protection Groups or Recovery Plans), follow these steps for a clean transition:

  1. Delete active VM replications within the vSphere Client.
  2. Log into the Virtual Appliance Management Interface (VAMI) of the legacy SRM and VR appliances at https://####:5480.
  3. Unregister both appliances from the vCenter Server.
  4. Power down and delete the legacy 9.0.2 appliances from the inventory.
  5. Upgrade the vCenter Server to version 9.1.
  6. Deploy the unified VCF Protection and Recovery 9.1 appliance using the ISO media: Protection-and-recovery-9.1.0.0.25367487.iso.
  7. Establish site pairing and re-configure VM replication within the new 9.1 interface.

Additional Information

Standalone SRM and vSphere Replication appliances are deprecated starting with version 9.1. An in-place ISO upgrade is not supported for these versions because the product has transitioned to a unified "VCF Protection and Recovery" appliance architecture. Moving from standalone 9.0.2 to 9.1 typically requires a convergence migration via version 9.0.4; however, for environments with minimal replication configurations, a fresh deployment is a streamlined alternative.

Additional Resources: