The point being you can't really investigate every file that causes a
status 1 every day.  In the prior job I mentioned just one backup took
me hours to certify that none of the files involved were an issue.

Unless they're going to let you kill all other processes on a system and
lock out all users and connections during a backup they'll have to live
with status 1.

-----Original Message-----
From: veritas-bu-bounces at mailman.eng.auburn.edu
[mailto:veritas-bu-bounces at mailman.eng.auburn.edu] On Behalf Of Wayne T
Smith
Sent: Friday, June 30, 2006 8:55 AM
To: veritas-bu at mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] status 1 (was: Typical success rates?)

You have points 1 and 2 reversed. 

If you exclude files without determining their relevance to your 
business, your job and your business are at unnecessary risk. :-(

Status code 1 is better than nothing, not success. ;-)

cheers, wayne

WEAVER, Simon wrote, in part,  on 6/30/2006 4:16 AM:
> 1) exclude the file/files that are causing the status code
> 2) Investigate and if not relevant, revert to point 1.
>   
_______________________________________________
Veritas-bu maillist  -  Veritas-bu at mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu