After converging the VLR (9.0.4) appliance, it is no longer accessible

Products

• VMware vSphere ESXi

Issue/Introduction

• The VMware Live Recovery (VLR) 9.0.4 appliance becomes inaccessible after an attempted converge operation.

• Rebooting the appliance fails during the service initialization phase.

• The appliance console displays the following error message:

                    "Integrity: Problem loading X.509 certificate -22"

 

             

 

• Multiple services are skipped during the boot process, leaving the appliance in a non-operational state

Environment

VMware Live Recovery : 9.0.4

Cause

This condition is caused by the presence of legacy (non-enhanced) replication data during the convergence workflow to VLR 9.0.4. The convergence process is designed to require that all existing replications be migrated to an enhanced replication state prior to execution. If legacy replications remain registered within the database, a ServiceExportFault is triggered, resulting in an incomplete architectural state and service failure.

Cause Validation:

 The va-config.log file located at /opt/vmware/support/logs/va-config/va-config.log contains entries indicating failure of the convergence task due to existing legacy replications.

         getConfigureTaskProgress - Processing request to 'getConf igureTaskProgress'
    2026-02-18 07:51:46,972 [srm-reactive-thread-30] WARN com.umware.dr.configservice.taskMonitor.ConfigureTaskHandler####a getConfigureTaskProgress - Task finished with error!
    (drConfig.fault.ServiceExportFault) {
    faultCause = null,
    faultMessage = null,
    component = hms,
    reason = (umodl.LocalizableMessage) {
    dynamicType = null,
    dynamicProperty = null,
    key = hms.migration.9.0/checkExport.sh.2,
    arg = null,
    message = Legacy replications present.

        script = 9.0/checkExport.sh,
    exitCode = 2

        at java.base/jdk. internal.reflect.DirectConstructorHandleAccessor.newInstance(Unknown Source)
    at java.base/ java. lang.reflect.Constructor.newInstanceWithCaller(UnknownSource)
    at java.base/ java. lang.reflect.ReflectAccess.new Instance(Unknown Source)
    at java.base/ jdk. internal.reflect.ReflectionFactory. new Instance(Unknown)

Resolution

1. Unregister the Newly deployed VLR appliances. 

2. Power on old vSphere replication appliance and reconfigure with VCenter and validate if any legacy replications are present.

3. Reconfigure the Legacy replications into Enhanced replications. 

 How do I reconfigure existing replications to use vSphere Replication with enhanced replication capabilities

4. Deploy a New VLR appliance and proceed with Converge of appliance. 

    Deploy Live Recovery appliance :