cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted

client backup was not attempted because backup window closed (196)

22 août 2019 18:00:00 - Info nbjm (pid=5712) starting backup job (jobid=35733) for client MPX-VM-BIINT01
, policy MPX-CHYV16-01_P, schedule Cumulative-Inc
22 août 2019 18:00:00 - Info nbjm (pid=5712) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=35733, request id:{E80C09A8-FA0D-48E3-A729-1095346931C3})
22 août 2019 18:00:00 - requesting resource NETBACKUP_POOL-stu
22 août 2019 18:00:00 - requesting resource mpx-py-bkup02.snmvt.intra.NBU_CLIENT.MAXJOBS.MPX-VM-BIINT01
22 août 2019 18:00:00 - requesting resource mpx-py-bkup02.snmvt.intra.NBU_POLICY.MAXJOBS.MPX-CHYV16-01_P
22 août 2019 18:00:00 - awaiting resource NETBACKUP_POOL-stu. Maximum job count has been reached for the storage unit.
client backup was not attempted because backup window closed  (196)

 how to fix this issue i did  <install path>\Netbackup\bin\bpdown -v -f 
 <install path>\netbackup\bin\bpup -v -f 

<install path>\NetBackup\bin\admincmd\nbrbutil -dump

<install path>\NetBackup\bin\admincmd\nbrbutil -resetall 

it can be a solution ? please help me 

Tags (2)
2 Solutions

Accepted Solutions
Accepted Solution!

Re: client backup was not attempted because backup window closed (196)

The reason for queued job is clear:

awaiting resource NETBACKUP_POOL-stu. Maximum job count has been reached for the storage unit

You firstly need to check the Storage Unit Properties - 
If tape STU - how many concurrent drives? What is MPX (multiplexing) set to?

When you have this information, go check Activity Monitor to see what other jobs were running at 18:00 last night? 
How long did those jobs run? 

You then need to decide if you can change STU properties to allow more concurrent jobs to the same drive(s), or if extending the Start Window in the policy schedule will help. 

If you decide to allow concurent jobs (multiplexing), please read up on this topic. 
Sections in NBU Admin Guide I :
https://www.veritas.com/content/support/en_US/doc/18716246-126559472-0/v41156285-126559472
https://www.veritas.com/content/support/en_US/doc/18716246-126559472-0/v41780635-126559472
https://www.veritas.com/content/support/en_US/doc/18716246-129889741-0/v42735833-129889741

Forum posts :
https://vox.veritas.com/t5/NetBackup/Media-Multiplexing/td-p/647742 
(ignore the Symantec links - new Veritas links above)

https://vox.veritas.com/t5/NetBackup/Media-Multiplexing/m-p/683457

https://vox.veritas.com/t5/NetBackup/Multiplexing-and-Multistreaming/m-p/595443

 

View solution in original post

Highlighted
Accepted Solution!

Re: client backup was not attempted because backup window closed (196)

Please only do nbrbutil -resetall  IF you have determined from nbrbutil -dump output that there are orphaned device allocations and that available resources (as per Storage Unit properties) are not getting allocated.

View solution in original post

3 Replies
Accepted Solution!

Re: client backup was not attempted because backup window closed (196)

The reason for queued job is clear:

awaiting resource NETBACKUP_POOL-stu. Maximum job count has been reached for the storage unit

You firstly need to check the Storage Unit Properties - 
If tape STU - how many concurrent drives? What is MPX (multiplexing) set to?

When you have this information, go check Activity Monitor to see what other jobs were running at 18:00 last night? 
How long did those jobs run? 

You then need to decide if you can change STU properties to allow more concurrent jobs to the same drive(s), or if extending the Start Window in the policy schedule will help. 

If you decide to allow concurent jobs (multiplexing), please read up on this topic. 
Sections in NBU Admin Guide I :
https://www.veritas.com/content/support/en_US/doc/18716246-126559472-0/v41156285-126559472
https://www.veritas.com/content/support/en_US/doc/18716246-126559472-0/v41780635-126559472
https://www.veritas.com/content/support/en_US/doc/18716246-129889741-0/v42735833-129889741

Forum posts :
https://vox.veritas.com/t5/NetBackup/Media-Multiplexing/td-p/647742 
(ignore the Symantec links - new Veritas links above)

https://vox.veritas.com/t5/NetBackup/Media-Multiplexing/m-p/683457

https://vox.veritas.com/t5/NetBackup/Multiplexing-and-Multistreaming/m-p/595443

 

View solution in original post

Highlighted
Accepted Solution!

Re: client backup was not attempted because backup window closed (196)

Please only do nbrbutil -resetall  IF you have determined from nbrbutil -dump output that there are orphaned device allocations and that available resources (as per Storage Unit properties) are not getting allocated.

View solution in original post

Highlighted

Re: client backup was not attempted because backup window closed (196)