Link to home
Start Free TrialLog in
Avatar of deltaend

asked on

Server 2012 - Clustered Shared Volumes

Ok, I need some clarification and possibly some help.  For Server 2012 Standard it appears that Microsoft requires Clustered Shared Volumes for pretty much every service in a cluster.  We have really nice servers with traditional RAID cards but fairly inexpensive SATA storage drives.  From what I have read, it seems as if Microsoft have designed their CSV to NOT work either SATA drives or our RAID cards and that drives need to be directly connected to the computer via SAS bus.  My three questions are the following:

1. Have I misread or overlooked something here?
2. Why would Microsoft put such an insane limitation on their CSV if a proper RAID is required for speed and large scale storage?
3. Is there any way to work around the problem to get my system setup for CSV?

Thank you.
Avatar of CTCRM
Flag of United Kingdom of Great Britain and Northern Ireland image

Here are a couple of useful links that I would suggest spending some time reading through first.

2012 Cluster Shared Volumes

Hardware Requirements for CSV

Apologies for not being of much help as this topic is fairlt new to me also.
Avatar of Jim Millard
CSV is an enhancement over "traditional" shared volumes, and is purely meant as enhancement for Hyper-V to permit multiple systems to access different files on the volume simultaneously. It's was necessary for them to allow VMs on the same datastore to be running on different hosts at the same time as part of their "live migration" feature. 2012's support is an outgrowth of that, and is intended to use new SCSI commands for direct-attached disks (which is the case for SAS shelves).

The core issue is that your description suggests that you aren't using hardware that is truly a SAN. CSV--and clustering in general--requires shared peer access that most multi-access drive shelves can't provide, even with a good RAID controller. A fibre channel or iSCSI SAN is needed to accomplish what you're after. It's not a limitation by Microsoft.

Please provide server, HBA, array, & connectivity information so we can better understand the environment. At this point, it looks like you're  getting mad at Lamborghini because their latest supercar can't fly: you're expecting it to do something outside of its design capability.
Avatar of deltaend


OK, perhaps I'm going about this the wrong way.  Can I setup CSV on server's A + B if they are connected to iSCSI targets C and D?
Absolutely. One iSCSI volume is going to be used for the cluster quorum, and you can use the other as the CSV. If you can, add a third volume for the quorum (need <2GB, but that's what I always use) instead of using "full size" volumes.
So, the idea here is that even though Linux and BSD can perform iSCSI in a clustered fashion without the requirement of SAS drives, Windows can't?  Or is it just that CSV can't exist on the same machine as the iSCSI targets that aren't SAS?
I guess it seems that no one really knows.
Avatar of Jim Millard
Jim Millard
Flag of United States of America image

Link to home
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial