And a bad one. It means there is some hardware or software fault your IT staffer must track down. Don't let them wiggle out and tell you that all machines do this. Our office doesn't experience such crashes and neither should yours.
I have 5 servers in this problem -- 1 backup server and 4 others.
All are running Windows 2000 SP4 and hooked up on a local network using Ative Directory.
The 1 backup machine is a new server designed just to hold backup data from the other servers with a mirroed 400 GB drive.
We tried using NovaBackup to run the backups over a network shared drive, but it would cause the backup machine to crash about 25% of the time for each backup.
We switched to NTBackup, and the crashes are much less often (maybe 1-5% of the time now), but the scheduled backups do not always run, or they run and fail about halfway through the backup process.
One machine will not run any of its scheduled backups, yet when you run them manually they work just fine.
Another machine runs its backups on time every night, but will have a write error about halfway through about 1 out of every 3 backup jobs.
The other two machines seem to run the backup as scheduled, or not, depending on their mood.
I tried re-scheduling the times with task manager for 1 of the machines -- this seemed to work for that one as far as actually performing the backup. I read one Windows report that stated backups scheduled with the NTbackup utility do not always happen unless you "tweak" the times in Task Manager.
When I go to the scheduled tasks and look at the backup jobs that did not run, it states that it did run, and has an exit value of 0 -- no error, but the backup file was never created. Even the backups that quit halfway through with a write error will state an exit value of 0.
Seems like such a simple task -- backup data at xx:00, but obviously nothing is meant to be easy.
Anyways, any insight on this would be appreciated.