That's not exactly true; we didn't see issues with an inordinate
number of bpdbm processes on MP5 until the images which were corrupt
had expired and were ready to be pruned from the catalog were unable
to be processed.  In our case, it was between three and six months
after those images were initially written.

In our case, we had another process fail (hot catalog backups) which
led us to the corrupt images and the large number of bpdbm problems.
Now, I'm not trying to say that is his issue, however, it did happen
to us on a select few images that were written with MP5.

-- nick


>  So this suggests that 6.0MP5 is not the cause.  Something else changed, and
>  Symantec can't tell what that was.  You might know, but probably not.  Many
>  times it's what is happening on the clients that hurt you and of course the
>  user community never admits to anything.
>
>  A lot of processes by itself isn't a problem.  It's what they're doing
>  that's the problem...  Many of those could be idle.
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu