Michaylo_rus

updated

14 years ago

M

Michaylo_rus

1 Rookie

•

49 Posts

0

1204

March 5th, 2013 06:00

Bandwidth configuration

Hi All,

Please help me to understand the correct way how to configure bandwidth throttling. I have a remote site with 3 servers. I defined a dataset, configured the bandwidth throttling for each plug-in, and created a policy with using this dataset and assigned these 3 server into the policy. And now when the policy starts, the backup for all 3 servers start at the same time and as result it occupies 3 times more WAN bandwidth. How I can configure the option to start the backup of clients one by one in the policy?
Or is there another correct way to add the remote clients into backup with using one WAN channel?

Thanks!

  • Michaylo_rus

    1 Rookie

    •

    49 Posts

    695

    0

    Posted March 5th, 2013 11:00

    Ian, thanks for the quick reply I will open a request as you suggested.

    To set 1/3 is a workaround, but the channel will be used not optimal.

    Theoretically, is it possible to create a few policies (1 per server) and start them during a backup window but with using pre/post script which will monitor result of the previous policies?

  • ionthegeek

    2 Intern

    •

    2049 Posts

    695

    0

    Posted March 5th, 2013 08:00

    As far as I'm aware, there isn't a way to schedule clients to run one-by-one in a policy. If there are only a handful of clients, you could create separate schedules to make sure they run in sequence but this isn't really a scalable solution if there are a lot of clients affected.

    If you don't mind all three clients starting at the same time, you could reduce the bandwidth throttle to 1/3 of its current value.

    This sounds like a good enhancement. I would recommend submitting a request for enhancement through PowerLink / Service Center.

  • ionthegeek

    2 Intern

    •

    2049 Posts

    695

    0

    Posted March 5th, 2013 11:00

    I can think of a way to chain policies together but it wouldn't be pretty.

    You could build a pre-script that polls a file on a share somewhere to see if the previous client has completed. Each client would have a post-script that updates the file in some way to notify the next client to start up. It's not elegant but it would probably work.

  • Michaylo_rus

    1 Rookie

    •

    49 Posts

    695

    1

    Posted March 5th, 2013 12:00

    OK, I will go such way as a workaround.

    Thanks )

  • 695

    0

    Posted March 8th, 2013 11:00

    If you are backing up across a WAN you could also consider router based QoS. I have successfully used that in the past to limit the amount of bandwidth a particular set of clients uses for Avamar backups.

    They all share that bandwidth, but if one has more to transfer, or whatever, it won't necessarily be limited to 1/3 of that limit.

    Hope this helps.

    Jonathan

  • Michaylo_rus

    1 Rookie

    •

    49 Posts

    695

    0

    Posted March 13th, 2013 05:00

    Hi Jonathan,

    I see, yes it's workable solution, but unfortunately not in my case.