Backup constantly Failing

[nuedge]

Hi all!

I have a job running daily. It backs up 51gb every day - pretty much all the data. the problem is I'm ALWAYS getting a FAILED message. I thought it was because it was skipping to many files but these are all the files it skips:

The item \Users\fyaz\OUTLOOK\Outlook.pst in use - skipped.
The item \Groups\Vauxhall\2002\Job Numbers\National Tactical Job Numbers.doc in use - skipped.
The item \Groups\Vauxhall\2002\Job Numbers\ADapt Job Numbers.doc in use - skipped.
The item \TEMP\~DFA3B6.tmp in use - skipped.
The item \TEMP\~DFA3C6.tmp in use - skipped.
The item \WINNT\JET1.tmp in use - skipped.
The item \WINNT\JET180.tmp in use - skipped.
The item \WINNT\JET3.tmp in use - skipped.
The item \WINNT\NETLOGON.CHG in use - skipped.
The item \WINNT\~DF772E.tmp in use - skipped.
The item \WINNT\Profiles\Administrator\Cookies\index.dat in use - skipped.
The item \WINNT\Profiles\Administrator\History\index.dat in use - skipped.
The item \WINNT\Profiles\Administrator\Temporary Internet Files\index.dat in use - skipped.
The item \WINNT\system32\CPL.CFG in use - skipped.
The item \WINNT\system32\DNS\dns.log in use - skipped.
The item \WINNT\system32\DTCLog\DTCXATM.LOG in use - skipped.
The item \WINNT\system32\DTCLog\msdtc.log in use - skipped.
Access denied to directory \WINNT\system32\spool\PRINTERS.
^ ^ ^ ^ ^
The item \WINNT\system32\wins\j50.log in use - skipped.
The item \WINNT\system32\wins\wins.mdb in use - skipped.
The item \WINNT\system32\wins\winstmp.mdb in use - skipped.
The item \Desktop DB in use - skipped.
The item \Desktop DF in use - skipped.
The item \Desktop DB in use - skipped.
The item \Desktop DF in use - skipped.

Surely that isn't enough to get a Failed message?

Could there be any other reason??

Thanks in advance

 

[sdeb]

Maybe yes,

All depends wich version of BE you're using, I think that in older versions the open files were generating a "failed backup".

It would be easier for you to skip those files in you job selections to avoid all error messages (if there're not needed like "tmp" files) .

Bye.

 

[zoeythecat]

Backing the Winnt directory you will get failed message because of files that can not be backed up (I.E - WINS database needs to be backed up while it is offline). I bet if you exclude the Winnt directory from being backed up you will not get a failed message. Of course, you can still keep this as a backup selection and some files will get backed up but some will not and will give you a failed error message in the backup log. Also, when you see messages like this ==>Access denied to directory \WINNT\system32\spool\PRINTERS. <== can cause a failed message as well.
^ ^ ^ ^ ^

 

[nuedge]

thing is, I never used to get the messages even though i was backing up the winnt files

 

[zoeythecat]

Interesting. What type of backups are you running? I know I get the same failed messages from my &quot;Full Backup&quot; because I am backing up all kinds of directories and get same type of messages as you in the log. There may be some directories you are backing up that require a backup agent to backup open files. I pretty much gave up on the failed messages because I monitor the logs weekly and know the backup is working. It would be nice to get rid of the &quot;Failed&quot; message though. My differential backup works with no messages.

Sorry to be not much more help than this.

 

[SQLBill]

I have found that in BE v8.6 if it skips even one file, it marks the job 'failed'. This is because it 'failed' to do the job required. That doesn't mean the whole job failed and that's where the messages come in handy. You can do like you did and check to see exactly what failed and if they aren't important to you, just ignore them.

-Bill

 

[protos]

Not correct, if you see a &quot;skipped&quot; file in 8.6 that does not cause a fail on the job.

Yes fail at the end can be misleading because you can have a successful backup job and still get a fail at the end, but skipped files do NOT cause the fail.

In 8.6 look for 5 carrots ^^^^^
and you will see what is the cause of the fail.
then go to support.veritas.com
and search for the exact line preceding the 5 carrots ^^^^^
typically you will find the answer since the technotes are geared towards the exact errors.
cheers !!!!!!!!!