Our Windows 2k3 standard x86 server is on deaths door. Well, not completely. 1 of the disks in the RAID5 partition went south and caused parity issues to the point that the only solution is to rebuild the RAID array. The only catch is that this is still a live production server (DC, DHCP, DNS, Application, File, and network backup services). This was not my design. I've inherited this mess. So now I have basically our entire network running on a broken RAID5 server.
Anyway, once I get the volume shadow copy service functional again which was working before the crash (I am hoping the http://support.microsoft.com/kb/891957 hot fix will fix this problem or a call to Microsoft), I am planning on doing the following:
1. Run a complete system backup of SERVERX C: drive (including system state) and its D: drive (about 450gb worth of data) using NTBackup to an attached USB drive.
2. Restore the backup from step 1 onto the new server. This new server will have a Win2k3 OS patched w/ the same rev level as the old server, with exact partitions (i.e. the C and D drive). Fix / config / replace all driver issues. This restore will be done not connected to the network. Once its in a stable state (i.e. drivers and the like). Take the old SERVERX off line and put the new SERVERX on line.
Heres the fun bit. Once I get SERVERX working on the new hardware, I will need to fix the old hardware and do this exact same process again but in reveres so I can free up the new hardware.
I would love to just rebuild the whole thing, but I just dont have the time.
Any thoughts out there on my plan? Should I use something else beside NTBackup (say, like Acronis). Ive done system state restores before w/ NTBackup, but never on a server w/ these many services.
I just realized that the Win2k3 server discs that I have are R2's. My SERVERX is not on SP1. Am I screwed using NTBackup for my move?