First in the gui add the column to your view "state details"
That will tell you why a job is not running.

Could be you have on your storage unit, max drives, or max jobs and if those 
have been met then the job will queue.

-----Original Message-----
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu 
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Sushil
Sent: Wednesday, May 12, 2010 10:37 AM
To: VERITAS-BU AT MAILMAN.ENG.AUBURN DOT EDU
Subject: [Veritas-bu] Issues with Oracle backup Netbackup 5.1


Another thing which i noticed in logs there were many jobs which were in queued 
state but only 4 drives out 0f 8 were utilised. I can not find the reason why 
the jobs were queued if the tape drives were available. Strange enough those 
queued jobs became active after 2 hours.

I have no idea what those jobs were waiting for in those 2 hours, is there any 
way to find that out? And also what could be the reason for this?

Thanks,
Sushil

+----------------------------------------------------------------------
|This was sent by sushil.gambhir AT gmail 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


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