This usually occurs right after a restart of the services because the interval hasn't yet occurred for roll-up to happen. Wait for a day and it should disappear.
After 2 days, the alarm is still here.
You may want to apply the workaround as described in this KB.
The KB mentions changing the 1 day interval to 5m, mine is already set to 5m, its the default:
You might try to alter the interval down to something lower than 5 minutes, let it run for a day, and change it back.
Hi,
I configured for 3m, left it 1 day, then back to 5m, and let it for 1 more day, but problem persists.
Check for any hostname conflicts. I faced the same issue and it was found to be a duplicate hostname in the network. Disconnected NW from that server and checked the vCenter, the issue got resolved.