A popular way to do what you discuss is to change
replication parameters during the upgrade. Basically, have the ADC talk to
an Active Directory isolated server, check for errors and then bring it back
into the replication cycle.
Another alternative I've seen work is to take a DC off-line
during the upgrade. I've seen some introduce a new one first and then
bring it off-line during the upgrade. After the all clear, it's then
removed from the domain else brought back on-line.
The first option is much better as it offers you a chance
to check it out prior to moving forward. The second option works if you
can flatten all DC's but the one with the good data, in essence creating a hot
backup. I suppose you could just mark all the records authoritative and
then reintroduce it, but....
I've never seen a successful ADC deployment that didn't
spend a lot of time in the lab getting it right.
Al
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Strand, Ted
Sent: Tuesday, August 03, 2004 3:34 PM
To: [EMAIL PROTECTED]
Subject: [ActiveDir] AD Backup - Sort of
I am
about to turn on a connection agreement for my first AD connector. I have
backed up the exchange directory and also exported the directory to csv for
recovery. I would like to do the same thing with the AD data to have a
roll-back plan if the CA does something I didn't expect. I have played
with LDIFDE and the CSV equivalent, and although I have been able to export with
both, I have not been able to import back in to change the data. Are there
any other (preferably free) methods to capture this ad data, and then reuse it
to undo changes? I would hate to have to do an authoritative restore from
tape to fix any issues.
Thanks
-Ted
Strand-
