New Feature in 2008 R2 – Cluster Shared Volumes

This week, Microsoft is announcing that Windows 2008 R2 will add a new feature to Failover Clusters called “Cluster Shared Volumes (CSV)”. This feature is being introduced so that they can support the Live Migration feature for Hyper-V. You can get more details about CSV and other 2008 R2 features in the following document:

Windows Server 2008 R2 (Beta) Reviewers Guide –

They are giving sessions about this at WINHEC and TechEd EMEA this week. Unfortunately, I won’t be attending these, but it’ll be really interesting to see where this goes in the future. This certainly gives you an idea of where Microsoft might be heading for future releases of Windows. It seems to me that they’ll be heading towards a “shared everything” model in the future, stacking NLB and perhaps Compute cluster all in one massive cluster solution.

In talking with the cluster team, they don’t currently plan to support this feature in a multi-site cluster environment…it’s not yet clear why. Perhaps it has something to do with possible network latency between the nodes. I’ll post more about this as I get the details.

2 thoughts on “New Feature in 2008 R2 – Cluster Shared Volumes

  1. Yes, it is not supported in multi-site, and the behavior of CSV is weird in this scenario: on non-owning node, any process that tries to access CSV, just hangs and it does not start responding until you move CSV ownership to this node.
    Reason for this is that DCM computes the topology between nodes according the static information in cluster configuration: it searches for cluster network that has both owning and non-owning node’s NIC connected. In case it does not find such network, it mounts the CSV in something like ‘Paused’ state, so any calls through CSV driver to CSV will end in CSV driver waitng for volume to be ready….

    In my opinion, this is not what product team exactly wanted – seems to me that CSV design was done not considering multi-subnet scenarios at all…

Leave a Reply

Your email address will not be published. Required fields are marked *