cancel
Showing results for 
Search instead for 
Did you mean: 

Info nbjm (pid=21275) Waiting in NetBackup scheduler work queue on server

SurajKamble
Level 2

I am getting below messages (Info nbjm (pid=21275) Waiting in NetBackup scheduler work queue on server) in details status, please let me know if anybody resolved this issue.

I am using AdvancedDisk (13TB) & i have enough resources on master server (Media & master servers are same).



07/11/2018 10:45:32 - Info nbjm (pid=21275) starting backup job (jobid=304931) for client sn1ylpx1a0008, policy BSSDG_ORACLE_DB_Daily, schedule Daily_Incremental
07/11/2018 10:45:32 - Info nbjm (pid=21275) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=304931, request id:{7AF9E2D0-84B4-11E8-BECF-3A8FA6556AEB})
07/11/2018 10:45:32 - requesting resource LTE_Staging_Disk-stu
07/11/2018 10:45:32 - requesting resource sn1ylpx1g0001.NBU_CLIENT.MAXJOBS.sn1ylpx1a0008
07/11/2018 10:45:32 - awaiting resource LTE_Staging_Disk-stu. Waiting for resources.
Reason: Storage unit concurrent jobs throttled, Media server: sn1ylpx1g0001,
Robot Type(Number): NONE(N/A), Media ID: N/A, Drive Name: N/A,
Volume Pool: NetBackup, Storage Unit: LTE_Staging_Disk-stu, Drive Scan Host: N/A,
Disk Pool: LTE_Staging_Disk, Disk Volume: /backup_vol01
07/11/2018 10:47:32 - Info nbjm (pid=21275) Waiting in NetBackup scheduler work queue on server sn1ylpx1g0001
07/11/2018 10:49:32 - Info nbjm (pid=21275) Waiting in NetBackup scheduler work queue on server sn1ylpx1g0001
07/11/2018 10:51:32 - Info nbjm (pid=21275) Waiting in NetBackup scheduler work queue on server sn1ylpx1g0001
07/11/2018 10:53:32 - Info nbjm (pid=21275) Waiting in NetBackup scheduler work queue on server sn1ylpx1g0001
07/11/2018 10:55:32 - Info nbjm (pid=21275) Waiting in NetBackup scheduler work queue on server sn1ylpx1g0001
07/11/2018 10:57:32 - Info nbjm (pid=21275) Waiting in NetBackup scheduler work queue on server sn1ylpx1g0001
07/11/2018 10:59:32 - Info nbjm (pid=21275) Waiting in NetBackup scheduler work queue on server sn1ylpx1g0001
07/11/2018 11:01:32 - Info nbjm (pid=21275) Waiting in NetBackup scheduler work queue on server sn1ylpx1g0001
07/11/2018 11:03:32 - Info nbjm (pid=21275) Waiting in NetBackup scheduler work queue on server sn1ylpx1g0001
07/11/2018 11:05:32 - Info nbjm (pid=21275) Waiting in NetBackup scheduler work queue on server sn1ylpx1g0001
07/11/2018 11:07:32 - Info nbjm (pid=21275) Waiting in NetBackup scheduler work queue on server sn1ylpx1g0001
07/11/2018 11:07:40 - granted resource sn1ylpx1g0001.NBU_CLIENT.MAXJOBS.sn1ylpx1a0008
07/11/2018 11:07:40 - granted resource MediaID=@aaaa7;DiskVolume=/backup_vol01;DiskPool=LTE_Staging_Disk;Path=/backup_vol01;StorageServer=sn1ylpx1g0001;MediaServer=sn1ylpx1g0001
07/11/2018 11:07:40 - granted resource LTE_Staging_Disk-stu
07/11/2018 11:07:40 - granted resource TRANSPORT
07/11/2018 11:07:41 - estimated 0 kbytes needed
07/11/2018 11:07:41 - Info nbjm (pid=21275) started backup (backupid=sn1ylpx1a0008_1531278461) job for client sn1ylpx1a0008, policy BSSDG_ORACLE_DB_Daily, schedule Daily_Incremental on storage unit LTE_Staging_Disk-stu
07/11/2018 11:07:41 - started process bpbrm (pid=91376)
07/11/2018 11:07:42 - Info bpbrm (pid=91376) sn1ylpx1a0008 is the host to backup data from
07/11/2018 11:07:42 - Info bpbrm (pid=91376) reading file list for client
07/11/2018 11:07:42 - connecting
07/11/2018 11:07:42 - Info bpbrm (pid=91376) listening for client connection
07/11/2018 11:07:42 - Info bpbrm (pid=91376) INF - Client read timeout = 300
07/11/2018 11:07:42 - Info bpbrm (pid=91376) accepted connection from client
07/11/2018 11:07:42 - Info dbclient (pid=11918) Backup started
07/11/2018 11:07:42 - Info bpbrm (pid=91376) bptm pid: 91380
07/11/2018 11:07:42 - connected; connect time: 0:00:00
07/11/2018 11:07:43 - Info bptm (pid=91380) start
07/11/2018 11:07:53 - Info bptm (pid=91380) using 262144 data buffer size
07/11/2018 11:07:53 - Info bptm (pid=91380) setting receive network buffer to 262144 bytes
07/11/2018 11:07:53 - Info bptm (pid=91380) using 16 data buffers
07/11/2018 11:07:53 - Info bptm (pid=91380) USING 262144 data buffer size for FT
07/11/2018 11:07:53 - Info bptm (pid=91380) start backup
07/11/2018 11:07:53 - Opening Fibre Transport connection, Backup Id: sn1ylpx1a0008_1531278461
07/11/2018 11:07:53 - begin writing
07/11/2018 11:08:20 - Info dbclient (pid=11918) dbclient(pid=11918) wrote first buffer(size=262144)
07/11/2018 11:22:22 - Info dbclient (pid=11918) dbclient waited 0 times for empty buffer, delayed 0 times
07/11/2018 11:22:22 - Info dbclient (pid=11918) done. status: 0
07/11/2018 11:22:22 - Info bptm (pid=91380) waited for full buffer 1321 times, delayed 808006 times
07/11/2018 11:22:24 - Info bptm (pid=91380) EXITING with status 0 <----------
07/11/2018 11:22:24 - Info bpbrm (pid=91376) validating image for client sn1ylpx1a0008
07/11/2018 11:22:24 - Info dbclient (pid=11918) done. status: 0: the requested operation was successfully completed
07/11/2018 11:22:24 - end writing; write time: 0:14:31
the requested operation was successfully completed (0)

