Dustin,

Do you have any stuck jobs? I've seen this happen in the past where a 
client also has problems. Backups generate incomplete errors and the 
master/media server responsible for writing the data gets stuck like 
this. Other backups ran fine, and if the problem persisted over more 
than one day, only the client would fail completely. Most of the time I 
could kill -9 on the client and restart netbackup on the master/media 
servers.

The problem I experienced was with a solaris 8 client crashing and 
restarting each day, up until the zombie processes consumed enough 
resources that a new backup job would not start. Sometimes while the 
client was quietly going bad and the backups would finish successfully 
on attempt 2 or 3, I would see bpbrm consuming a lot of CPU time.

This happened more to me with version 5.x.

Does BPBRM_VERBOSE = 5 give anything meaningful?



> I’ve noticed in the past that bpbrm is utilizing 99.9% of the CPU and 
> hasn’t let down. Also it says it has used 15436:40 CPU Time which 
> seems like the process has gone rogue. Has anyone else had this happen 
> or is this normal, and how would I fix it?
>
> NetBackup 6.5
>
> Dustin D'Amour
>
> Wireless Switching
>
> Plateau Wireless

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