Windows Server 2012 Cluster Shared volume combat

Cluster shared volumes, a simple understanding is a distributed Access file system for Hyper-V optimization, where nodes in a cluster can write to a disk at the same time, and are controlled access to avoid data-writing conflicts. This feature is similar to VMware's VMFS. This feature is available from Windows Server 2008, where a user creates a virtual machine in a failover cluster, typically using a virtual assignment of a separate disk LUN, so that each virtual machine has its own LUN to enable independent failover. But the current arena is no longer a single fight. When the number of virtual machines is large, the user's management costs for LUNs and clustered virtual machines increase.

Once the cluster shared volume is enabled, the following are called CSV, and multiple VMS distributed on multiple cluster nodes on the node can access their VHD files at the same time. These VHD files can coexist in the same LUN and do not affect their failover.

Benefits of CSV: In addition to managing the configuration more easily than before, and making more efficient use of disk space, the number of virtual machine LUNs is greatly reduced, before the LUN is the unit of failover, so you need to create a separate LUN for each VM, and in CSV, multiple VMS can use the same LUN, It does not affect the transfer of other VMS on the same LUN; administrators can easily track the path of the VHD files and other files used by the VM, instead of using a drive or a GUID identifier to identify the disk, and when using CSV, the path appears on the node computer's system partition \ The Clusterstore folder. And when viewed from any node, the path is the same, and the fewer LUNs you use, the faster the validation link is when you set up the cluster, if there are more than 10 or 20 LUNs, the verification time is really not flattering, OK, now this problem is solved.

As for the operation of the cluster shared volume, that is a very simple matter, we look at the operation, of course, my premise is that the Hyper-V failover cluster has been built. If you can assign a 1GB quorum disk and a number of capacity data disks to a failover cluster as needed, our CSV will open on this data disk.

To enable cluster Shared volumes: The method is to locate the appropriate LUN under the storage node, right-click "Add to Cluster shared volumes"

More Wonderful content: http://www.bianceng.cnhttp://www.bianceng.cn/OS/server/

At this point, when we look at the information for this LUN, we can see that the change has changed and that the original partition number has become on each node: c:\clusterstorate\volume1, this information corresponds to each node in the cluster, so the system disk for each node must be the same, To achieve a shared disk space for the same LUN. As shown in the following illustration:

Using Cluster Shared volumes: When users use a clustered shared volume, they simply store the virtual machine files under C:\clusterstorage\volume1, and each VM has a separate folder under this directory, and we are ready to use CSV to create a Windows 2003 SP2 's virtual machine.

Next, we need to select a storage node for the VM:

Then enter the name of the VM and the storage location, which is c:\clusterstorage\Volume1, when we create a successful directory to generate test in this directory, dedicated to the VM virtual machine files.