Are the jobs really running slower, I wonder, or has transmission stopped, thus 
having the Admin Console show a slower and slower rate as time passes?

Is it possible that the jobs are waiting for something?  I've seen jobs be 
apparently hung, but really they were waiting for a tape, when another job 
(usually a vault duplication) "stole" it.

Since going to 5.1MP1, I occasionally have a bunch of Oracle backups hang.  
When I have the client owner look at the client side, he says the client 
"thinks" the jobs completed long ago and there are no current connections to 
the backup server. The images involved do not make it into the catalog :-(   

NetBackup could certainly use better facilities for reporting the state of the 
backup server and its jobs.

cheers, wayne

Williams, Kristopher L wrote, in part:
> I am having a problem with jobs slowing down through the backup window
> and eventually coming to a point of being hung. The jobs start running
> at decent speeds, then trickle down to about 17 - 25 kb/sec. It's
> different clients each night, and out of 500 jobs, there might be 7-8
> hung when I check the morning after. I am unable to kill the jobs via
> activity monitor, the only way I can get them to die is to stop the
> services on all media managers and restart them. After this is done the
> hung jobs go away and end with status code 23. Has anyone seen anything
> like this?
> 
> I'm running NetBackup v5.0 MP3 on a Windows 2000 Master server. All
> media servers are Windows 2000 also. The library is a STK L700 with FC
> LTO Gen1 drives. All drives and robot are at the current level of
> firmware. Clients are all Windows based (NT 4, Win2k, Win2k3). All of
> the hung jobs are network backups. Because it is different clients each
> night, I do not think it is 100% a network problem.