KrisJTurn1

updated

14 years ago

K

KrisJTurn1

19 Posts

0

3004

November 30th, 2012 12:00

Avamar Client Transfer Speeds?

I am fairly new to Avamar.  So not sure if the client can do this or not.

We are in the midst of testing an Avamar solution for all our remote sites.  These sites vary from different connection rates.  We have our test lab set to mirror some of our lower bandwidth sites.  I need to find out a way if possilbe to control the throughput of the data from the Avamar client to the Avamar servers.  Also, is there a way in the logs to find out what the transfer rate is currently?

Thanks,

Kris

  • ionthegeek

    2 Intern

    •

    2049 Posts

    1319

    0

    Posted November 30th, 2012 13:00

    The Avamar client supports bandwidth throttling.

    For file system backups, you can go to the Options tab, select the appropriate file system plug-in from the drop-down list (Windows File System, Linux File System, etc.), check the "Show Advanced Options" checkbox and scroll down until you find "Network rate throttle (Mbps)". Fill this in with your desired bandwidth in Mbps (decimals are fine, e.g. 1.2).

    For plug-in backups (Exchange, Oracle, etc.), it's a little trickier. You have to select the plug-in from the drop-down, click the "More" button and fill in the attribute and value by hand.

    For the attribute, enter [avtar]net-throttle. For the attribute value, enter your desired bandwidth. When you're happy with the setting, click the + sign under the fields and you should see the flag added to the select box below. Click OK to save your changes. The [avtar] in the flag tells the plug-in to pass the flag through to avtar which is the process that actually communicates with the server.

    Please note that the bandwidth throttle tries to throttle the average network usage to the requested value rather than being a hard cap so there may be minor differences between your testing and the real environment but nothing drastic.

    You can also add a custom attribute to increase the frequency of status messages reported in the logs. Enter status for the attribute and a value in seconds for how often the status should be logged. The default is 300. Be cautious about setting this value too high -- it can make the logs extremely large. If you need more advanced information, you can also enable comstats but the output is somewhat arcane and it will make the logs extremely large.

  • dookie3

    8 Posts

    1319

    0

    Posted December 3rd, 2012 04:00

    Is it right to say that this throttling is per client inside the backup set and not per group/data-set ? so that each client will be limited ? or is it limited per group backup ?

  • ionthegeek

    2 Intern

    •

    2049 Posts

    1319

    0

    Posted December 3rd, 2012 07:00

    Correct. The throttle applies to each individual avtar session, it is not per group or per dataset.

  • ionthegeek

    2 Intern

    •

    2049 Posts

    1319

    0

    Posted December 3rd, 2012 08:00

    The calculation seems reasonable but if you need to throttle the total amount of Avamar traffic on a link, it would likely be better to throttle at the network level for efficiency and manageability reasons. If you used this strategy, the throttle value would have to change whenever a client was added or removed.

    Throttling is generally used to keep a busy client from saturating its own link rather than controlling the overall bandwidth usage of a group of clients.

  • dookie3

    8 Posts

    1319

    0

    Posted December 3rd, 2012 08:00

    Thanks, would a fair example assumption be;

    1 Mega-byte link leaving say 50 % for standard services would be 0.5 MB

    Thus than if you had 30 DTLT clients at the site you would than specify in the data set a throttle limit of 0.02 or 34.14 KiloBytes as an average.

    Would that be a correct assumption ? Obviously this would never be an effective,efficient use of the bandwidth allocated to the backup application as different clients would be using different amounts of bandwidth dependant on there load and bytes to be sent so it's not dynamic.

    I suppose QOS would be a better method until the software catches up.