vCenter Server unreachable during VLCR recovery region upgrade
search cancel

vCenter Server unreachable during VLCR recovery region upgrade

book

Article ID: 445890

calendar_today

Updated On:

Products

VMware Live Recovery

Issue/Introduction

During a scheduled VMware Live Cyber Recovery (VLCR) recovery region upgrade, you observe the following symptoms in the global console:

  • The alert: "vCenter Server in recovery SDDC #### is unreachable" is displayed.
  • Secondary critical alerts indicate that the ransomware security cloud workload appliance and its required firewall rules are missing from the recovery SDDC.
  • The status dashboard may show dozens of critical issues and warnings in active plans.

Environment

  • VMware Live Cyber Recovery (VLCR)
  • VMware Cloud Foundation (VCF)

Cause

The unreachability is caused by a transient architectural state during the backend upgrade process executed by the VMware Operations Team. Specifically, the passive Backup File Controller (BFC) code deployment requires an operational window of approximately 48 hours to complete.

While the passive BFC upgrade task is actively processing and synchronizing data states, access routes and appliance visibility to the recovery target are temporarily disrupted. This occurs while the system shows a status similar to the following:

------------------------------------------------- Task History -------------------------------------------------- Status  Task     Version                Start                End/Progress ------- -------- ---------------------- -------------------- ------------Running Upgrade  9.0.1.10-####_####     2026-06-24 16:36:35  70% Description: Upgrading passive BFC

Resolution

Allow the backend operational upgrade task to run uninterrupted until it reaches 100% completion across the cluster environment.

Do not attempt manual intervention, data deletion, or virtual machine modifications on the recovery SDDC cluster while the controllers are executing code migration. The communication path automatically restores itself once the active and passive nodes finish state reconciliation. This typically takes up to 48 hours.

If the alerts persist beyond 48 hours after the upgrade start time, contact support for verification. To speak with a customer representative or a Support Engineer see . Scroll to the bottom of the page and click on your respective region.

You should  to be updated on any changes to this operational behavior.