Posts Tagged ‘ADAM’

vCenter Server Error – Directory Partition has not been Backed Up

December 6, 2010 4 comments

During one of our weekly vHealth reports that run against our ESX environment, we noticed a new error showing up for our vCenter server. The error was complaining about the Directory Partition not being backed up. After checking the event logs on the vCenter server, the following error was found:

This directory partition has not been backed up since at least the following number of days. Directory partition:DC=virtualcinter,DC=vmware,DC=int ‘Backup latency interval’ (days):90 It is recommended that you take a backup as often as possible to recover from accidental loss of data. However if you havent taken a backup since at least the ‘backup latency interval’ number of days, this message will be logged every day until a backup is taken. You can take a backup of any replica that holds this partition. By default the ‘Backup latency interval’ is set to half the ‘Tombstone Lifetime Interval’. If you want to change the default ‘Backup latency interval’, you could do so by adding the following registry key. ‘Backup latency interval’ (days) registry key: System\CurrentControlSet\Services\NTDS\Parameters\Backup Latency Threshold (days)

Obviously, this error threw up a flag with us. We backup our server on a regular basis and couldn’t figure out where this alert was coming from. After some digging we came across a KB Article from VMware, basically saying this error could be ignored.

This message does not impact the vCenter Server functionality and can be safely ignored because vCenter Server automatically backs up the ADAM database into the vCenter Server database.
A complete copy of the ADAM database is kept in the VPX_BINARY_DATA table of vCenter Server database. To know the last time when the ADAM database was backed up, see the CREATED_TIME column of the VPX_BINARY_DATA table.

The entire KB article can be found HERE. The one thing that did baffle us is that we do take system state backups of our vCenter server, however, something isn’t triggering the Backup Latency Interval to reset. We are still looking into this, though since it’s more or less a false alert, it has moved down the priority list. As soon as there is more info, I’ll update this post. If anyone has seen this before, feel free to share your thoughts or experiences.