Comprehensive data protection for all workloads
Post Reply
MAA
Enthusiast
Posts: 83
Liked: 1 time
Joined: Apr 27, 2013 12:10 pm
Contact:

Why "Storage optimizations" only for Target?

Post by MAA »

Why Veeam B&R has settings for "Storage optimizations" only for Target? (Local target, LAN target, WAN target)
Why there are no settings for Source? (Local source, LAN source, WAN source)

dellock6
Veeam Software
Posts: 6032
Liked: 1837 times
Joined: Jul 26, 2009 3:39 pm
Full Name: Luca Dell'Oca
Location: Varese, Italy
Contact:

Re: Why "Storage optimizations" only for Target?

Post by dellock6 » 1 person likes this post

Because that settings means how big is a single block that Veeam compares to others for deduplication purposes: 256kb, 512kb or 1Mb.
The smaller the block, the higher the deduplication ration you can reach so the lower the data you need to send to the target storage, that is why it has those names. On the opposite, there is a higher CPU overhead when using high deduplication ratio.
So, it's not an "optimization" but simply a friendly way to offer you different deduplication ratios.

Luca.
Luca Dell'Oca
Principal EMEA Cloud Architect @ Veeam Software

@dellock6
https://www.virtualtothecore.com/
vExpert 2011 -> 2021
Veeam VMCE #1

Gostev
SVP, Product Management
Posts: 29114
Liked: 5363 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Why "Storage optimizations" only for Target?

Post by Gostev »

MAA wrote:Why there are no settings for Source? (Local source, LAN source, WAN source)
Source (backup proxy) is always "local" to the VM data when Veeam is deployed correctly.

To add to Luca's explanation, these optimizations affects two things the most:
1. Significantly reduces incremental backup size due to smaller blocks (good thing)
2. Significantly reduces data processing throughput due to having to process significantly more blocks (bad thing)

However, when backing up over LAN, and especially over WAN, the primary bottleneck will be network speed anyway. Thus, throughput will not be impacted by these settings, however the benefit of using smaller block size will remain.

MAA
Enthusiast
Posts: 83
Liked: 1 time
Joined: Apr 27, 2013 12:10 pm
Contact:

Re: Why "Storage optimizations" only for Target?

Post by MAA »

Gostev wrote:Source is always "local"
Not always!
I have a source at the main office (LAN source), and source in branch (WAN source), and target at the main office (Local target: local storage in backup server). In my case target is always local.

tsightler
VP, Product Management
Posts: 5905
Liked: 2759 times
Joined: Jun 05, 2009 12:57 pm
Full Name: Tom Sightler
Contact:

Re: Why "Storage optimizations" only for Target?

Post by tsightler »

But if you have a "WAN Source" then there really should be a proxy at that location, thus making it local. Having a proxy local to the source is the proper "best practice" configuration. Of course, what Luca said is actually correct, this setting really just configures the block size used for dedupe, so effectively setting it for the target sets it for the source as well, so it doesn't really matter.

Gostev
SVP, Product Management
Posts: 29114
Liked: 5363 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Why "Storage optimizations" only for Target?

Post by Gostev »

MAA wrote:Not always!
Exactly why I have this note (in red) in my response ;)
Gostev wrote:always "local" to the VM data when Veeam is deployed correctly

MAA
Enthusiast
Posts: 83
Liked: 1 time
Joined: Apr 27, 2013 12:10 pm
Contact:

Re: Why "Storage optimizations" only for Target?

Post by MAA »

The "Source" in your concept is the "vm on esxi host" or "backup proxy"?
In my case "vm on esxi host" and "backup proxy" are located in the branch.
In my case they are not local relative to the Target (backup server and storage)

Gostev
SVP, Product Management
Posts: 29114
Liked: 5363 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Why "Storage optimizations" only for Target?

Post by Gostev »

Source is backup proxy.
Target is backup repository.

Backup proxy should be deployed locally to the processed VM (in the same site).
Sounds like you have Veeam deployed correctly.

Post Reply

Who is online

Users browsing this forum: Bing [Bot], Google [Bot], popjls and 60 guests