unless you have some critical reason to do so, there's no real need to backup all DCs for data recovery reasons (i.e. restoring objects in AD). You may still want to do a backup where there are really slow lines to improve recovery of hardware failures - otherwise it's a good practice just to rebuild them and have them replicate the database again.
but whatever you do, you shouldn't leave it up to the responsibility of each site - instead I'd suggest to control the backup centrally as you'd also want to control the restore centrally (the other admins can otherwise screw up your environment more quickly than you think). /Guido -----Original Message----- From: Donovan, Michael [mailto:[EMAIL PROTECTED] Sent: Mittwoch, 19. November 2003 21:21 To: [EMAIL PROTECTED] Subject: [ActiveDir] Backup Topology Suggestions Hi- I'm hoping someone can offer suggestions: we are moving over to an AD infrastructure next month and I am trying to come up with a good backup topology, not a plan, that would allow us to capture a complete backup of the AD in a domain with 4 sites: LA, Phila, and London and Spain. My connection to LA and Phila is good, London to LA and Phila is marginal, and Spain is below marginal. Each site will be responsible for there own backup. My question: Is it a practice to re-define, or just define, replication partners, times and costs so that the Admin can schedule a backup after a known replication process finishes? Michael Donovan [EMAIL PROTECTED] List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
