Wayne, 

      We have also experienced the same pains since upgrading to 5.0
MP2 about two weeks ago.  I have had two cases open with Veritas One is
still open.  The first issue I had was a hung ltid process on one of my
SAN media servers slowing everything down to where it would take approx.
30 minutes for jobs to show as queued and another 1 to 2 hours before
they would become active.  This was solved by deleting the storage unit
of the server that was hung(until it could be rebooted).

The second case is still open on jobs that are staying queued even
though multiplexing limits on the tape drives have not been met.  Jobs
will stay queued until an empty drive becomes available.  I have a Webex
session scheduled Thursday morning so the engineer can see this problem
first hand.

On The other :File added" message check to make sure that you haven't
run out of disk space.  We also had a run away Bpsched process where the
log file grew to over 70GB in an 8 hour period filling the disk.  Once
this happened I was getting the same errors.

Michael Kelczewski
Senior Application Analyst - Computer Operations
City of Jacksonville
Information Technologies Division
220 E. Bay St., Suite 200
City HAll Annex
Jacksonville, FL  32202
904-630-1079,   Fax 904-630-2764
kelcz AT coj DOT net

Version 5.0MP2 (I don't have 5.1 installed) (Solaris 9, LTO1, L700)  
fixed a lot of v4.5 problems and adds lots of new goodies (although 
first looks and trials at disk staging and synthetic backups are
totally 
underwhelming).

Unfortunately, for me it broke a lot more than it fixed and we're very

unhappy with it.   Mysteriously queued jobs, tapes attached with no
jobs 
active, status codes 213 and 196, and jobs going incomplete or failing

after "end writing" in log are a few of the things we experience.  It 
has been a very labor intensive time.

Today I had a new one: at the end of a nearly 24-hour 158 gig backup of

several file systems, a number of "bpbrm (pid=xxxxx) could not write 
FILE ADDED message to std err" messages appeared in the log and the job

went to "Incomplete" status instead of finishing.  On resuming the job,

it began from the beginning. ;-(    (The client is still at v4.5).

Maybe v5.0MP3 will be better or we'll find magic potion to correct 
something somewhere?!    Hope this helps, wayne