Since everyone else gave you the troubleshooting steps for the error 41, I
will just try to help you with your problem.

I have run in to this issue on both unix systems and Windows.  It is because
of the # of files.  Sometimes just running the find command is not possible.

I have always resorted to splitting the file system up.  You can create a
policy specific to the file system that fails.  Enable Allow multiple data
streams.  In the file selection list, do not put NEW_STREAM.  Just put the
file system name that fails with an "*" after the "/".

For instance, if the file system is /usr/some_dumb_admins_junk_pile, the
file selection would be /usr/some_dumb_admins_junk_pile/*.

Each directory under /usr/some_dumb_admins_junk_pile will be a separate job
(we are trouble shooting here).  You may find that most will run okay and a
few won't.  The few that won't need to be excluded from the ALL_LOCAL_DRIVES
policy and a special policy for the troublesome subdirectories created.

Works every time, but you have to work on it to determine where the actual
problem is.  (It could end up being an FS issue).




Bobby Williams
2205 Peterson Drive
Chattanooga, Tennessee  37421
423-296-8200

-----Original Message-----
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Jeff
Cleverley
Sent: Friday, January 04, 2008 12:54 PM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Getting a list of files from a failed backup

Greetings,

I have a file system that has started to fail full backups on a regular
basis.  The incremental backups run fine.  This file system is on a hpux
11.11 server,  There is only 228 gig of used data, but it does have ~5.5m
inodes in use.  The backup fails with a status 41.  This server has other
file systems on it with more used inodes and more used space, and they don't
have this problem.  I've run the backup at various times when I know the
network and file system load is low, but it doesn't change.

The current backup environment is 5.1 mp2.  It was supposed to be retired by
now which is why it hasn't been upgraded.

The reason I want to see what files it is backing up before it fails is that
all of the backups seem to backup just over 195 gig before they fail.  The
file counts vary quite a bit.  I'm expecting that I may have a very poorly
laid out structure with hundreds of thousands of files in one directory that
is causing this problem.  This may also be caused by some timeout if it does
hit this, but I haven't been able to find it in any of the log files.

I was able to recovery an image from the tape listing by running bpmedialist
-mcontents -m bk7159.  That returns image massey_1199305335.  I've tried
doing the following bpflist command and get the no entity found

bpflist -backupid massey_1199305335 -d 01/02/2008 -e 01/03/2008 -client
massey

I also tried running the bpflist this way and get no entity found again.
This format works when I give it a different client name and pattern, so I
know I have the syntax correct.

bpflist -client massey -st FULL -d 01/02/2008 00:00:00 -rl 1 -pattern
/mnt/wizard

I'm guessing some of this isn't working because the backup did not complete
and there isn't a valid image for it.

Any help you can provide that will show me where the backup is failing would
be greatly appreciated.

Thanks,

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

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