Comprehensive data protection for all workloads
- Posts: 84
- Liked: 2 times
- Joined: Jan 20, 2011 5:45 pm
- Full Name: Mike Schlottman
When selecting the Optimization of a backup, does the level of optimization,i.e. WAN, LAN or Local, have a significant effect on the time it takes to roll up incrementals into a full backup? I have all of my backups set to WAN, but I could potentially set the to LAN if it could have an effect on my roll up of incrementals.
My biggest bottlneck is IO speed of the disks on my linux veeamtarget. I have plenty of CPU and memory, but rolling up my incrementals can take up to 9 hours for a single job when no other jobs are running on those disks. I do weekly rollups, and am considering changing that to doing rollups almost every night.
- Veeam Software
- Posts: 19877
- Liked: 1844 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
Yes, WAN target setting produces additional processing overhead coming from the quantity of blocks that need to be processed (due to a half smaller block size). This obviously affects storage as more I/O operations needed to write the same amount of data.
Note that you'll have to run the full backup for the change to take effect.
- VP, Product Management
- Posts: 5775
- Liked: 2616 times
- Joined: Jun 05, 2009 12:57 pm
- Full Name: Tom Sightler
Using WAN target will can cause more blocks to be moved, however, if it happens to make significantly smaller increments (for example, in the case of servers with many small changes) then it can actually improve the performance of transformation since, even though the blocks are smaller, there is less total data to move.
Users browsing this forum: Bing [Bot], Google [Bot] and 70 guests