Yes, I did open a support call.  I submitted this post after waiting a
day or two to get a solution from the vendor who provides our support. 
Yesterday after I sent this, I did get a call back and was told to
increase the CLIENT_READ_TIMEOUT on the master server to 3600 .  I
started running it again this morning and don't know if that will fix
it, the fix makes sense and in hindsight I should have tried that
first.  We'll see....

RCA


"David A. Chapa" wrote:
> 
> If Mark Erikson, Veritas is listening, he would be the man to answer your
> Storage Migrator questions.
> 
> Have you opened a support call for this one?
> 
> -----Original Message-----
> From: veritas-bu-admin AT Eng.Auburn DOT EDU
> [mailto:veritas-bu-admin AT Eng.Auburn DOT EDU]On Behalf Of RYAN C. ANDERSON
> Sent: Thursday, November 09, 2000 11:26 AM
> To: Veritas NBU
> Subject: [Veritas-bu] Maximum file count?
> 
> I'm using NBU 3.1.1 (will upgrade to 3.2 next week, then 3.4 next month)
> on Solaris.  I'm backing up a very small volume on a Solaris client,
> only 460 MB--the problem I believe is that its a Storage Migrator
> filesystem with many file 'stubs'.  The problem is that the backup hangs
> on one particular directory *every* time.  This particular directory has
> 14,560 files in it.  As of a couple weeks ago it would finish quickly.
> I've let it run over weekends with no success.  It never gives an error
> code, it always just runs, but I have to kill it because its in
> production and it sometimes takes as much as 25% cpu.
> 
> Questions:
> 
> Am I just not letting it run long enough?
> 
> What is the maximum file count limit?
> 
> Will 3.2 or 3.4 help me out?
> 
> Regards,
> 
> RCA
> --
> Ryan C. Anderson        |   United Defense L.P.
> Unix Administrator      |   763.572.6684 (desk)
> ryan_anderson AT udlp DOT com  |   612.235.9936 (pager)