Re: dcdiag - replication Concerns

Meinolf,
some of those questions I will not be able to answer now. I have started
this job 2 weeks ago and am still learning the environment and configs. So
it is in trying to understand the configuration that I run dcdiag, replmon,
checking event logs, etc and notice this error. But based on what I know
there is no backup currently being done of AD. So I will take a look at the
other domain controllers and make a decision as to what to do later. I
figured I may have to follow similar procedures as you suggested, but i just
wanted other opinions before I go that route.
thanks
Nik



"Meinolf Weber [MVP-DS]" <meiweb@(nospam)gmx.de> wrote in message
news:6cb2911d70138cc1470f2716605@xxxxxxxxxxxxxxxxxxxxxxx
Hello Nik,

If a DC is over the tombstone lifetime, you have either replication
problems in your domain or the machine was disconnected/shutdown longer
then the shown 60 days.

So you have to demote the DC, cleanup AD database, AD sites and services
from it and promote it again. Sometimes it can be possible to bring it
back to replication according to:
http://technet.microsoft.com/de-de/library/cc757610(WS.10).aspx

To help you further we need more information about the complete domain
setup, amount of DCs and sites where they are located. Did you have
restored a DC after a crash before form an image or other not supported
backup for AD restore?

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and
confers no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

Morning Guys,
Just a a quick check for any ideas on why this may be. I am receiving
the
following error when I run dcdiag.exe.
Doing primary tests

Testing server: Locale\Server1
Starting test: Replications
REPLICATION-RECEIVED LATENCY WARNING
Server1: Current time is 2009-10-05 09:30:21.
DC=ForestDnsZones,DC=my-domain,DC=lab
Last replication recieved from Server1 at 2009-03-30
12:27:04.
WARNING: This latency is over the Tombstone Lifetime
of 60
days!
DC=DomainDnsZones,DC=my-domain,DC=lab
Last replication recieved from Server1 at 2009-03-30
12:27:05.
WARNING: This latency is over the Tombstone Lifetime
of 60
days!
CN=Schema,CN=Configuration,DC=my-domain,DC=lab
Last replication recieved from Server1 at 2009-03-30
12:26:36.
WARNING: This latency is over the Tombstone Lifetime
of 60
days!
CN=Configuration,DC=my-domain,DC=lab
Last replication recieved from Server1 at 2009-03-30
12:26:32.
WARNING: This latency is over the Tombstone Lifetime
of 60
days!
DC=my-domain,DC=lab
Last replication recieved from Server1 at 2009-03-30
12:26:41.
WARNING: This latency is over the Tombstone Lifetime
of 60
days!
All other tests are successful - 'passed'. All ideas welcome!
Thanks
Nik




.

Relevant Pages

  • Re: dcdiag - replication Concerns
    ... If no backups exist i would follow asap this way for backup: ... Last replication recieved from Server1 at 2009-03-30 ... WARNING: This latency is over the Tombstone Lifetime ...
    (microsoft.public.windows.server.active_directory)
  • dcdiag - replication Concerns
    ... REPLICATION-RECEIVED LATENCY WARNING ... Last replication recieved from Server1 at 2009-03-30 ... This latency is over the Tombstone Lifetime of 60 ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD Replication - DCDIAG
    ... As Jorge Pinto said you probably didn't monitor the replication at regular ... REPLICATION-RECEIVED LATENCY WARNING ... This latency is over the Tombstone Lifetime of 60 ...
    (microsoft.public.windows.server.active_directory)
  • Re: dcdiag - replication Concerns
    ... As said before 2 ways to fix the tombstone lifetime problem, ... from above about getting replication back to work or remove the DC. ... REPLICATION-RECEIVED LATENCY WARNING ... WARNING: This latency is over the Tombstone Lifetime ...
    (microsoft.public.windows.server.active_directory)
  • AD Replication - DCDIAG
    ... WARNING: This latency is over the Tombstone Lifetime of 60 days! ... (Event String could not be retrieved) ...
    (microsoft.public.windows.server.active_directory)
Loading