Nope, it was not there in 5.1 So you have 8 drives - and your storage unit is set to use 8 drives... correct? And multiplexing for the storage unit is set to 4 - so you should be able to have 32 jobs running at once - 4 to each of the 8 drives. 4 x 8 = 32
So let's look at something else. Are you running more than one job per client? (multistreamed backups) If so lets look at how many jobs per client are allowed. Master server properties, Global Attributes Maximum jobs per client -if this is one or 2 look at what jobs are running and which ones are queue. Has that Client reached it's max number of concurrently running jobs? The Maximum jobs per client property specifies the maximum number of backup and archive jobs that NetBackup clients can perform concurrently. Default: 1 job. This can also be set per client - so if the Global is like 8 but you still have queue, again in the master properties look at Client Attributes See if a client is listed here, if yes then look at the General tab and see if the client has be set to limit the number of data streams The Maximum data streams property specifies the maximum number of jobs that are allowed at one time for each selected client. (This value applies to the number of jobs on the client, even if multistreaming is not used.) -----Original Message----- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Sushil Sent: Thursday, May 13, 2010 3:30 AM To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: [Veritas-bu] Issues with Oracle backup Netbackup 5.1 > 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.gamb...@gmail.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +---------------------------------------------------------------------- _______________________________________________ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
