Stale vCenter Backup Job Alerts in Aria Operations VMware Infra Management Health Overview Dashboard

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

• The VMware Infra Management Health Overview dashboard (in Operations > Dashboards > Manage page) displayed multiple vCenter backup jobs in a Gray state, despite these jobs being marked as "Not existing" in adapter logs

• These stale backup jobs persisted in the UI (in Operations > Configurations Inventory Management > Objects > Backup Job page) beyond the expected 7-day retention period

• The following events can be seen in the /storage/vcops/log/adapters/VMwareInfraHealthAdapter/VMwareInfraHealthAdapter_ID.log adapter logs:

  • 2025-04-15T18:33:57,361+0000 ERROR [Collector worker thread 3] (19447) com.vmware.adapter3.vmwareinfrahealth.VMwareInfraHealthAdapter.processData - Resource key being marked as not existing is: 20250408-######-######## [example.vCenter.com] : VCENTER_BACKUP_JOB
  • 2025-04-16T18:31:04,049+0000 ERROR [Collector worker thread 1] (19447) com.vmware.adapter3.vmwareinfrahealth.VMwareInfraHealthAdapter.processData - Resource key being marked as not existing is: 20250409-######-######## [example.vCenter.com] : VCENTER_BACKUP_JOB
  • 2025-04-17T18:33:15,489+0000 ERROR [Collector worker thread 4] (19447) com.vmware.adapter3.vmwareinfrahealth.VMwareInfraHealthAdapter.processData - Resource key being marked as not existing is: 20250410-######-######## [example.vCenter.com] : VCENTER_BACKUP_JOB
  • 2025-04-18T18:30:16,581+0000 ERROR [Collector worker thread 7] (19447) com.vmware.adapter3.vmwareinfrahealth.VMwareInfraHealthAdapter.processData - Resource key being marked as not existing is: 20250411-######-######## [example.vCenter.com] : VCENTER_BACKUP_JOB
  • 2025-04-19T18:32:11,677+0000 ERROR [Collector worker thread 20] (19447) com.vmware.adapter3.vmwareinfrahealth.VMwareInfraHealthAdapter.processData - Resource key being marked as not existing is: 20250412-######-######## [example.vCenter.com] : VCENTER_BACKUP_JOB
  • 2025-04-20T18:34:18,640+0000 ERROR [Collector worker thread 22] (19447) com.vmware.adapter3.vmwareinfrahealth.VMwareInfraHealthAdapter.processData - Resource key being marked as not existing is: 20250413-######-######## [example.vCenter.com] : VCENTER_BACKUP_JOB
  • 2025-04-21T18:31:11,901+0000 ERROR [Collector worker thread 24] (19447) com.vmware.adapter3.vmwareinfrahealth.VMwareInfraHealthAdapter.processData - Resource key being marked as not existing is: 20250414-######-######## [example.vCenter.com] : VCENTER_BACKUP_JOB
  • 2025-04-22T18:32:54,392+0000 ERROR [Collector worker thread 21] (19447) com.vmware.adapter3.vmwareinfrahealth.VMwareInfraHealthAdapter.processData - Resource key being marked as not existing is: 20250415-######-######## [example.vCenter.com] : VCENTER_BACKUP_JOB
  • 2025-04-23T18:34:50,184+0000 ERROR [Collector worker thread 21] (19447) com.vmware.adapter3.vmwareinfrahealth.VMwareInfraHealthAdapter.processData - Resource key being marked as not existing is: 20250416-######-######## [example.vCenter.com] : VCENTER_BACKUP_JOB
  • 2025-04-24T18:31:48,976+0000 ERROR [Collector worker thread 24] (19447) com.vmware.adapter3.vmwareinfrahealth.VMwareInfraHealthAdapter.processData - Resource key being marked as not existing is: 20250417-######-######## [example.vCenter.com] : VCENTER_BACKUP_JOB
  • 2025-04-24T18:31:48,977+0000 ERROR [Collector worker thread 24] (19447) com.vmware.adapter3.vmwareinfrahealth.VMwareInfraHealthAdapter.processData - Resource key being marked as not existing is: 20250417-######-######## [example.vCenter.com] : VCENTER_BACKUP_JOB
  • 2025-04-24T18:31:48,977+0000 ERROR [Collector worker thread 24] (19447) com.vmware.adapter3.vmwareinfrahealth.VMwareInfraHealthAdapter.processData - Resource key being marked as not existing is: 20250417-######-######## [example.vCenter.com] : VCENTER_BACKUP_JOB

Environment

• Aria Operations 8.18.x

• Aria Operations 8.x

Cause

• An intermittent internal processing issue within the VMware Infrastructure Health Adapter prevented the proper update of backup job object states and execution of the configured 7-day retention policy.

Resolution

• Verify that the VMware Infrastructure Health Adapter status is in Green/Collecting state from Operations > Configurations > Inventory Management > Adapter Instances > VMware Infrastructure Health Adapter Instances page.

• To address the internal processing issue with the VMware Infrastructure Health (VIH) adapter, navigate to:

  • Operations > Configurations > Inventory Management > Adapter Instances > VMware Infrastructure Health Adapter Instances

  • Stop collection for the VMware Infrastructure Health Adapter Instances.

• Restart the collection for:

  • VMware Infrastructure Health Adapter Instances

• After restart:

  • All backup jobs should transition to "Not existing" state.

 

• • The Gray status will be cleared from the dashboard.

  • Backup objects will successfully be deleted after the 7-day retention period as expected.

Additional Information

• This issue is intermittent and related to a temporary state handling failure within the adapter.

• The adapter logs repeatedly showed Resource key being marked as not existing for all affected jobs, confirming detection logic was functioning.

• Restarting the VMware Infrastructure Health Adapter clears the temporary glitch or state issue within the adapter, allowing it to correctly process the "not existing" status and trigger the retention policy.

• Reference links:

  • vCenter Backup Job

  • VMware Infrastructure Health (VIH) Adapter is missing from Integrations source