NTBackup event log shows completed, but actually it's not.

I run a backup using NTBackup, and log the output to a file. In the Event Viewer, it says the backup completed as normal (Event ID 8001), but when I checked the log it's not. Upon completion, the log file is supposed to show the backup size, date, time but it doesn't. Why is it so?
yatieAsked:
Who is Participating?
 
YensidModConnect With a Mentor Commented:
PAQed per request/recommendation - No Refund

YensidMod
Community Support Moderator
0
 
Netman66Commented:
Do you have Detailed or Summary selected for the logging type?

0
 
yatieAuthor Commented:
Event log:

Event ID:8001, Source: NTBackup, Type: Info
Description: EndBackup of 'E:' Verify:Off Mode:Append Type:Normal

The log file should be like this:

aaa.xls
Backup completed on mm/dd/yy at hh:mm:ss.
Backed up xxxxx files in yyyy directories.
Processed zzzzzz in hh hours, mm minutes, and ss seconds

But, this part went missing, and the backup is confirmed not completed by checking the content of the log file, cataloging, and compare with the directories.
0
Learn to develop an Android App

Want to increase your earning potential in 2018? Pad your resume with app building experience. Learn how with this hands-on course.

 
Netman66Commented:
Does anything get logged in that file?  Is it even created?

Perhaps, the SYSTEM no longer has proper access to the log directory?  Just a guess.

Advise.



0
 
nicholaspCommented:
Firstly, is the backup being performed with the "/e" option? if so then it will not log everything only exceptions.

Secondly is the backup set to varify? if so it may be hanging on varify - if so check your scsi card.

Next, how old is your media? if it is over 2 years old and your verify is failing you will probably need new tapes.

One final thing to check... is your machine running from a UPS,  if so make sure your backup drive is on the UPS also (assuming it is external)
0
 
nicholaspCommented:
turn on verify. if it fails, it's probably your hardware.
0
 
yatieAuthor Commented:
netman66,
as I said, only that part is missing. the log file was generated, but not completed as in the earlier msg.

nicholasp,
1. nope
2. nope. verifying will double the whole backup process. tested earlier.
3. new
4. internal tape drive.
5. h/w is ok. this is an injtermittent problem. most of the time it's ok, using the same script.

anybody else has experience in this?

0
 
netmachCommented:
yatie, what is the make/model/firmware of the tape drive?

0
 
paullamhkgCommented:
No comment has been added lately, so it's time to clean up this TA.
I will leave a recommendation in the Cleanup topic area that this question is to:

Be PAQ'd/Points No Refunded

Please leave any comments here within the next seven days.

PLEASE DO NOT ACCEPT THIS COMMENT AS AN ANSWER!

Paul
EE Cleanup Volunteer
0
All Courses

From novice to tech pro — start learning today.