Some things to consider as you take this approach:
Write down what you're thinking. Why? Because it'll help to focus the thoughts. This can have a lot of moving parts in the process and it helps if you can keep your focus on the end goal at all times - even when you get mired down in politics.
If you lose the root domain, you have some big issues. It could happen, but I highly suggest you leave room in your report/guide for improvements aimed at shoring up any weaknesses in the processes that are followed to support the root domain. Of all, that is a very critical domain to ensure it is always running and available. Take into account all 8 layers when you do this.
Put a value on the assets (domains in this case) in the scenarios. For example, is it as important if you lose that 20 person domain in South Florida? How important to the overall business? Is it important if you lose the root domain? How important? What's the relative value to the business?
The reason I say that is because when you start down this path there will be a recommendation to make improvements as well as to how you approach the backup/restore process. If you have some values assigned, you can better prioritize and justify expenditures of time and money.
Good luck!
Al
On 9/26/06, Yann <[EMAIL PROTECTED]> wrote:
Thanks Al for advices. :)Guido pointed me to some very usefull papers on recovery.Maybe my first job will be to understand the different types of AD recovery in order to master the whole procces.Some questions i have to face are :-> What if a whole domain crashes (Root and Childs) ?-> What is a whole sites crashes ? And that sites contains several DCs for other domains ?My goal is to (try to)make a recovery as fast as possible and with minimal effects on end users.Cheers,There's a whitepaper on Microsoft's website. I think there are several blogs out there talking about same.
Things to look for? Timing of backups. Name resolution. Time sync. DA accounts. Backups from DC's or GC's (you'll want to pay attention to that). Role holders.
Shouldn't be too bad otherwise.
Kind of messy while you clean the orphaned DC's out of the mix seems to otherwise work well in the lab.
I highly suggest you spend a lot of time up front detailing the requirements and timelines so that you can make the solution fit the requirements vs. the other way around.
My $0.04 worth anyway.
On 9/26/06, Yann < [EMAIL PROTECTED]> wrote:Hello all,I have to write a forest disaster reocvery plan fonr my entrerprise, and also test this plan in a test lab.We have AD 2k3 forest in FFL mode with:-> one "empty" root : no resources, only for security reason (to secure Entreprise & Ad domain admin).-> 3 childs domain.-> each DCs have AD integrated dns zone.-> Wins are also part of the infrastructure.-> 20 AD sites.I don't know where i have to start. Is there a roadmap or a step-by-step guide that describes the different strategies of a good recovery ?And if experts in this list have good advices, they are welcome :)Thank you very muche,Yann
Découvrez un nouveau moyen de poser toutes vos questions quelque soit le sujet ! Yahoo! Questions/Réponses pour partager vos connaissances, vos opinions et vos expériences. Cliquez ici.
Découvrez un nouveau moyen de poser toutes vos questions quelque soit le sujet ! Yahoo! Questions/Réponses pour partager vos connaissances, vos opinions et vos expériences. Cliquez ici.
