cancel
Showing results for 
Search instead for 
Did you mean: 

INF - Waiting in NetBackup scheduler work queue

vonage_83
Not applicable

archive backup streams for one DB instance was in hung state for so long while alerts are coming :

INF - Waiting in NetBackup scheduler work queue

please suggest solution for this.

 

Thanks

5 REPLIES 5

Marianne
Level 6
Partner    VIP    Accredited Certified

As a start - NBU version and patch level on master, media and client.

Various changes and improvements have been made to the scheduler / job manager / resource broker over time.

Where do you see this message - on the master or the client?

Settings on master? Mpx level for STU? Mpx level for schedule? Max jobs per client?

Database being backed up? Script configured to generate multiple concurrent streams?

Omar_Villa
Level 6
Employee

Run nbpemreq -job screen all, this will show you what is in your scheduler queue if something ever got in.

Other question is who starts the backup? the master or the client? 

 

Regards.

Marianne
Level 6
Partner    VIP    Accredited Certified

Another new forum member who posted once and never came back.......... crying crying

ktandel
Level 4
Partner Accredited Certified

usr/openv/netbackup/bin/admincmd/bpconfig -U shows:
 

Max Simultaneous Jobs/Client: 1
Max drives this master: 1
 
Using the same command, change the Max drives this master to zero:
/usr/openv/netbackup/bin/admincmd/bpconfig -mdtm 0
This is the maximum drives for this master, the maximum number of drives for this master and remote media server cluster that the master server should consider available when scheduling backups. Drives is a non-negative integer. The default is 0 (unlimited).
 
Also change the Max Simultaneous Jobs/Client to a value larger than 1:
/usr/openv/netbackup/bin/admincmd/bpconfig -mj 32
This specifies the maximum jobs per client. This is the maximum number of jobs that a client may perform concurrently. The number must be a positive integer. The default value is 1.

jaketame
Level 3
Partner

I found that this is relating to the Frequency Based schedules.

Ie.

Full Backup - Frequency - 1 week - Backup ran 0100

The scheduler then has to wait 1 full week before it can run the backup again even if the start window is 2200.

I have been changing the Frequency's to 6 days to overcome this.