Windows Server 2012: Part 5.4—Cluster Shared Volumes
August 13, 2012 5 Comments
Slalom consultant and accomplished Microsoft systems developer Derek Martin sheds light on Windows Server 2012 (WS12) through his insightful blog series focusing on his research within the technical preview documentation, personal experimentation with the product, and thoughts of how they can apply to the real world as soon as it is released to manufacturing (RTM).
Sorry about the delay in continuing my series. In the time I was away, I attended Microsoft TechEd (always an impressive show) and got wrapped up with two different clients. All good things but I got a bit distracted. Here is the next installment of the Windows Server 2012 goodness—cluster shared volumes (CSVs).
If you aren’t familiar with CSVs, see this excellent post on TechNet for the full scoop. The basic rendition is this: let’s say you have a cluster of machines and you want to have common storage among all of the instances. This common storage would be used for like SQL Clusters, file server clusters, etc. The problem with CSVs were many, but the main culprits were: they only worked with certain workloads, they were hard to configure, and often broke (typically around patch Tuesday when the head node rebooted).
In Windows 2012, one of the foundational underpinnings of all that is good is storage (hence the sub series on just this). In 2012, like 2008R2, we have the ability to create CSVs for the Hyper-V role. This means that all of my hosts can share a common storage LUN (or SMB3 but that’s another post!) and hosts only write to the blocks they are supposed to because they are smart (they know which Virtual Machines are being run in the cluster by which host). The obvious benefit is that when you need to live migrate from one host to another in the same cluster, all you do is transfer the memory and bam, you’re done. No more LUN remapping which I swear never really worked anyways. CSVs have also been extended now to the file server role, which brings in impressive additional capabilities. But they didn’t stop there.
CSVs in 2012 are even more impressive when you combine cluster aware patching as described earlier as well as drain stopping clusters, taking host nodes into a maintenance mode and particularly with regard to backups. I don’t fully understand the changes to the VSS writers within Windows to fully appreciate all that was done here but I do know that backups are now much smarter and less impactful on storage arrays when snapshots need to be taken.
Here is a list of other goodies that CSVs (along with clustering services in general) bring to the table in Windows 2012:
- Bitlocker support for the CSV
- 63 host nodes per cluster
- 4000 VMs per cluster
- Continuous availability for storage
- Parallel backups support
- Better incremental and snapshot support
Finally, CSVs can also take advantage of other general storage enhancements that are amazing as well:
- Data deduplication
- New file system which supports way bigger drives and more efficient storage (4KB sectors)
- Encrypted hard drive support (full hardware offloading of Bitlockering)
- Support for ODX (Offline Data Transfer) which, if you haven’t seen, checkout the Day 1 Keynote of TechEd North America to see them use ODX to transfer data at 10 GIGABYTES per second (not gigabits…GIGABYTES)
- Full support for the SMI-S protocol so that Windows can talk directly to storage arrays and carve up LUNs and more. Very useful to System Center.
If you are a nerd like me, you will love CSVs and clustering in general in 2012. It is the key to a flexible cloud…well, one of them. Tune in next time where I’ll talk about something completely different maybe!