The "traditional method" is supported when the cluster is across physical machines. The other method is supported when the cluster is on a single VMware host. One way to illustrate the difference is to think about vMotion-ing one of the machines in the cluster from one ESXi server to another. It's just treated as another process on the machine it is moving. However, in the VMDK case, vMotion knows it is a disk and can manage the disk migration along with the machine migration.
Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more. Asked 9 years, 9 months ago. Active 9 years, 9 months ago. Viewed 2k times. Improve this question. I hope we get a damn good answer — SpacemanSpiff. A comparison would be to a clustered file system, however, unlike other clustered file systems, CSV does not use any proprietary technology — it uses standard NTFS, so there is nothing special you need to purchase or support — it just works!
If your storage is suitable as a standard clustered disk, it can be used as a Cluster Shared Volume. In the past, only one node could host a virtual machine VM and access the VHD on the shared storage, so if another node needed to host the VM or access the disk, it would need to failover and it would affect every resource on that shared disk. With CSV in R2, any node can host the VM and any node can access the VHD on shared storage, so VM and disk ownership can move freely across cluster nodes without impacting any other resources on that shared disk.
If you add another virtual machine, where possible, you should keep the same arrangement for the VHDs on that virtual machine. When you plan the storage configuration for a failover cluster that uses CSV, consider the following recommendations:. To decide how many LUNs to configure, consult your storage vendor. For example, your storage vendor may recommend that you configure each LUN with one partition and place one CSV volume on it. There are no limitations for the number of virtual machines that can be supported on a single CSV volume.
Consider the following examples:. When you plan the storage configuration for a particular virtual machine, consider the disk requirements of the service, application, or role that the virtual machine will support. Understanding these requirements helps you avoid disk contention that can result in poor performance. The storage configuration for the virtual machine should closely resemble the storage configuration that you would use for a physical server that is running the same service, application, or role.
You can also mitigate disk contention by having storage with a large number of independent physical hard disks. Choose your storage hardware accordingly, and consult with your vendor to optimize the performance of your storage. To add a disk to CSV, you must add a disk to the Available Storage group of the cluster if it is not already added , and then add the disk to CSV on the cluster. In Failover Cluster Manager, in the console tree, expand the name of the cluster, and then expand Storage.
Right-click Disks , and then select Add Disk. A list appears showing the disks that can be added for use in a failover cluster. The following Windows PowerShell cmdlet or cmdlets perform the same function as the preceding procedure. Enter each cmdlet on a single line, even though they may appear word-wrapped across several lines here because of formatting constraints.
The following example identifies the disks that are ready to be added to the cluster, and then adds them to the Available Storage group. In Failover Cluster Manager, in the console tree, expand the name of the cluster, expand Storage , and then select Disks.
Select one or more disks that are assigned to Available Storage , right-click the selection, and then select Add to Cluster Shared Volumes. The disks are now assigned to the Cluster Shared Volume group in the cluster.
The CSV cache can boost the performance of read requests without caching write requests. In Windows Server and Windows Server , it's off by default. In Windows Server R2, the CSV cache is enabled by default; however, you must still allocate the size of the block cache to reserve. There are multiple methods to back up information that is stored on CSVs in a failover cluster.
You can use a Microsoft backup application or a non-Microsoft application. You should consider the following factors when you select a backup application and backup schedule for CSV:. Be sure to carefully review what data your backup application backs up and restores, which CSV features it supports, and the resource requirements for the application on each cluster node.
If you need to restore the backup data onto a CSV volume, be aware of the capabilities and limitations of the backup application to maintain and restore application-consistent data across the cluster nodes. For example, with some applications, if the CSV is restored on a node that is different from the node where the CSV volume was backed up, you might inadvertently overwrite important data about the application state on the node where the restore is taking place.
Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Is this page helpful?
Please rate your experience Yes No. Any additional feedback? Note In Windows Server R2 and later, there are multiple Server service instances per failover cluster node. This behavior is by design. Please consult the pages linked in the section More information below.
0コメント