Test Recovery fails with error : "<VM-name> failed recovery. Error: Cyber Recovery internal error. Please contact support."

Products

• VMware Live Recovery

Issue/Introduction

Symptoms:

• VLCR bubble recovery for VMs on a Recovery Plan fails with following error:
  
  Error : <VM_name> failed recovery. Error: Cyber Recovery internal error. Please contact support.


• Workflow steps shows up as:
  

  Step 1. Run the step Recover <VM_name>
1.1 Retrieve VM snapshots for 1 VMs
No events recorded for this substep.

  1.2 Recover 1 VMs

  Feb 23, 2026 23:48 PM UTC -- VM <VM_name> running live from cloud file system
Feb 23, 2026 23:48 PM UTC -- VM <VM_name> restored from snapshot  - Manual - 2026-02-23T23:39:06 UTC
Feb 23, 2026 23:48 PM UTC -- VM <VM_name>registered with vCenter <VC_IP>
Feb 23, 2026 23:48 PM UTC -- Reconfiguring Ethernet adapters for VM '<VM_name>'
Feb 23, 2026 23:48 PM UTC -- Reconfigured Ethernet adapters for VM '<VM_name>'
Feb 23, 2026 23:48 PM UTC -- Updating IP address for VM '<VM_name>'
Feb 23, 2026 23:50 PM UTC -- VM <VM_name> failed recovery. Error: Cyber Recovery internal error. Please contact support

Environment

VMware Live Cyber Recovery

Cause

• For Recovery SDDC, use of old mount API results in mount issue especially when multiple clusters deployed
  
  -- from irragent.log, its observed that Recovery SDDC takes longer to process or times out the call requests from IRR:

2026-02-24T01:44:06.178+0000 [.vm-recovery-short-0] ################# VM: <VM-Name>, Status: STATUS_IN_PROGRESS, CurrentState: Initiating VMC failover to dc: <datacenter>, staging datastore: <datastore_name>, primary datastore: <workload_datastore>
2026-02-24T01:44:06.270+0000 [.#############-######] ################## show_sddc invoked orgId: <org_ID> sddcId: <sddc_ID>
2026-02-24T01:44:06.869+0000 [.#############-######] ################## Relaying 1 events
2026-02-24T01:44:06.880+0000 [.irr-agent-event-producer-1] ################## Relaying 3 events
2026-02-24T01:44:16.018+0000 [.#############-######] ################## RPCClientAdapterImpl : da. aws. VmcDR. snapAndFailoverVm. ########. VmcDRService-2 was slow: took 11 seconds to complete or timeout
2026-02-24T01:44:16.961+0000 [.#############-######] ################## RPCClientAdapterImpl: da. aws . VmcDR. snapAndFailoverVm. ########. VmcDRService-2 was slow: took 11 seconds to complete or timeout
2026-02-24T01:44:17.019+0000 [.#############-######] ################## RPCClientAdapterImpl: da. aws. VmcDR. snapAndFailoverVm. ########. VmcDRService-2 was slow: took 12 seconds to complete or timeout
2026-02-24T01:44:17.069+0000 [.#############-######] ################## RPCClientAdapterImpl: da. aws. VmcDR. snapAndFailoverVm. ########. VmcDRService-2 was slow: took 11 seconds to complete or timeout
2026-02-24T01:44:17.962+0000 [.#############-######] ################## RPCClientAdapterImpl: da. aws. VmcDR. snapAndFailoverVm. ########. VmcDRService-2 was slow: took 12 seconds to complete or timeout

Resolution

Contact Broadcom Support to investigate and resolve the issue.