After upgrading to or installing VMware Live Recovery 9.0.x (formerly Site Recovery Manager), you may observe the following behavior in the vSphere Client:
com.vmware.vc-site-recovery solution user initiates repeated "Check compliance" and "Apply Solution" tasks.
VMware Live Recovery 9.0.4, 9.0.5
In Live Recovery 9.0.4 and newer, the XML (/opt/vmware/hms/conf/hms-configuration.xml) no longer exists.
This issue occurs because the VMware Live Recovery appliance is configured by default to automatically push the vmware-hbr-agent VIB to all ESXi hosts in connected clusters via vSphere Lifecycle Manager (vLCM).
The task stalls at 5% if vLCM cannot place a host into Maintenance Mode to complete the VIB installation. Common environmental blockers include:
Note on Directory Changes: In VMware Live Recovery 9.0.5 and later, the directory structure has changed. The configuration file previously located at /opt/vmware/hms/conf/hms-configuration.xml has moved to /opt/vmware/etc/hms/hms-configuration.xml.
To resolve this issue, you must disable the hms-auto-install-hbragent-vib property on the Live Recovery appliance.
root.true):
Step 1: Check the current setting Run the following command to check the status of the hms-auto-install-hbragent-vib property:
grep -i hms-auto-install-hbragent-vib /opt/vmware/etc/hms/hms-configuration.xmlNote: Review the output. If the value is set to
true, proceed to Step 2. If it is alreadyfalse, no further action is needed.
Step 2: Disable the auto-install setting If the setting is currently true, run the hms-configtool to set it to false:
/opt/vmware/hms/bin/hms-configtool -cmd reconfig -property hms-auto-install-hbragent-vib=false
Step 3: Restart the HMS service To apply the configuration changes, restart the Host Management Service (HMS):
systemctl restart hms