I don't know if your jobs ever went active or not. Typically if bpsched is not 
scheduling jobs - something (obviously) caused it to stop responding.

Things that may be the cause:
1.    CLIENT_CONNECT_TIMEOUT's being set to more then the default of 300 
seconds (check the bp.conf file).
    *  If that is the root cause - grep the bpsched log for "timeout " (note 
the space on the end - if you do not include a space in the search you will get 
tons of queue timeout messages).
  
2.   Insufficient message queue space.   
    * Check the bpsched log for messages about "suspending process", "queue 
full" and "defer/undefer" messages.  Those are indications that message queue 
space is not adequate and should be increased. (this applies to Unix of course)


3.  A corrupt bpsched.d worklist file. (in netbackup/bin/bpsched.d).
   *  If you have checked for items 1 and 2 - then it's best to stop nbu, and 
cleanup the worklist files in that directory and then restart (this includes 
the drive worklist files).


Oh - and you can increase logging on the fly for bpsched for version 5.1 (not 
sure which patch version this started at) - but run:
netbackup/bin/admincmd/bpschedreq -verbose #  
   # is the verbosity level.

Hope that helps.

+----------------------------------------------------------------------
|This was sent by comp_geek_gal AT yahoo DOT com via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------


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