Video Screencast Help
Search Video Help Close Back
to help

Consistent & Easier Bandwidth Throttling for Replication

Created: 03 Oct 2011 | Updated: 03 Oct 2011 | 7 comments
Todd D. Woodward's picture
0 Agree
0 Disagree
0 0 Votes
Login to vote

Currently with PureDisk and Media Server Dedupe, you have to hand-edit pd.conf and agent.cfg as described in the following SymWISE documents, in order to throttle the bandwidth used for replication between servers:

Unfortunately, the SymWISE documents above and the Deduplication - Additional Usage Information and the Deduplication Guides here and here, don't really provide clear and consistent information on how to throttle bandwidth, and doesn't reflect true behavior.

(For example, even with throttling properly set, replication will still utilize all bandwidth for the first five minutes, and then throttle down.)

Regardless of the sketchy information, the method for setting bandwidth limits is cumbersome and confusing.

NetBackup and PureDisk need to include bandwidth throttling settings  for replication in the GUI, instead of forcing users to modify multiple text files, and the bandwidth limits need to be enforced at all times.

Comments 7 CommentsJump to latest comment

Prolonging_The_Magic's picture

Someway to schedule different throttle rates would be nice. 

+1
Login to vote
Todd D. Woodward's picture

Great idea to add to the idea! Awesome!

Todd D. Woodward
IT Supervisor, SOC Shift Lead – Appliances SOC
Symantec Corporation
www.symantec.com

Springfield, Oregon

 

 

0
Login to vote
Jim Ganong's picture

Do this enhancement! 

Don't take a lack of responses to this post as ANY indication of how serious this problem is for admins on a day-to-day basis; I talk with other folks using puredisk at conventions, etc... and we all agree on this one.

Thanks!

0
Login to vote
smithgr63's picture

Inclusion of the throttling settings to the GUI and the ability to scheduled the duplication jobs would be welcome additions.

0
Login to vote
SYMAJ's picture

I am looking into resolving this issue on a customer site at present, and after reviewing the information referred to in this note have a number of questions:

1. I understand there was an issue with these parameters not being honoured in earlier releases of the Puredisk code.  Is this issue resolved with 1.4.2 of the appliance code for the 5000 series appliances ?

2. If I edit the agent.cfg file on my 5000 appliances to change the bandwidthlimit parameter from =0 to = 100000, will this effectively limit all of the replication traffic from the appliance to a maximum of 100Mb of the available 4Gb network link ?

3. If I want to put an overall restriction in place is the above parm change the only one I need ?  i.e. do I also need to change the pd.conf files anywhere ?  I believe that the pd.conf changes are only required to implement restrictions on individual replication jobs, and the agent.cfg change will put in place an overall restriction which is what I want

4. Has the issue whereby the restriction was not honoured until after five minutes of the job running been resolved in the 1.4.2 code level ?

Thanks,

AJ

0
Login to vote
SYMAJ's picture

After spending a lot more time on this subject I am still not 100% sure of the control procedure required.  My understanding is as follows:

If I place the bandwidthlimit parameter into the agent.cfg file on each of the 5000 appliances (either by editing the file or through the GUI) this will limit the bandwidth allowed duplication 'per stream'.  Then there is the 'maxstreams' parameter in the pd.conf file - this will limit the streams per replication job.

My issue here is if my understanding above is correct, then I can limit the number of streams per duplication job, and the bandwidth allowed per stream, but how can I control how many duplication jobs are allowed to run concurrently ?

Firstly I understood that the the bandwidthlimit parameter - when used alone - would set an overall limit on the bandwidth allowed for duplication / replication.  The additional information (reflected above) however contradicts this.  See attached for excerts from Puredisk manual from where I got the above information.

Can anyone throw any light on this ?  In summary I want to be able to restrict the overall bandwidth used when replicating backup images from one 5000 appliance to another. 

AJ

AttachmentSize
Limiting Bandwidth Usage for Replication between PureDisk Pools.pdf 203.27 KB
0
Login to vote
SYMAJ's picture

Any Symantec personnel following this ??

I have spoken to Symantec locally and can get no clarification on the questions raised, previous 'posters' in this thread also appear not be able to get clarification.  Does anyone know, will anyone commit ?

AJ

0
Login to vote