Funny thing about that Windows server 2003, the backup decided to stop working one day. I kicked off the job manually and noticed the backup program come up and then close after a few seconds. Before getting to far, I just happened to notice event 8017 listed which turned up the following information:
Microsoft's
Article ID: 828402 titled Backup (NTBackup.exe) stops during the backup process and event 8017 is logged states that there is a HotFix available, but to apply it only if you are severly affected.
Since the customer was not freaking out about any critical data I felt that we weren't severly affected and opted for a different approach.
The following lines placed in a batch file work just fine. The scheduler can run the batch file just like running the ntbackup, but this way all the switches are in a file that is much more difficult to mess up. Plus, this uses a variable to specify the name of the day of the week and adds it to the backup job name.
@echo off
FOR /F "tokens=1-4 delims=/ " %%I IN ('DATE /t') DO SET mydate=%%I
C:\WINDOWS\system32\ntbackup.exe backup D:\ /um /n "Daily Backup-%mydate%" /d "D-Drive %mydate%" /v:yes /r:no /rs:no /hc:on /m normal /j "Daily Backup" /l:f /p "8mm AIT"
C:\WINDOWS\system32\ntbackup.exe backup C:\ /um /t "Daily Backup-%mydate%" /d "C-Drive %mydate%" /a /v:yes /r:no /rs:no /hc:on /m normal /j "Daily Backup" /l:f
( )
