Unsolved
This post is more than 5 years old
2 Posts
0
908
LUN presentation best practices
We plan on having a file server with lots of similar files which should dedupe well.
Shoudl we present an XIO lun directly to the Windows VM and XIO dedupe will work on the files or will having an XIO lun presented to vSphere work just as well in terms of dedupe and/or performance
brettesinclair
2 Intern
2 Intern
•
715 Posts
0
September 5th, 2015 16:00
The data reduction (dedup and compression) is inline so practically it makes no difference. I'd present it to vSphere as normal, create a datastore(s) and put your vm's drives on it/them.
There's no benefit in messing around with RDM's, or in-guest iscsi.
bkatrag407
22 Posts
0
September 6th, 2015 20:00
Right, As Brett mentioned it doesn't matter how you present the LUN to host, In Simple terms, This Data Duplication happens once the host writes reaches the XtremIO device but not at Host level which is writing the data, So with that said XtremIO doesn't care which type of host(Windows VM or ESX server) is writing the data to the XIO LUN, You can present the LUN in any of your preference.
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
October 28th, 2015 05:00
Hi guys,
So to the original questions...it does make sense to put all files with similar data (that can dedup and compress) well on the XIO. eg: all C: drive of VMs, if you got 1000VMs. This will give you best out of dedup and compression.
Any more thoughts ?
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
October 29th, 2015 07:00
Don't forget to look into sdelete/dd to make sure you get the most "thin" benefits possible. Also think about how that translates to VMs (some versions of ESXi support UNMAP , some require manual intervention).