Greetings,

I received a number of replies through the group and 1 directly to me.  
I thought I would do a summary of the problem and solution rather than 5 
different posts to the group.  My thanks to the following people for 
their responses:

Harry Tirrell
Carl Stehman
Mitch Lien
Tim Hoke
Bobby Williams

The problem was trying to get the list of files from the failed backup.  
I got the same information from Harry and Mitch with was to try changing 
the timeout value on the client (CLIENT_READ_TIMEOUT) in the bp.conf, 
and do the following:

- Add "VERBOSE = 5" to the /usr/openv/netbackup/bp.conf file.
- Create the "bpbkar" directory within /usr/openv/netbackup/logs (on the 
client).
- Create a touch file called "bpbkar_path_tr" within the 
/usr/openv/netbackup directory (on the client).
- Run job twice.

I did both at the same time.  The job completed on the first pass, so 
the timeout value worked.  I also happened to be watching the backup 
when it got to the area it usually failed.  It showed me a truly munged 
file that is most likely the cause of the problem.  The file listing 
said the file was 544 gig in size which is a good trick in a 280 gig 
file system :-)  The user has since deleted the file.  I'll expect next 
months backups to run cleanly.

Thanks again for all the help.

Jeff

-- 

Jeff Cleverley
Unix Systems Administrator
4380 Ziegler Road
Fort Collins, Colorado 80525
970-288-4611
jeff.cleverley AT avagotech DOT com

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu