Discussions specific to the VMware vSphere hypervisor
Post Reply
adept1
Enthusiast
Posts: 29
Liked: 4 times
Joined: May 09, 2015 1:58 pm
Contact:

ExaGrid best practice

Post by adept1 » Jan 05, 2019 12:46 am

I was reading the best practices for ExaGrid https://www.veeam.com/kb2056.

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.

Thanks!
Alex

Andreas Neufert
Veeam Software
Posts: 3914
Liked: 707 times
Joined: May 04, 2011 8:36 am
Full Name: Andreas Neufert
Location: Germany
Contact:

Re: ExaGrid best practice

Post by Andreas Neufert » Jan 06, 2019 4:35 pm 1 person likes this post

In general Exagrid is a dedup storage, but has a non deduped fast landing zone for fast restore for random Veeam workloads.

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.

adept1
Enthusiast
Posts: 29
Liked: 4 times
Joined: May 09, 2015 1:58 pm
Contact:

Re: ExaGrid best practice

Post by adept1 » Jan 07, 2019 5:06 am

Thanks. I have set back to recommended values and doing active fulls.

jhoughes
Veeam Software
Posts: 114
Liked: 28 times
Joined: Apr 20, 2017 4:19 pm
Full Name: Joe Houghes
Location: Austin, TX
Contact:

Re: ExaGrid best practice

Post by jhoughes » Jan 08, 2019 2:30 pm

Exagrid will also have the recommendations of using the settings of "dedupe friendly" for compression and "local target" for storage optimization within their integration guide, which you can download from the Exagrid Grid Manager itself (located in the Help section).

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.
Husband, Father, Solutions Architect, Geek Extraordinaire | @AustinVMUG & @ATXPowerShell leader | vExpert | Cisco Champion | Tech Field Day Delegate | VCP 4/5/6 | VCP6-NV | VMware/Cisco UCS/Powershell/VEEAM Enthusiast

Post Reply

Who is online

Users browsing this forum: No registered users and 9 guests