- Posts: 29
- Liked: 4 times
- Joined: May 09, 2015 1:58 pm
Is using "de-dupe friendly" compression setting still valid, or is "optimal" preferred? Also, should I be using "local target?"
The reason I ask, is because some time (perhaps years) ago I had changed these to "optimal" and "local target 16+TB" after reading something that I cannot find now. None of our backups are anywhere close to 16TB. The largest is probably about 2TB or less.
I've been running out of space on my ExaGrid, so I'm trying to tweak some things to buy time before I can install a new one.
Please only answer if you're familiar with ExaGrid specifically, as I understand that its settings are not the same as other de-dupe appliances.
- Veeam Software
- Posts: 4029
- Liked: 732 times
- Joined: May 04, 2011 8:36 am
- Full Name: Andreas Neufert
- Location: Germany
Block size... „local“ means 1MB block size which is optimal for the Exagrid engine.
At other dedup appliances „local 16TB“ is used to increase the sequential processing and read ahead cache hit rate at restore. It comes usually with a penalty at random read restores.
So for Exagrid „local“ is OK.
Please keep in mind that any change here will become only active when you perform an „active full“.
Veeam own dedup can be enabled and this is compatible with all dedup engines. It is usually not enabled for dedup engines as if you disable it Veeam changes metadata read pattern at restore which is better for dedup storage. Usually you do restores from the Exagrid landing zone which is not deduped, so it make sense to leave Veeam dedup enabled.
For compression you have 3 options.
Disabled (not recommended as more traffic as needed is processed over the network).
Optimal + Repository setting „uncompress...“
Or dedup friendly which is the recommended one for exagrid based on tests.
- Veeam Software
- Posts: 129
- Liked: 33 times
- Joined: Apr 20, 2017 4:19 pm
- Full Name: Joe Houghes
- Location: Austin, TX
You'll also see this in their reference architecture of a Veeam/Pure Storage/Exagrid environment, which they have located here: https://www.exagrid.com/wp-content/uplo ... ecture.pdf (settings on page 49)
Having been a long time Veeam & Exagrid customer before coming onboard to Veeam, I don't remember ever reading anything relating to using the 'Local target (16 TB + backup files)' storage optimization setting, at least not in regards to using that with Exagrid. If someone had written that up for some reason, it could have been long ago, as Exagrid has changed their documentation to recommend the same "local target" option at least since their Veeam v9 integration guide.
Users browsing this forum: Google [Bot] and 10 guests