Discussion Locked

Disaster recovery

0 helpful
2 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I'm currently undergoing a project for disaster recovery of our NT servers.
I was wondering if anyone can point me to the right direction of where I can find some useful information and also sample documentations on this.
I have done some screen captures of the NT servers (PDC, BDC, Member servers)with their network configuration, hardware configuration etc.. etc..
but was wondering if theres any useful info that I can use for documentation of our NT server disaster recovery.
TIA

2 replies

by jimbb

Setting up disaster recovery is much more than just documenting how to (re)install servers. Keep *any* possible scenario in mind, to start with. In what order should you install your servers, in case they are all gone? What do you really need to be able to do so? Where do you store important info and other things, such as installation disks and CDs, patches, drivers and so? Which applications should be up and running first? How do you purchase new equipment, in case needed?
In other words, if "disaster recovery" is your scope, you need a way to do emergency purchases (including authorisation), a temporary location (in case your server room is burnt down), agreements with suppliers, agreements with other departments and so on.
Checkhttp://www.uark.edu/staff/drp/. I found this to be a quite complete and comprehensive example.

Jim

by edwarvel

Get the program from PowerQuest called Drive Image Pro and make an image of your servers. It can restore the server exactly as it was when the image was made. I have my drives partitioned so the boot partition contains only the files for the OS and all programs and data are on logical partitions. For my needs I just image that partition since I'm not so concerned w/ a drive failure as with some install corrupting my registry so I can't reboot. It can back up whole drives however. On a network you could make an image of each drive and store one copy of each image on another computer on the network so if a drive fails, for instance, you would just replace the drive and copy the image from the other computer to the new drive and restore it toit's exact state in about 20 min. This wouldn't help much if your building burned down but it would be an easy way to restore individual systems as problems arise (a much more likely occurance).

This discussion is closed to new replies.