LSFS vs LSFS with dedpup vs Flat File System
Posted: Thu Oct 06, 2016 5:57 pm
I am intrigued by LSFS, but want more details on when to use each of the 3 file options you offer, LSFS, LSFS w/Dedupe, and FLAT. I am guessing (but I couldn't find documentation) that LSFS w/Dedup shouldn't be used for Boot OS VM Volumes? (this is just based of MS best practices for HyperV). So is LSFS without Dedup OK for boot VM volumes or is Starwind resilient enough you can use Dedup on Boot OS Volumes?
I will have 2 arrays now on DL380's, 1 is 2.5 10K SAS in Raid 10, that I plan to use for boot OS volumes. 1 6x SATA Raid 6 that I plan to use for data (obvious LSFS w/Dedup would excel here). I can add a 3rd array in the future possibly using 4-6x 1tb 2.5 WD Reds in Raid 10.
What is a good allocation file types on hardware for different functions? Would LSFS (no dedupe) be good for boot volumes (even with its possible slower read performance)?
And I assume that either is not ideal for cold Archival data, so I plan to store that outside of Starwind (probably replicated with DFS on to the other server).
I will have 2 arrays now on DL380's, 1 is 2.5 10K SAS in Raid 10, that I plan to use for boot OS volumes. 1 6x SATA Raid 6 that I plan to use for data (obvious LSFS w/Dedup would excel here). I can add a 3rd array in the future possibly using 4-6x 1tb 2.5 WD Reds in Raid 10.
What is a good allocation file types on hardware for different functions? Would LSFS (no dedupe) be good for boot volumes (even with its possible slower read performance)?
And I assume that either is not ideal for cold Archival data, so I plan to store that outside of Starwind (probably replicated with DFS on to the other server).