This post is more than 5 years old
17 Posts
0
3935
March 23rd, 2012 13:00
Bandwidth throttle VMWare windows Image transfer
I have the 6.0 VMWare guide but it says to change throttle via dataset, edit, options, show advanced. But there is not network usage throttle there. I've only seen that under "windows file system". It is on page 108 of the emc avamar 6.0 for vmware guide.
I cannot edit it on the client side as it is just a proxy, not the client. (image backup). Is there a attribute and value? like throttle or --throttle=xmbps ?
Thanks!
No Events found!
ionthegeek
2 Intern
•
2K Posts
0
March 26th, 2012 08:00
In the dataset, try this:
Attribute: [avtar]throttle
Value:
Where n is your desired network bandwidth limit in megabits.
Bebo2k
544 Posts
0
March 23rd, 2012 19:00
Hi northvibe,
Please check the following Powerlink article on How to throttle CPU and network usage of an Avamar client during backups:
https://solutions.emc.com/emcsolutionview.asp?id=esg95533
Hope this helps you.
Thanks,
Ahmed Bahaa
ionthegeek
2 Intern
•
2K Posts
0
March 26th, 2012 08:00
I should also warn you that VMware Image backups in v5 do not make use of client-side caches so they tend to send a large number of "is_present" requests across the network to the Avamar Server. Limiting the network bandwidth may have an impact on the speed of your backups.
northvibe
17 Posts
0
March 26th, 2012 08:00
But this is a VMWare plugin. So there is no Avamar client installed on the client. I cannot edit a avtar.cmd file as it does not exsist.
The only way I can see this being possible is in the Data set, under options, then More. Being able to enter an atttribute and value. Is that possible?
northvibe
17 Posts
0
March 28th, 2012 07:00
Thank you, I'll test this and monitor the network bandwidth.
ionthegeek
2 Intern
•
2K Posts
0
March 28th, 2012 07:00
The dataset option should work in all current release versions. The warning about is_present requests also applies to all current release versions of the Avamar software.
The client caches will be enabled on VM proxy clients in a future release but this is primarily to avoid sending a storm of identical is_present requests to the server during the same backup. VM image backups are prone to this behaviour because long strings of 0s (such as are found in VMDK flat files) are broken up into chunks that have the same hash so we end up with thousands of identical requests. If these requests can be handled by the cache, we avoid hitting the network or the server with them.
In particular, please note that this change will not have a substantial effect on typical VM image backup performance (unlike file system clients where the caches account for most of the performance gain).
northvibe
17 Posts
0
March 28th, 2012 07:00
Is this only V5? We are running V6.