Decommissioning VLR with vSAN Data Protection results in a lingering "vSAN Data Protection Service Health" alarm.
search cancel

Decommissioning VLR with vSAN Data Protection results in a lingering "vSAN Data Protection Service Health" alarm.

book

Article ID: 452809

calendar_today

Updated On:

Products

VMware vSAN

Issue/Introduction

In a VMware Cloud Foundation (VCF) 9.x or vSphere 9.x environment, after successfully unregistering and decommissioning a VMware Live Recovery (VLR) appliance (version 9.0.5.x), the following symptoms may occur:

  • The vSAN Skyline Health dashboard continues to trigger an alert for "vSAN data protection service health."
  • The vSAN cluster configuration correctly reflects the data protection service as "not deployed."
  • Manual triggers of the health check do not clear the alert, despite no VLR plugins or extensions remaining in the vCenter Managed Object Browser (MOB).
  • The vCenter Server version is typically 9.0.x or later

Environment

  • VMware Live Recovery 9.x
  • VMware Cloud Foundation (VCF) 9.x

Cause

The vsan-health service may retain a stale monitoring state or cached entry for the Data Protection service. This may prevent the Skyline Health dashboard from updating its status even after the service is decommissioned and the underlying registrations are removed.

Resolution

  1. Open an SSH session to the vCenter Server Appliance and log in as root.

  2. Execute the following command to restart the vSAN Health service: vmon-cli -r vsan-health

  3. Allow 60 to 120 seconds for the service to fully initialize

  4. Navigate to the vSphere Client, select the cluster, and go to Monitor > Skyline Health.

  5. Click Retest to confirm the "vSAN data protection service health" alert is cleared.

 

Additional Information

  • Verify that the appliance was removed following the official documentation: 
  • To speak with a customer representative or a Support Engineer see Contact Support. Scroll to the bottom of the page and click on your respective region.
  • For persistent plugin issues, refer to KB 414417 for cleaning up the com.vmware.drui.plugin extension.