Steps to Converge to VMware Live Recovery Appliance 9.0.4 and Common Issues During Convergence
search cancel

Steps to Converge to VMware Live Recovery Appliance 9.0.4 and Common Issues During Convergence

book

Article ID: 408127

calendar_today

Updated On:

Products

VMware Live Recovery

Issue/Introduction

Starting with VMware Live Recovery 9.0.4, the previously separate appliances — VMware Live Site Recovery, vSphere Replication, and vSAN Data Protection — are combined into a single VMware Live Recovery appliance.

This convergence simplifies deployment and management but requires careful preparation and specific upgrade paths. This article provides the steps to converge and highlights common issues and resolutions encountered during the process

 

Prerequisites

Before starting convergence, verify the following:

  1. ESXi Host Requirements

    • ESXi 8.0 U2d or later OR 8.0 U3b or later

    • vSAN Data Protection requires ESXi 9.0 or later on both protected and recovery sites

  2. Appliance Versions

    • VMware Live Site Recovery and vSphere Replication must be 9.0.2.2 or later

    • Direct upgrade from vSphere Replication 8.7.0.x to 9.0.x is not supported. Upgrade path is:
      8.7.x → 8.8.x → 9.0.2.2 (or later)

  3. Replication Configuration

    • Ensure replications are reconfigured to Enhanced Replication

  4. Connectivity & Access

    • SSH must be enabled on VMware Live Site Recovery, vSphere Replication, and vSAN Data Protection appliances

    • VMware Live Recovery 9.0.4 appliance must have access to legacy appliances

  5. Deployment Requirements

    • Deploy VMware Live Recovery 9.0.4 on both protected and recovery vCenter sites

    • Only one combined Live Recovery appliance per vCenter is allowed

    • Up to nine Live Recovery add-on appliances can be deployed per vCenter

  6. Special Considerations

    • If using VMware Life Cycle Manager (vLCM), hosts automatically enter/exit maintenance mode after VR upgrades (see KB 389735)

    • If converging with array-based replication + vVols only, you can use a Live Recovery add-on appliance, but note:

      • There is no upgrade path from add-on → full appliance

      • To use VR or vSAN DP later, you must deploy the full appliance and use the Configuration Import/Export Tool

Environment

VMware Live Recovery Appliance 9.0.4

Cause

 

  • Direct in-place upgrades from 9.0.2 appliances to 9.0.4 are not supported

  • The supported path is:
    Fresh 9.0.4 Deployment → Converge Workflow → Configuration Migration

Resolution

Convergence Steps

  1. Deploy the new 9.0.4 appliance by using the .OVA file downloaded from the Broadcom portal, and assign it a new FQDN and IP address during deployment.

  2. Open a browser and go to the VMware Live Recovery Management Interface:
    https://<appliance-IP-or-FQDN>
    → Click Launch VMware Live Recovery Appliance Management

  3. Log in as admin

  4. Click Converge Legacy Appliances

  5. The  Converge is a 3-step process.
  6.  Step 1: Platform Services Controller

    1. Enter credentials for the vCenter where legacy appliances are registered.

    2. If prompted, click Connect to verify vCenter certificate.



  7. Step 2: vCenter Server
    1. Select the vCenter, click List Services to Converge, choose services, and click Next

  8. Step 3: Source Appliance
    1. Enter credentials for the legacy appliances (VR, SRM, vSAN DP), then click Finish

  9. Run the Configuration Wizard to confirm current settings

  10. Repeat the procedure on the recovery site

Common Issues and Resolutions

1. Error: (Due to mounting ISO)

ERROR Operation Failed
Failed to install update: Is a directory.
Operation ID: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX 

Cause: This occurs because ISO-based in-place upgrade from 9.0.2.2 → 9.0.4 is not supported. (https://knowledge.broadcom.com/external/article/383847/error-failed-to-install-updateis-a-direc.html)

Resolution:

  • Deploy a new 9.0.4 appliance

  • Use Converge workflow for migration

 

2. Error: (On Step 1)

Unable to connect to host "vCenter_FQDN:443"

Cause: Hostname resolution failure. Netcat direct lookup fails if DNS cannot resolve vCenter FQDN.

Resolution:

  • Add vCenter FQDN and IP mapping in /etc/hosts on the 9.0.4 appliance

 

3. Error: (On Step 3)


OR

Cause:

  • SSH not enabled on VR/SRM appliances

  • Hostname resolution failure (direct lookup failed)

Resolution:

  • Enable SSH on VRMS and SRM appliances

  • Add VR/SRM FQDN and IP to /etc/hosts

 

Reverting to VMware Live Recovery 9.0.2.2

If convergence to 9.0.4 fails or you need to roll back, follow these steps:

Snapshot Recommendations (Before Convergence)

  • Take a snapshot of VR, SRM, and vCenter on the Protected (PR) site.

  • Take a snapshot of VR, SRM, and vCenter on the Disaster Recovery (DR) site.

  • If vCenters are running in Linked Mode, take offline snapshots to ensure consistency across both sites.

These snapshots provide a quick way to revert the environment to 9.0.2.2 in case of convergence failure.

Additional Information

Powered by Wolken Software