How to limit the network speed for replicate backups?
While backup Disk1 with "acrocmd backup disk --disk=1" we can limit the network speed via parameter --network_speed=8192kb.
But we need first to backup Disk1 to a local HDD and than copy it to network share. We use the command "acrocmd replicate backup" but there is no parameter to limiting the network speed for copying the image. Our Machine has only a 100mb NIC and Acronis would be use the whole bandwith for replicate.
Even in the "validate archive" exists a parameter "--read_speed" to limit the bandwith, so I miss such a function for exporting/replicating backups.
How we can limit the network speed while replicating the backup to share?
Thanks for your commend Ramil, but to use a replication plan didn't solve our problem really.
If we use a backup plan with two targets (local HDD an second to network share) then we have two solve two different problems.
1. on the backup plan we have only one parameter to limit the speed, and if I'm not wrong, the limitations is for all targets in this plan, not only to limit the network speep. If we set this parameter we limit also the speed of our HDD, or not?
2. by creating a backup plan, we cann't create a backup chain for quarterly F-I-I backups. There isn'nt a feature for backup chains like in ATI2017.
So we chose to backup our Disk by commandline tool acrocmd. Unfortunately with acrocmd we have to manage two jobs to backup on two targets (HDD and copy to network share too). For backup to HDD we need no limitation of speed, but for the second step, copy to share, we need a limitation. So we run into a new problem, with acrocmd we can limit the transfer speed to HDD (we needn't it), but we aren't able to limit network speed, but we need to limit it.
Now I have no idea how to create a replication plan which will work on each client (about 500 or more client) with different targets (HDD havent always the same driveletter). Nor I know always the time when the full backup is ready to copy, nor I know always the name of the backup. And how do I replicate only the last backup of each client and can be sure, that the backup is valid?
I would really to prefer using plans in the "Plan" section, but then we need a feature for backup chains, or we have to use acrocmd, then we can scedule our own chain, but then we need a limitation on network speed too.
Best regards
Sigi
Hi
1. Yes, speed limitation also limits disk speed.
2. I think it is still possible to solve your problem:
- Create archive using acrocmd (as you do right now)
- Replicate archive using special "replication plan". Replication plan is a special plan that only replicates backups. It is not the same as backup plan. Replication plan is created in the "Plans"->"Backup replication" section.
Hi,
I just tried your sugestion, but with this solution I cann't use ASZ as source!
Our first target is a local disk with secure zone -> this works well, as a plan and also by using acrocmd. Our second target is a network share. So I try your solution and I'm not able to select ASZ as source on my Agent as a plan.
If I use acrocmd, I can use ASZ (but unfortunately no speed limitation): acrocmd replicate backup --loc="atis:///asz" --arc="...
Have a look in my Acronis dokumentation (it's in german, but I think you know it), ASZ is'nt valid as source.
How solve this (new) problem? Don't understand me wrong, but always when I think I have found a way to do it right with Acronis, I fail because AB 12.5 doesn't support our minimal requirements.
Hi
We implement replication from ASZ using special replication in future versions (internal ID: ABR-125588).
Right now I can suggest dirty hack:
- Create archive using acrocmd (as you do right now)
- Back up archive file to network share (yes, double backup).
Drawback is that you should do recovery twice: recover archive file, then start recovery from recovered archive file.
Hi,
Ok, it's really a dirty hack, but I will give it a chance.
Today I tried a workaround with an existing plan (backup to local HDD and second target is a network share). first I exported the plan and open it in a texteditor, found two (!) parameter to limiting speed as I expected.
One parameter to limit diskspeed an some lines down, the second parameter to limit networkspeed! So I changed both attributes to different values for testing and import the plan back. (The limitation was switched off in plan and the values were 100 percent by default = no limitation)
But it seems that Acronis didn't implement or use both parameters, only the diskspeed value is used, as I see on network usage during replication to share, it's nearly at 90% and not at 30%:
I think it schould not be so hard for Acronis to implement te second limitation right, as it's already exists in the plan, or im wrong?
Hi
"diskSpeed" and "networkSpeed" in fact set the same option in the underlying code (something like "output speed"). That's why it is impossible to set both options via GUI. In your case network speed limitation is 90%.
Hi
We are adding right now option "--network_speed" to "replicate backup", "export backup" and "export archive" (internal ID:ABR-136217). This functionality will be released in Acronis Backup 12.5 Update 2 (end of 2017 right now).
Hi,
OK thanks for your information. I'm looking forward to the Update.
Hi Ramil,
I just testing the version 12.5.8610, but I Didn't find any changeing to the previous version.
In a new plan I can still use only one parameter to limit the speed:
If I look into the plan (via export and edit), I see both limits used the same value:
So if I use the networklimit to prevent havy use on my LAN, I also limit the diskspeed. Am I right?
I thought with Update 2 the limitations would be splitet in network AND diskspeed?
Best regards
Sigi
Hi
> So if I use the networklimit to prevent havy use on my LAN, I also limit the diskspeed. Am I right?
Correct. I said that in previous messages in this thread.
> I thought with Update 2 the limitations would be splitet in network AND diskspeed?
No, we didn't plan this. We implemented options "--network_speed" and "--disk_speed" for backup replication and exporting.
You can use these options and limit the network usage during backup replication.