The procedures outlined in the article are pretty complete. But it shoudn't have to come to this. This example stresses the importance of preparedness.
- Plan for different kinds of disasters. One DC going down in a multi-dc environment is one thing, but what do you do when you're entire DC structure gets corrupted? Think about a schema update gone bad, virusses, malicious user.
- Verify. A plan is great, but it does you no good if for whatever reason it doesn't work. So test you're backups regularly, make sure all required people know where to find backups, ADRM passwords etc.
And of course, learn from mistakes made.
my 2 cents
Keep Up with TechRepublic