Hi All,
I have 3 ESXi 4.1 hosts being managed by a dedicated VM running vCenter. Its been up and running fine for about 10 months, but in the last month we have started getting errors each day in the ADAM [VMwareVCMSDS] Event Log for ADAM [VMwareVCMSDS] Replication. The errors are:-
This directory partition has not been backed up since at least the following number of days.
Directory partition:
DC=virtualcenter,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 haven't 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)
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
And also the same error for
Directory partition:
CN=Schema,CN=Configuration,CN={C20BDF6E-5292-4C71-BE6F-5F7DCC59E32C}
and
Directory partition:
CN=Configuration,CN={C20BDF6E-5292-4C71-BE6F-5F7DCC59E32C}
Now I logged a call with support who told me its because NT backup needs running for a System State. I have been doing this every day since the servers went live anyway and this completes each day without errors, but it only started happening over the last few weeks (more than the 90 day tombstone). They checked the datastamp on the DB and looks like the vcenter adam db isn't getting updated when the system state completes.
They are still looking at it, and ahve suggested I run a powershell script to backup the adam instead, but I can't do this with the script I have found as it requires the dsdbutil.exe from Server 2008 but we run Server 2003 R2.
Any ideas what I can do to resolve this?
Thanks,
Andy
