Implement Exchange Clustering Using VMwareGSX and W2K cluster services

Article Title: Use the VMwareGSX and W2K cluster services to implement Exchange clusters. Linux is a technology channel of the IT lab in China. Includes basic categories such as desktop applications, Linux system management, kernel research, embedded systems, and open source.
　　 Part 1: network configuration, memory 512 MB * 2
There are three servers, each with two fast virtual NICs: VMnet1 and VMnet2. the first server DC01 serves as AD, the other two servers are named cluster1, and cluster2 serves as two nodes. the network card VMnet1 of DC01, cluster1, and cluster2 is in the same network segment (192.168.100.0) and serves as the cluster public network.
The VMnet2 Nic is in the same network segment (192.168.225.0) as the private network of the cluster.
Among them, the VMnet1 and VMnet2. of DC01 are all IP addresses allocated from DHCP: 192.168.100.1, 192.168.225.1.
VMnet1 and VMnet2. use static IP addresses.
　　
　　 Part 2: Create a Windows Cluster.
1. Install AD on the host, the domain name dba.com, and create a clust user.
Based on the IP address assigned by VMware DHCP, VMnet1 is 192.168.100.1.
Install VMnet2 NIC: Add new hardware-nic-VMnet2
Based on the IP address assigned by VMware DHCP, VMnet2 is 192.168.225.1.
In AD, create a host name that corresponds to the cluster IP Address:
For example, myclu 192.168.100.100
2. Create a VM on the first node. The memory size is 256 MB. In: configuration Editor,
Set the first Nic Network Adapter to VMnet1 and add the second NIC: Add-custom-VMnet2
　　
3. Create a cluster log disk and a shared Disk
Use plainmaker In the VMware installation directory: (200 MB, 2G)
Plainmaker quorum. pln 200
Plainmaker shareddisk. pln 2000
Cut the generated quorum. pln, shareddisk. pln, quorum1.dat, and shareddisk1.dat to the Virtual Machine directory and open them respectively.
Quorum. pln, shareddisk. pln change the directory of the ACCESS row to the directory of the virtual machine.
For example, Access "C: \ vmnode \ w2kcluster1 \ quorum1.dat"
Access "C: \ vmnode \ w2kcluster1 \ shareddisk1.dat"
　　
4. in: configuration Editor, Add the log disk and shared disk created in step 3: Add-HardDisk-use an exciting disk-brower-select quorum in the Virtual Machine directory. pln, shareddisk. pln
Open the vmx file in the Virtual Machine directory and add disk. locking = "FALSE" in the last line"
　　
5. Install W2k Advsrv on the first node and set the first fast NIC (VMnet1 AMD Adapter) to use the static IP address 192.168.100.20
Set the second fast network Adapter (VMnet2 AMD Adapter #2) to use the static IP address 192.168.225.2.
Disable NetBIOS on each Nic
Add to AD
　　
6. Configure disks on the first node: sign, partition, and format disks 1 and 2 (log disks and shared disks ).
　　
7. Install the cluster service on the first node:
Cluster name: DBACLU-account: clust-managed Disk: Disk 1, Disk 2-configure cluster network:
Network Name: Local Connection 2, device: AMD Adapter #2, IP: 192.168.225.2, Private Network
Network Name: local connection, device: AMD Adapter, IP: 192.168.100.20, all communications (hybrid network)
Cluster IP Address: 192.168.100.100 (in the same network segment as the public network), select NIC: "public network nic"
Close the first node.
　　
8. The procedure for creating a VM on the second node is similar to that on the first node.
When installing w2k adv, set the first fast network adapter to 192.168.100.30 and the second to 192.168.225.3.
Disable NetBIOS on each Nic
Enable the first node first. Enable the second node. Set "local connection, local connection 2" to "Automatic Acquisition" for the NIC at the second node ",
Run ipconfig/renew to determine which network adapter belongs to the VMnet1 network segment and which one belongs to the VMnet2 network segment, and change it to the correct IP Address:
192.168.100.30, 192.168.225.3. synchronize with the first node.
　　
9. Install the cluster service on the second node and add it to the cluster DBACLU.
　　
10. Run comclust on two nodes respectively.
　　
　　 Part 3: Create an Exchange Cluster
1. Install Exchange on both nodes
2. Run "Cluster Manager", which creates a group for the physical Disk resources and name it "Disk Gourp1", corresponding to shared Disk 2
Rename this group to "E2KVS01"
3. Select the group "E2KVS01"-new resource-resource type: IP Address-name: "E2KVS01 IP Address" input: 192.168.100.100 (with the public network of the first cluster1 node in
Same Network Segment ).
-Add cluster1 and cluster2 to "possible owners"-Skip "dependency"-select "E2KVS01 IP Address"-Online work
4. Configure the virtual server name
Select "E2KVS01"-new resource-resource type: Network name, name: "E2KVS01 virtual server name"-set cluster1, ter2 is included in "Possible owner"-Add the resource "E2KVS01 IP Address" to "dependency"-specify the virtual server name E2KVS01-
Select "E2KVS01 virtual server name"-Online work
5. select "E2KVS01"-new resource-resource type: Microsoft Exchange System Attendent, name "Microsoft Exchange System Attendent (E2KVS01)"- ter1, ter2 is included as "Possible owner"-add Disk 2 (physical disk resources), resource "E2KVS01 IP Address", "E2KVS01 virtual server name" to "dependency "-
Online work is not performed at this time.
6. From "Microsoft Exchange System Attendent (E2KVS01)" to "MS Exchange Search Instance (E2KVS01.
7. Cluster Transfer:
Click "Microsoft Exchange System Attendent (E2KVS01)"-Work offline,
Click E2KVS01 to move the group.