Forum Discussion

Lynne_Seamans's avatar
Lynne_Seamans
Level 6
12 years ago

5200 Storage Unit - best practice question Maximum Concurrent Jobs

I get a lot of queuing during backups due to 'maximum jobs on storage unit'..  the only storage unit i have is a 5200 appliance (currently @ 2.5.1). 

Checked, and its "Maximum concurrent jobs" is set to 20.  I don't remember setting that, so either it's the default, or the consultant who set the appliance up did it (or I did and just don't remember, but hey, it happens).

What do other folks have for their 5200's Storage Unit as "maximum concurrent jobs"?  Would i be safe to increase that by 5 or so?

Thanks for any info..

 

Backup and Recovery
NetBackup Appliance
Not Applicable
  • Rusty_Major's avatar
    Rusty_Major
    12 years ago

    Just throwing in what we do. We typically set our storage unit and max I/O streams limitation to between 100 and 150. This works great on Appliances or newer servers. Older traditional servers, such as the Sun/Oracle T2000 don't do this very well and so we have different storage units for them as they can only handle about 5-8 streams before crumpling under the hashing algorithm.

    However, you have MSDP, so you should be good. I would increase it 5 or 10 at a time and see what kind of results you get.

  • Mark_Solutions's avatar
    Mark_Solutions
    Level 6
    12 years ago

    A 5220 should be able to handle up to about 100 jobs - or at least 100 I/O streams

    To allow for duplication and replication you can safely increase the number of job on the Storage unit but may also want to limit the I/O streams on the disk pool to allow for duplication and replication

    This also depends on the type of backups you are doing - if all 100 were over a 1g network then it would be pointless, but if you have teamed 10g and also do VMWare backups over the fibre then you should be good to ramp it up more

    Hope this helps - I have seen it somewhere but can't find it now that the maximum reccomended limit was 125

  • Ed_Carter's avatar
    Ed_Carter
    Level 4
    12 years ago

    For me 100 streams would be a dream come true. I can manage about 40 streams at a reasonable throughput with no duplication or replication occuring. As soon as SLP's start processing I'm lucky to get 5000kb/ps on a single stream.

    For info I believe 20 is the default when creating the MSDP STU.

  • Lynne_Seamans's avatar
    Lynne_Seamans
    Level 6
    12 years ago

    Thanks, all.  Good info.  I am doing a lot of replication and de-duping, and I'm not on fibre, just a couple bonded 1gig connections.

    I might inch it up and see what happens!

  • D_Flood's avatar
    D_Flood
    Level 6
    12 years ago

    Just remember, there are two places to "inch it up"...There's the Max Jobs setting under NetBackup Management/Storage/Storage Units and the Max IO Streams setting under Media and Device Management/Devices/Disk Pools.

     

    If you do a lot of AIR you may want the Max IO setting to be higher than your Max Jobs since AIR seams to count more against threads more than it does against jobs.

  • Rusty_Major's avatar
    Rusty_Major
    Level 4
    12 years ago

    Just throwing in what we do. We typically set our storage unit and max I/O streams limitation to between 100 and 150. This works great on Appliances or newer servers. Older traditional servers, such as the Sun/Oracle T2000 don't do this very well and so we have different storage units for them as they can only handle about 5-8 streams before crumpling under the hashing algorithm.

    However, you have MSDP, so you should be good. I would increase it 5 or 10 at a time and see what kind of results you get.

  • Lynne_Seamans's avatar
    Lynne_Seamans
    Level 6
    12 years ago

    I did increase it 5, by "it" i mean "Maximum jobs on storage unit", from 20 to 25.  I have started getting warnings about my disks being too busy, but only occasionally, so i think i'll leave it there for now.

    \