NTbackup failures notifications

NTbackup runs on two DC's I have in remote locations.   NTbackup runs as a scheduled job that pulls it's selection lists from a script (backup.bks).  occassionaly the backup will fail and never any reason as to why.  This could simply be ignorance on my part and not knowing where to find these errors.  But the event logs shows the job starting but never ending.  And the log file has nothing written to it.

Does NTBackup write to a log someplace other than event viewer so that I can document the failure for SOX?

**edit**
We do have a log file written based on when the job starts, whats skipped and when it finishes, which is only good if the backup is successful.  I'm looking for the "other" log (should one exist) that reports why the job failed.
webenerdsAsked:
Who is Participating?
 
UbuntopConnect With a Mentor Commented:
Hmm that would be odd, but the "L" is shown as a capital in the ntbackup help; while the f|s|n are shown as lower case.  The summary below is right out of the Win 2000 Server NTbackup help file.  Either way, I would change the s to f for the full log.  I think summary only shows the start and end time.

/L:{f|s|n}
Specifies the type of log file: f=full, s=summary, n=none (no log file is created).
0
 
UbuntopCommented:
C:\Documents and Settings\USERNAME\Local Settings\Application Data\Microsoft\Windows NT\NTBackup\data

There are log files in this folder for NTBackup.
0
 
webenerdsAuthor Commented:
I should have mentioned this is Windows 2000
0
Never miss a deadline with monday.com

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

 
UbuntopCommented:
Add the /L switch to your scheduled backup.
ntbackup /L:f

This will place a log in C:\winnt\backup.log.  Options are below.

/L:{f|s|n}
Specifies the type of log file: f=full, s=summary, n=none (no log file is created).
0
 
webenerdsAuthor Commented:
Well, further investigation indicates that /l:s is there, and indeed a backup log exists, however it is also blank.

Will case matter?
0
 
webenerdsAuthor Commented:
I'll edit the batch file that fires up NTBackup and change l to L and report my findings.
0
 
webenerdsAuthor Commented:
The l or L made no difference to the log files.  The backups failed for 1/31 and 2/1 and yet again I have no idea as to why.

This is frustrating.
0
 
webenerdsAuthor Commented:
I ran the batch file from the desktop via RDP and found that the backup was exceeding the one tape in the drive and the users on site would just pull the tape thinking the job was done and insert the next tape for the next day.  

While I haven't found a way to get a log from this and determine what exactly is going on, I did figure out the reason for the empty log...the backup wasnt finished.

So, while the question isnt entirely answered, it's safe enough to close.
0
 
webenerdsAuthor Commented:
Pointed me in the right direction but wasnt a complete success.  Thanks for the assistance.
0
All Courses

From novice to tech pro — start learning today.