I have nothing to do on the weekend, I think of a colleague, I can use VMware to Iruse Cluster, and I will come to play. I found it online, there are not many information about this, two have mentioned some points, manage him, try it.
System configuration: CPU: AMD ATHON XP2500 MEM: 256M * 2 Dual Channel Hard Disk: 80G OS: WinXP SP1 VMware GSX Server 2.5.1 Build-5336 Windows 2003 Enterprise Edition
I usually open a virtual machine on my machine, running is quite smooth, I haven't tried to open two. However, 512M memory should be able to live against.
Less nonsense, first with VMware GSX Server, two Win2003 systems (listening to a tried friend said that Workstation can also do Cluster, but when he is doing it, he doesn't have it, I have to use www.ttdown.com I have a VMware GSX Server version)
Since Cluster requires domain environments, my host is WinXP, and it is not likely to say three virtual machines like online articles, a special DC and DNS, my memory opens two virtual machines. It is already enough. Searched on Microsoft's website, if a node in the Cluster made DC, another node also made DC (article link http://support.microsoft.com/default.aspx?scid=kb) EN-US; 281662), two words do not say, run -> DCPROMO, newly built an ODBA.NET domain, do two virtual machine Test1, test2 into DC, where Test1 is part-time to do DNS.
Each virtual machine requires two network cards, setting as follows:
Test1 Public: IP - 172.17.0.1 Mask - 255.255.255.0 DNS - - 172.17.0.1 Private: IP - 10.1.1.1 Mask - 255.255.255.0
Test2 Public: IP - 172.17.0.2 Mask - 255.255.255.0 DNS - - 172.17.0.2Private: IP - 10.1.1.2 Mask - 255.255.255.0
Since Test2 is also installed with DC, Test2 also has DNS, and opens the area copy. Otherwise, the main DNS (node 1) will be hung down, you will find that the cluster manager can be connected to the virtual server with the cluster manager on node 2, This is because he doesn't know the host name. Of course, this should also be solved by changing the HOSTS file. If you use DNS like me, Test2's NIC settings, DNS Server is 172.17.0.2 instead of 172.17.0.1
Next, create a shared disk cabinet.
With a PlainMaker.exe in the program directory of VMware GSX Server, take advantage of him. Assuming him Copy to you prepare to store the shared disk cabinet file, assume that it is E: / SCSI.
CLUSTER's shared disk cabinet requires at least a quorum disk and a shared disks so we need to create two SCSI disks.
PlainMaker Quorum.pln 200 PlainMaker SharedDisk.pln 2000
This will generate a file in the E: / SCSI directory.
Quorum.pln shareddisk.pln quorum1.dat shareddisk1.dat shareddisk2.dat (Online said only four, but I really have this ^ _ ^)
Next, two SCSI disks are added to the two virtual machines, and they choose the existing virtual disk, select VMware Plain Disks, filename quorum.pln, shareddisk.pln in the open file type.
The most important step, open the .vmx file inside each virtual machine, add disk.locking = "false" at the end.
In addition, Win2003 needs to install SCSI drivers, to the VMware website, can go down to the driven virtual soft mirror (address: http://www.vmware.com/download/downloadscsi.html). Then point the virtual floppy drive to this image, install the SCSI driver for each virtual machine, and then convert two SCSI disks into a Basic disk in disk management, create the main partition, format it to NTFS. The set of 200m is set to Q partition, the volume quorum, 2G is set to S partition, the volume surrogate SharedDisk (so naming is just to be good, you can also name it)
The preparation work is almost, yes, but also to create an account in AD, set to ClusterAdmin to establish and manage Cluster.
Turn off Test2 and open Test1.
Run -> Comclust
Newly built a cluster, named TEST, IP is set to 172.17.0.66, the arbitration
After completing, turn on Test2, start-> Comclust, select the added node to have a cluster
All the way ok.
Open the cluster administrator and set the private to only internal communication only in the network. In the actual Cluster system, connecting two private is the famous "heartbeat".
At this point, VMware Win2003 Cluster creates complete. On this basis, the Cluster of SQL Server and Exchange can continue to test.
