Hello,
We have existing replication jobs that are configured for optimal compression level, with the improvements in latest VBR release (better compression and lower CPU usage on higher levels), I want to try and switch our job from Optimal to High, to reduce network traffic over the WAN links, not worried about the increase in CPU as the machine has more than enough for the increased overhead.
Is there anything to be aware of, when changing this on a replication job that has replicated a bunch of VMs using optimal setting, what happens when it's changed to high compression?
My main concern is, I wouldn't want this to trigger some kind of re-replication process, will it use the new setting next run and continue to only sync changed blocks?
-
- Expert
- Posts: 171
- Liked: 19 times
- Joined: Aug 28, 2015 2:45 pm
- Full Name: Mirza
- Contact:
-
- Veeam Software
- Posts: 2838
- Liked: 650 times
- Joined: Jun 28, 2016 12:12 pm
- Contact:
Re: What are the effects of ad-hoc changing replication job compression level?
Hi cerberus,
Please see the the User Guide page on changing Data Compression settings. As noted, changing this for replicas will not change the processing on the next run.
However, please note this entry from the Replica section of the User Guide:
Please see the the User Guide page on changing Data Compression settings. As noted, changing this for replicas will not change the processing on the next run.
However, please note this entry from the Replica section of the User Guide:
So this is only relevant with two proxies for the replica data transfer.Compression is applicable only if VM data is transferred between two backup proxies. If one backup proxy acts as the source and target backup proxy, VM data is not compressed at all.
David Domask | Product Management: Principal Analyst
-
- Expert
- Posts: 171
- Liked: 19 times
- Joined: Aug 28, 2015 2:45 pm
- Full Name: Mirza
- Contact:
Re: What are the effects of ad-hoc changing replication job compression level?
The VM is transferred between two proxies, the source proxy is the actual backup server where VBR is installed and where the VBK files are, and the destination proxy is a separate VM at a remote site.
Just to confirm, if I use the backup server itself as proxy, this still counts as two backup proxies at play?
Just to confirm, if I use the backup server itself as proxy, this still counts as two backup proxies at play?
-
- Veeam Software
- Posts: 2838
- Liked: 650 times
- Joined: Jun 28, 2016 12:12 pm
- Contact:
Re: What are the effects of ad-hoc changing replication job compression level?
Correct, the main point is that the replicas themselves are stored as virtual machines and use snapshots for the restore points, so the compression affects the data transfer. The User Guide's point is that this option is only relevant with two proxies used for the transfer; if you were to use the same proxy for both source and target processing, then the Compression option has no effect.
David Domask | Product Management: Principal Analyst
-
- Expert
- Posts: 171
- Liked: 19 times
- Joined: Aug 28, 2015 2:45 pm
- Full Name: Mirza
- Contact:
Re: What are the effects of ad-hoc changing replication job compression level?
That makes sense, thanks for the info.
Who is online
Users browsing this forum: No registered users and 5 guests