Windows server 2008 backup and restore


I am having issues with restoring my WindowsServer2008 with WindowsServerBackup2008.

I have used the registry hack to allow system state backup to the C: drive. I then backup the whole C: drive to another machine.

My current test is doing a restore test, but i get the following error message.
Recovery for volume Local Disk(C:) failed. Error: The recovery location for a volume restore cannot be a critical volume.

I can't find anymore information on this or senarios where C: drive is backed and restored.

Out test machine is a VMWare machine with only a C: drive. Usually with our physical machines we have a C: drive and a D: (data) drive. But since this is a virtual machine, we dont care that much.

So, is our C: backup strategy wrong?

If we were to do a C: & D: strategy, would we only do systemstate backup of C: and full backup of D:? In the event of C: corruption of some sort, are we faced with a restore strategy which involves SystemState followed by installing all the program files applications like Sql Server and any associated tools, basically a reinstall anyway?

A last resort we have is to use VMWare to do snapshot type backups and then transfer them to backup tape, that itself is a bit of a task and want to focus on WSB2008 in this forum before i consider that.

Just to make it clear, we backup to another machine and that machine handles the backup to the tape drive.

thanks a lot!
Who is Participating?
Windows Server Backup console

If you do Backup Schedule...
You would need another disk to do this.
In Disk Management, you'll be backing up Disk 0 (which hosts your C: and other drives if you have partition this disk) to Disk 1 (an internal drive, external drive, or a LUN volume). You can't use Disk 0 as a target for backup.

If you want to restore to a network location (ie your backup server's shared folder), then go through the Backup Once procedure or create a script (using wbadmin command lines) or use the task scheduler to do it for you.

Check out the Step 3 video on this link to see how it's done:

Here's another link that goes into more depth regarding scheduling backups with wbadmin and the task scheduler:
The backup image cannot be located on the same partition that you're going to restore it to.

Why not save the backup image to a network share (or a local partition or an external storage device) and then pull it from that location when you need to restore?

The backup image just needs to be saved in a location other than the one your backing up.
ValimaiAuthor Commented:
Hi. thanks for joining the discussion.

The backup process is:
Backup System State to C: (cannot do this to remote machine).
Backup C: directly to BackupMachine (remote) and this will include SystemState that is on C: now.
Restore to C: directly from BackupMachine (remote)

Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

ValimaiAuthor Commented:
Hi aldanch, just to let you know that the netometer link was helpful. Based on a clue in the video, I am running some tests (fingers crossed). Ill post my results back here soon.
Looking forward to reading the results!
ValimaiAuthor Commented:

this is the gem I was looking for.

this means i can use the solitary C: drive method and restore over the network.

Also, from my original post, i mention that i use a system state backup hack. This is not needed. A backup using switch -allcritical is a systemstate backup. Finally, since i can restore over network, and it does a system state restore. Everything is ok.

The other clue which I didnt test was that a backup is actually a hyper-v drive file which can be mounted without restore. Since we are using VMWare, it would take a conversion to use this file which is not very good if the file is large i guess. (untried).

thanks for sticking with me. The issue was difficult because there were not many resources on WSB2008 and while you did not have the exact answer, you added some clues.


Thanks! I've bookmarked that link for future reference.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.