5 REPLIES 5

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

We see this in Job Details:

 awaiting resource LTE_Staging_Disk-stu. Waiting for resources.
Reason: Storage unit concurrent jobs throttled, Media server: sn1ylpx1g0001,

Have you checked the Storage Unit config?
What is 'max concurrent jobs' set to?
How many other jobs were running to same STU at this point in time?

Another possibility is that capacity-managed throttling kicked in when disk was approaching HWM. 
See this TN:
https://www.veritas.com/support/en_US/article.000012398

Tape_Archived
Moderator
Moderator
   VIP   

Please share more details about Master server OS and it's configuration. Mostly NetBackup will give the reason for max settings on Storage Unit, Disk Pool, etc. This could be Master server waiting for OS resource to process NetBackup request; i have seen this issue in my environment & it was related Master server, a VM.

Hi,

Linux sn1ylpx1g0001 2.6.32-431.el6.x86_64 #1 SMP Sun Nov 10 22:19:54 EST 2013 x86_64 x86_64 x86_64 GNU/Linux

Linux 6.5

MemTotal: 64

CPU: 24

Maximum concurrent jobs: 30 (Advanced Disk)

 

Hi Marianne,

Executed commnad as mentioned in link you provided & it set to 30 .

But still i am facing the problem.

Maximum concurrent jobs: 30 (Advanced Disk)

Hi Marianne,

It's resolved after execute "nbemmcmd" command as mentioned in document. 

Value set to 30 automatically after execute the command.

Thanks :)