Create a bootable recovery CD with ntbackup for Windows Server 2003 R2 SP2

[KLynnM333]

We have a Windows 2003 R2 SP2 webserver that is currently backed up using ntbackup (the Windows backup tool). Our backups are stored on a shared drive of our file/print server. The webserver doesn't have a floopy drive so if it ever when down we would be able to restore it.

Ideally, in a server crash we want to be able to insert the CD and run ntbackup off of it and restore the server from there.

I tried Googling how to create bootable CDs and the only thing that I found was how to create bootable installation CD.

Our network guy asked me to do this in July and after many fail attempts I resorted to posting to this forum.

I tried BertPE and it worked but I was unable to run ntbackup out of the enviroment and I was also having issues connecting to our network. I also tried the instructions at http://www.nu2.nu/bootcd/ but Nero's site no longer carried the ASPI manager in needed.

Usually our network guy would handle this but I am the only person will a floopy drive in our IT department. I am just a Programmer, and have a somewhat limited understanding of how networking works and booting from a CDs work, but I am willing to learn.

Here's somethings that I know need to be on the CD:

CD-ROM boot sector
CD-ROM Drivers
ntbackup.exe
MS-DOS (maybe?)
and probably some other thing to connect to the network

Is there anything else I could be missing or an another direction that I should take?

Thank you for your replies.
KLM

[epots9]

i could be wrong but i think ntbackup can only run when windows is running.

But i recommend trying something like Norton Ghost (http://shop.symantecstore.com/store/...uctID.90124600), it can create simple backups like ntbackup or full image backups.

with a full image backups, it will backup the complete harddrive so in the event of a hardrive failure and a new harddrive is required you can load the image onto the new harddrive and the system will run has nothing had ever happened.

[KLynnM333]

Thanks for the help, we ended up using a server backup program.