Forum Discussion

MOHAMED_PATEL's avatar
MOHAMED_PATEL
Level 5
15 years ago
Solved

Netbackup 7.x Bandwidth Trottling

Netbackup bandwidth trottling is limited to 10000KB, i.e 10MB/s - this is by design.

Can this limit not be increased to compensate for newer technology, or does changing changing the registry/bp.conf setting do the trick-

My scenario is backing up exchange 2010 DAG (passive node), where the client sends data so fast maxing it's interface and causing backup to fail with socket write errors. Hence, I have used bandwidth trottling to limit...

Limiting the bandwidth to 50/70Mb/s for now should work - LTO3 drives used.

There is nothing in the admin guides detailing the max usage but just an example.

 

7.1.x and Earlier
Backing Up
Backup and Recovery
Basics
Best Practice
Configuring
Documentation
Features
NetBackup
Performance
  • Nicolai's avatar
    Nicolai
    15 years ago

    This is a fairly old tech note, but I think it' still valid:

    http://www.symantec.com/docs/TECH30467

    The last value is the amount of KB/sec you want the bandwidth throttled to. I do not see a 10MB/sec as restriction so changing the registry on the client should do the job.

17 Replies

  • Nicolai's avatar
    Nicolai
    Moderator
    15 years ago

    This is a fairly old tech note, but I think it' still valid:

    http://www.symantec.com/docs/TECH30467

    The last value is the amount of KB/sec you want the bandwidth throttled to. I do not see a 10MB/sec as restriction so changing the registry on the client should do the job.

  • RiaanBadenhorst's avatar
    RiaanBadenhorst
    Level 6
    15 years ago

    Well who would have thought going fast would ever be bad :P

     

    Please try setting it to higher value in the registry and let us know if it works.

  • Nicolai's avatar
    Nicolai
    Moderator
    15 years ago

    Have you checked if flow control is enabled on nic and switche?. Normal tcp flow control ensure data isn't send faster than the peer can receive them.

    http://www.tcpipguide.com/free/t_TCPWindowSizeAdjustmentandFlowControl.htm

  • UFO's avatar
    UFO
    Level 6
    15 years ago

    Agree. It is always botlleneck on the slowest part of the NBU chain but anyway - there is will be no overload when the channel is thin. Data will just go slower.

  • UFO's avatar
    UFO
    Level 6
    15 years ago

    Mohamed, could you please clarify why you want "this limit not be increased"?

  • RiaanBadenhorst's avatar
    RiaanBadenhorst
    Level 6
    15 years ago

    Volo,

     

    He asked why it cannot, or has not been increased, since the earlier release of the product when 10 or 100mbps was the standard in the indutry.

     

    He requires a higher value for the limit

     

    R

  • MOHAMED_PATEL's avatar
    MOHAMED_PATEL
    Level 5
    15 years ago

     Nicolai - nice link to TCP fundamental (simple) -

    The client does not have a bandwidth setting - this change is only affected on the Master server.

    Will check Flow Control setting - Currently Defaults are used.

    Riaan - in the test lab (standalone and not clustered master) the setting (registry) can be changed to a higher value, which reflects correctly on the master - however when attempting to change the IP address range, it requires not more than 10000KB.

    Services were happily restarted....no errors noted..yet

    I will be testing the backup shortly and post progress.

  • MOHAMED_PATEL's avatar
    MOHAMED_PATEL
    Level 5
    15 years ago

    Just on Limits -

    Netbackup Version 6.5.6 allows a max of 32767KB - 32MB/s.

    Netbackup 7.x has limit to 10000KB - 10MB/s

  • MOHAMED_PATEL's avatar
    MOHAMED_PATEL
    Level 5
    15 years ago

    Have now changed the registry setting to 50000KB on a production system - clustered master - no problems with this so far...phew

    limit registers as 50000KB in gui.

    Now for the backup test.....