This is a known issue affecting vRealize Operations. There is no resolution at this time.
Workaround:
To work around the issue:
- Log into the vRealize Operations User Interface (UI) in a browser
Example: https://vRealizeOperationsIPorFQDN where vRealizeOperationsIPorFQDN is the IP or Fully Qualified Domain Name (FQDN) of your instance
- From the Administration > Solutions page, stop the SDDC Management Pack adapter instance(s)
- Navigate to Administration > Inventory
- Expand Object types, and then select VCenterBackupJobs
- In the toolbar along the top of the Inventory Screen, click the red square (stop button) to stop collection for any old VCenterBackupJobs objects.
Note: If the above steps do not resolve the issue, please proceed. In vCenter, there is a file that retains the last state of these backup jobs that can become stale. This file can be safely removed as it will be generated again when the next backup job is started.
- SSH into the vCenter Server Appliance as root
- Create a temporary directory
mkdir /storage/applmgmt/backup_restore/tmp/
- Move the current backup-history.json file into the temporary directory
mv /storage/applmgmt/backup_restore/backup-history.json /storage/applmgmt/backup_restore/tmp/
- Restart the applmgmt service
service-control --restart applmgmt
- Start the SDDC management pack adapter instance (s) and monitor for new alerts