> 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.
> 



sorry but i could not find "state details" as column in activity monitor , 
maybe its not there in 5.1. Also there is no value set on Max. Conc. Jobs in 
storage unit.


> Is your storage unit definitely configured to use all the drives?
> And this may seem like a strange thing to ask but what is your
> client_connect_timeout set to on your master server? 


Yes it is configured to use all the drives. The client_connect_timeout value is 
4000 seconds.

Another thing which i noticed is that ?Maximum multiplexing per drive? is set 
as 4 on storage unit. But multiplexing is set as 16 on policies. Could this be 
the reason for queued jobs? But at times i have noticed that 1 out of 8 drives 
is utilised and still there are approx 5-6 jobs in queued state and when i see 
job details there is nothing.

+----------------------------------------------------------------------
|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