what is policy schedule Media Multiplexing is set ? Is it set right? Make sure this is set correctly

Are they in same pool and retention. Also what about max jobs per client setting in master server properties.

Thanks:

Max jobs per client = 4

Media Multiplexing is set = Yes

regards.

What is the number for media multiplexing ? 1 is the default which means you will able to run only 1 job but you have 4 drives which makes it 4 jobs.

Edit:I just checked the screenshot and you have Max concurrent drives set to 4 and multiplexing set to 4. Actually you should be able to run 4*4 =16 jobs if everything is set correctly. The other jobs that are getting queued are pointing to the same storage unit? Can you post the detailed status of the queued job

lsscsi shows 8 tapes coming from different path but NBU shows 4 of them and that is also repetitive. Please check if you have the configuration correctly setup or run the device configuration again if you have recently changed something.

I know that you have said yes, but please double-check MPX level in all schedules.
Insufficient media can also cause this.

Also check Job details for queued to job to see the reason for job being queued.

Sometimes orphaned device allocations can cause this.
You can troubleshoot this with 'nbrbutil -dump', examine MDS allocations and release media and/or drive allocations that you know are not currently in use.
nbrbutil -releaseMDS <mdsAlocationKey>
Quick fix is to reset all allocations when no backups are running:
nbrbutil -resetAll

I Would like to see what is showing in Queud jobs detail status. could you post it?

do you say any Drives in Restart status when you check them for Device moniter?

what is scan and tpautoconf -t shoiwng?

The job queue says 'no drives are available'.

Please see last part of my previous post:

Sometimes orphaned device allocations can cause this.
You can troubleshoot this with 'nbrbutil -dump', examine MDS allocations and release media and/or drive allocations that you know are not currently in use.
nbrbutil -releaseMDS <mdsAlocationKey>

Quick fix is to reset all allocations when no backups are running:
nbrbutil -resetAll

Marianne:

tpautoconf -t

[root@backup6m-bkp bin]# ./tpautoconf -t

Marienne:

did you check the resource allocation as suggested by Marianne?

did you check if the Drives are in RESTART state when you check from Device moniter ?

Nagalla:

They are in state "NO", so that this is right:

Regards.

Command is:

nbrbutil NOT nborautil and is located /usr/openv/netbackup/bin/admincmd

Best to first check resource allocation with 'nbrbutil -dump'.

Marienne:

You can see 4 device allocations - all Media:

No. If we look at the Allocation Ids, we can see that the Ids are a lot smaller than the current active one (13724). I cannot see any timestamp.

This means that 'something' happened some time ago - maybe YOU can tell us?