Книга: Mastering VMware® Infrastructure3

Virtual Machine Clustering Scenarios

Virtual Machine Clustering Scenarios

The clustering of Windows Server 2003 virtual machines using Microsoft Cluster Services (MSCS) can be done in one of three different configurations:

Cluster-in-a-Box The clustering of two virtual machines that exist in the same ESX Server host.

Cluster-Across-Boxes The clustering of two virtual machines that are running on different ESX Server hosts.

Physical-to-Virtual Clustering The clustering of a physical server and a virtual machine that is running on an ESX Server host.

Clustering has long been considered an advanced technology implemented only by those with high technical skills in implementing and managing high-availability environments. While this might be more rumor than truth, it is certainly a more complex solution once the virtual machine solution is blended into the deployment.

While you may achieve results setting up clustered virtual machines, you may not receive support for your clustered solution if you violate any of the clustering restrictions put forth by VMware. The following list summarizes the dos and don'ts of clustering virtual machines as published by VMware:

? Only 32-bit virtual machines with a boot disk on local storage can be configured as nodes in a server cluster.

? Only two-node clustering is allowed.

? Virtual machines configured as cluster nodes must use the LSI Logic SCSI adapter and the vmxnet network adapter.

? Virtual machines in a clustered configuration cannot be connected to a switch configured with a NIC team.

? Virtual machines in a clustered configuration are not valid candidates for VMotion, nor can they be part of a DRS or HA cluster.

? ESX Servers hosts that run virtual machines that are part of a server cluster cannot be configured to perform a boot from SAN.

? ESX Server hosts that run virtual machines that are part of a server cluster cannot have both QLogic and Emulex HBAs.

Оглавление книги