captaincrunch00
IS-IT--Management
Hi there,
I've got a 2003 server that has the System file go corrupt every time I reboot it.
I restore the C: and System state from Tape using Veritas' Intelligent Disaster Recovery (which works slick to same hardware) and the server boots up and runs like a champ.
I let it run a few days, then reboot it and wham, there goes that file. This has happened 3 times, and I realize it's probably because I'm restoring the same files to the drive, but I do not restore the System file or anything in the Config folder.
Any ideas as to what could be causing this, or should I just call Microsoft and see if they can figure it out?
Sadly the only way to check and see if it's corrupt is to reboot, then if it doesnt come back up I have about 4 hours of work to restore the server.
I've done all the checkdsk stuff I can, it doesnt find any errors. I do the checkdisk when the file is corrupt and I have to boot from a CD.
I've got a 2003 server that has the System file go corrupt every time I reboot it.
I restore the C: and System state from Tape using Veritas' Intelligent Disaster Recovery (which works slick to same hardware) and the server boots up and runs like a champ.
I let it run a few days, then reboot it and wham, there goes that file. This has happened 3 times, and I realize it's probably because I'm restoring the same files to the drive, but I do not restore the System file or anything in the Config folder.
Any ideas as to what could be causing this, or should I just call Microsoft and see if they can figure it out?
Sadly the only way to check and see if it's corrupt is to reboot, then if it doesnt come back up I have about 4 hours of work to restore the server.
I've done all the checkdsk stuff I can, it doesnt find any errors. I do the checkdisk when the file is corrupt and I have to boot from a CD.
