Forum Discussion

Peter_Hunt's avatar
Peter_Hunt
Level 3
9 years ago

196 because limit has been reached for requested resource

Master win 2008 r2 7.6.0.4
client  win 2003 6.0.mp6

This clients backup is failing with 196 because limit has been reached for requested resource.

This is disk backup on DD and SLP is also being used.

Below is the detailed status. 

11/7/2015 1:22:32 PM - Info nbjm(pid=6116) starting backup job (jobid=193400) for client hqsa0400, policy HQ65-PRD-MISC-FRI18-ALD, schedule Monthly-Full  
11/7/2015 1:22:32 PM - Info nbjm(pid=6116) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=193400, request id:{6B170F9F-F16E-4904-B925-63675D8CF412})  
11/7/2015 1:22:32 PM - requesting resource usilsb552x-dd-su
11/7/2015 1:22:32 PM - requesting resource usilsb5520.NBU_CLIENT.MAXJOBS.hqsa0400
11/7/2015 1:22:32 PM - requesting resource usilsb5520.NBU_POLICY.MAXJOBS.HQ65-PRD-MISC-FRI18-ALD
11/7/2015 1:22:32 PM - Info nbrb(pid=3984) Limit has been reached for the logical resource usilsb5520.NBU_CLIENT.MAXJOBS.hqsa0400    

 

What can be the cause for this??

  • This looks like the reason : "Limit has been reached for the logical resource usilsb5520.NBU_CLIENT.MAXJOBS.hqsa0400 " What is set for Max Jobs per Client in Host Properties - > Master - > Global Properties? Or was value limited for this client in Host Properties - > Master - > Client Attributes -> Client-name? A value of 4 jobs per client is normally a good start.
  • Limit has been reached for the logical resource usilsb5520.NBU_CLIENT.MAXJOBS.hqsa0400

     

    What is the Maximum jobs per client set to if you check the Host Properties > Master Server > Your Master Server Name > Global Attributes?

  • Thanks for your responses Marianane and Riaan

    Host Properties > Master Server > Your Master Server Name > Global Attributes? max job per client is set to 5

     

     

  • Did you check to see if you had 5 jobs already running for that specific client?

     

  • As revaroo stated, there must be some jobs running for this client. For example, is not policy HQ65-PRD-MISC-FRI18-ALD configured with Attributes\Allow Multiple Data Streams, thus generating individual jobs for Backup Selection rows? If yes, then you can adjust Max Jobs settings according to posts above. Or decrease number of streams according to Admin Guide with a NEW_STREAM directive.

    Riaan, just "streaming" jobs with non-zero "kilobytes written" are counted, not snapshot jobs.

    Michal

  • Thanks to all for your comments.. My apologies I messed up with two differednt clients and I ended up pasting wrong detailed logs. here are teh logs.

    Master server: Linux NB 7.1.01This is exchange server backups and 3 streams are failing with below out of 19 SGs

    Host Properties - > Master - > Global Properties? max jobs per client is 10

     

    media multiplexing in full backup schedule is 8

    storage unit is DD disk and 26 is max concurrent jobs settings.


    11/09/2015 21:01:25 - Info nbjm (pid=25408) starting backup job (jobid=4227202) for client usnbsx5702, policy Win-Exchange-Store-5702, schedule Full
    11/09/2015 21:01:25 - Info nbjm (pid=25408) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=4227202, request id:{546FC826-8757-11E5-91D6-B063ED2121C0})
    11/09/2015 21:01:25 - requesting resource usnbub5500-omaha-dd-1-lsu-dp-su
    11/09/2015 21:01:25 - requesting resource usnbub5500.NBU_CLIENT.MAXJOBS.usnbsx5702
    11/09/2015 21:01:25 - requesting resource usnbub5500.NBU_POLICY.MAXJOBS.Win-Exchange-Store-5702
    11/09/2015 21:01:27 - awaiting resource usnbub5500-omaha-dd-1-lsu-dp-su. Maximum job count has been reached for the storage unit.
    11/10/2015 06:52:52 - Info nbrb (pid=25369) Limit has been reached for the logical resource usnbub5500.NBU_CLIENT.MAXJOBS.usnbsx5702
    client backup was not attempted because backup window closed  (196)

  • Do you have more than 26 jobs running to this storage unit as we can see:

    Maximum job count has been reached for the storage unit.

  • Can you increase max jobs for the STU? Or start the backup earlier? The job started at 9pm and stayed queued until the backup window closed just before 7 am. "11/09/2015 21:01:27 - awaiting resource usnbub5500-omaha-dd-1-lsu-dp-su.  Maximum job count has been reached for the storage unit. 11/10/2015 06:52:52 - Info nbrb (pid=25369) Limit has been reached for the  logical resource usnbub5500.NBU_CLIENT.MAXJOBS.usnbsx5702 client backup was not attempted because backup window closed  (196)" What is the size and throughput of the jobs that kept the STU busy all night? Are the media server(s) and DD all on 10Gb network? Is the backup window enough for a single Exch server to backup this many SGs? Are these full or Incr backups? Can you change the Exch backups to run fulls over a weekend with bigger backup window and Incr during the week?