Disaster Recovery Plan for complete system restoration

[Roman]

All,

I'd like some real-world advice please. I manage a small 5 user
client-server network with a tight budget. The network uses a single server
running Win 2K3 R2. The server has several additional roles including IIS
with WSS3 and a suite of applications running under Terminal Services.

I've progressively worked through the precautionary steps including hardware
RAID1 and daily backups using NTbackup to an external USB hard drive.

I have an ever present linguring concern about disaster recovery. I've
researched and read numerous tutorials and MS articles however many
real-world forum threads are not so comforting. A real-world thread I read
only days ago highlighted the requirement to ensure all Service Packs and
critical updates are applied to the Windows server installation before
restoring a System State otherwise it will fail. Apparently this information
is not made evident in any articles according to the author. I have spent 3
days attempting a System State restoration once before and I was unsuccessful.

I'd like to step through my plan in the hope that I can get some guidance in
what can be improved to increase the likelyhood of success. Apparently 35% of
all system restorations from tape fail according to
http://www.computerperformance.co.uk/w2k3/disaster_recovery_backup.htm.

I have scheduled a full system backup, using ntbackup, each morning to
external HD - it only takes 1 hour. I've actually manually selected C:
(SystemData), D: (UserData), and System State because I don't want F:
included because it is the external drive containing the backups. The backups
are appearing on the external drive and I've successfully restored individual
files to test the process.

In the event a system restoration is required my plan is:

1. If required, replace both RAID1 HDs and partition C: and D: the same size
as they are now,
2. Install the OS,
3. For a full system restoration there is no need to apply Service Packs and
critical updates,
4. No need to run DCpromo,
5. Start ntbackup and start a full system restoration using the Advanced
wizard, and
6. Restart the server and all will be fine

Now, the way I understand it because I am running a single server and will
be doing a full system restoration, not just System State, I don't need to
follow the authoritative restoration guidelines and repair for AD at bootup?

 

[Pegasus \(MVP\)]

"Roman" <roman(at)romanportal(dot)com> wrote in message
news99D6A93-1E3D-42A7-A34D-D683DCE54A7F@microsoft.com...
> All,
>
> I'd like some real-world advice please. I manage a small 5 user
> client-server network with a tight budget. The network uses a single
> server
> running Win 2K3 R2. The server has several additional roles including IIS
> with WSS3 and a suite of applications running under Terminal Services.
>
> I've progressively worked through the precautionary steps including
> hardware
> RAID1 and daily backups using NTbackup to an external USB hard drive.
>
> I have an ever present linguring concern about disaster recovery. I've
> researched and read numerous tutorials and MS articles however many
> real-world forum threads are not so comforting. A real-world thread I read
> only days ago highlighted the requirement to ensure all Service Packs and
> critical updates are applied to the Windows server installation before
> restoring a System State otherwise it will fail. Apparently this
> information
> is not made evident in any articles according to the author. I have spent
> 3
> days attempting a System State restoration once before and I was
> unsuccessful.
>
> I'd like to step through my plan in the hope that I can get some guidance
> in
> what can be improved to increase the likelyhood of success. Apparently 35%
> of
> all system restorations from tape fail according to
> http://www.computerperformance.co.uk/w2k3/disaster_recovery_backup.htm.
>
> I have scheduled a full system backup, using ntbackup, each morning to
> external HD - it only takes 1 hour. I've actually manually selected C:
> (SystemData), D: (UserData), and System State because I don't want F:
> included because it is the external drive containing the backups. The
> backups
> are appearing on the external drive and I've successfully restored
> individual
> files to test the process.
>
> In the event a system restoration is required my plan is:
>
> 1. If required, replace both RAID1 HDs and partition C: and D: the same
> size
> as they are now,
> 2. Install the OS,
> 3. For a full system restoration there is no need to apply Service Packs
> and
> critical updates,
> 4. No need to run DCpromo,
> 5. Start ntbackup and start a full system restoration using the Advanced
> wizard, and
> 6. Restart the server and all will be fine
>
> Now, the way I understand it because I am running a single server and will
> be doing a full system restoration, not just System State, I don't need to
> follow the authoritative restoration guidelines and repair for AD at
> bootup?

Most system restores fail because the server administrator never
takes the time to perform a live system restore. It's as simple as
this. Here is what I usually do:
1. I create an image file of the system drive, using Acronis TrueImage.
2. I restore the image file to a spare IDE disk. Disks are cheap!
3. I boot the system with this IDE disk. I now know whether my
methods works or not.
4. I create a new image file twice each year, always keeping the
two most recent versions.
5. I create a new image file before any major upgrade, e.g. before
installing a service pack.

If Acronis TrueImage is too expensive for you then you could
create an image disk like this:
- Format a spare IDE disk on some WinXP PC.
- Boot the server with a Bart PE boot CD.
- Use robocopy.exe to copy the system drive to the IDE disk.
Include hidden files & permissions.

Creating a Bart PE boot CD (www.bootdisk.com) takes a bit
of time but it is a terrific tool for a system administrator.

The essential thing in all this is: You MUST test your recovery
process!

 

[Edwin vMierlo [MVP]]

>
> The essential thing in all this is: You MUST test your recovery
> process!
>

As Geoff N. Hiten (SQL MVP) would say:

If you don't test your recovery process, you do NOT have a recovery process,
you have a recovery HOPE !!!!

 

[Pegasus \(MVP\)]

"Edwin vMierlo [MVP]" <EdwinvMierlo@discussions.microsoft.com> wrote in
message news:uMtWsGMYIHA.4208@TK2MSFTNGP04.phx.gbl...
> >
>> The essential thing in all this is: You MUST test your recovery
>> process!
>>
>
> As Geoff N. Hiten (SQL MVP) would say:
>
> If you don't test your recovery process, you do NOT have a recovery
> process,
> you have a recovery HOPE !!!!
>

You put it much better than I did!