Instead of Lag Site, we do have a site and domain dedicated to Root operations. I think of this as the Quarterback strategy. Don't let it get sacked.
We have two DC's dedicated to Root AD functions in their own namespace. The Enterpise functions are Schema extension, forest Security operations, and DR. Since AD's take their namespace from the root of the directory, it is important to be able to recover this domain. So our DR process allows us to do Bare metal restore if nessesary. I do think it could be improved by doing P to V backups of these servers as an alternative. Todd -----Original Message----- From: David Adner To: ActiveDir@mail.activedir.org Sent: 5/21/2005 5:08 AM Subject: RE: [ActiveDir] AD DR - replication lag site----Why? I read Joe's comments as not creating a lag site per-se, but using virtual DC's which are periodically saved (I'll refrain from saying backed up since it's not a "backup", as was recently discussed) in order to perform a Forest-wide recovery. I don't think he was referring to recovery of a few deleted objects. > Joe, you pretty much agreed with the lag site proposition > towards the end of your piece. Whether you virtualize it, put > it is a different physical location or just put it on a piece > of hardware sitting in the same server room and configured > with a different replication schedule, it all comes down to > the same necessity of having a pristine DC that has not > received your deletion and from which you can repopulate your > F'ed up AD. List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
