Realization of the Exchange cluster http://www.chinaunix.net with VMware GSX and W2K cluster service: db2ora Posted: 2004-04-09 03:22:05
Using VMware GSX and W2K Cluster Service Exchange Cluster A few days ago, the younger brother finally got the Exchange SQL cluster. It will be written to everyone. I have a little triviality, I hope everyone Haihan. OK, the words returned to Zhengchuan. Part 1: Network configuration, Memory 512M * 2 has three servers, each with two fast web cards: VMNet1, VMNet2. The first server DC01, as an AD, the other two names Cluster1, Cluster2 as two nodes. DC01, Cluster1, Cluster2 network card VMNET1 is in a network segment (192.168.100.0) as a clustered public network. NIC VMNet2 is a network segment (192.168.225.0) for a clustered private network. The VMNet1, VMNet2 of DC01 is from DHCP. IP : 192.168.100.1, 192.168.225.1. VMNET1, VMNET2 for two nodes. Use Static IP. 2: Create a Windows Cluster. 1. Upset the AD, Domain DBA.com, create a CLUST user. According to VMware DHCP The IP, VMNet1 is 192.168.100.1. Install the VMNET2 NIC: Add new hardware - NIC-VMNet2 The IP of VMNet2 is 192.168.225.1. AD Create a host name corresponding to the cluster IP: MyClu 192.168.100.100 2. Create a virtual machine of the first node, 256MB in: Configuration Editor, set the first fast network card "NetWork Adapter" to VMNet1, and add a second network card: add-custom-vmnet2 3. Create a cluster log disk and shared disk Using the PlainMaker: (200MB, 2G) Plainmaker Quorum.pln 200 PlainMaker SharedDisk.pln 2000 will generate quorum.pln, shareddisk.pln, quorum1.dat, shareddisk1.dat Directory cut to the virtual machine, open Quorum.pln, SharedDisk.pln, change the Access's directory to the virtual machine. Such as: Access "c: /VMnode/w2kcluster1/quorum1.dat" access "C: / vmnode / w2kcluster 1 / SharedDisk1.dat "4. In: Configuration Editor", add the log disk and share disk created in the third step: add-harddisk-use an exciting disk-brower-selected Quorum.pln in the virtual machine directory, SharedDisk.pln Open the VMX file in the virtual machine directory, add: disk.locking = "false" 5. Install W2K Advsrv in the first node, set the first fast network card (VMNet1 AMD Adapter) Use Static IP: 192.168.100.20 Settings The second fast network card (VMNet2 AMD Adapter # 2) uses static IP: 192.168.225.2.
Close NetBIOS on each NIC Add to AD 6. Configure Disk in First Node: Sign, Partition, Format 7. Install the cluster service in the first node. : Group: DBACLU- Account: Clust-Managed Disk: Disk 1, Disk 2 - Configuring Cluster Network: Network Name: Local Connection 2, Device: AMD Adapter # 2, IP: 192.168.225.2, Special Network Name: Local Connection, Equipment: AMD Adapter, IP: 192.168.100.20, All Communication (Mixing Networks) Cluster IP: 192.168.100.100 (with public networks in the same network segment), select NIC: "Public Network Card" Close the first node. 8. Create a virtual machine of the second node, steps similar to the first node, but there are a few things to pay attention to the first fast network card is temporarily set: 192.168.100.30, temporarily set the second block: 192.168 .225.3. Close NetBIOS on each network card opens the first node first, open the second node, connect the second node's network card "local connection 2" to "Auto Get", run ipconfig / renew to determine Which network card belongs to the VMNet1 network segment, which piece belongs to the VMNet2 network segment, which is determined to change to the correct IP: 192.168.100.30, 192.168.225.3. Synchronize with the first node. 9. Install the cluster service in the second node, add the cluster DBAClu. 10. Run in two nodes: COMCLUST Part III: Create an Exchange Cluster 1. Install Exchange 2. Run "Cluster Manager" in two nodes, which is created for entity disk resources and name: "Disk Gourp1", corresponding Shared Disk Disk 2 Change this group to "E2kvs01" 3. Select Group "E2KVS01" - New Resource - Resource Type: IP Address - Name: "E2KVS01 IP Address" Enter: 192.168.100.100 (Public with the first node cluster1 The network is in the same network segment). - Connect the Cluster1, Cluster2 into "Possible Owners" - Skip "Dependence" - Select "E2kvs01 IP Address" - Online Work 4. Configuring a virtual server name selection group "E2kvs01" - New Resource - Resource Type: Network Name, Name: "E2KVS01 Virtual Server Name" - incorporate Cluster1, Cluster2 in "Possible owner" - Add resource "E2kvs01 IP Address" Add to "Dependence" - Specifies the virtual server name to e2kvs01 - Select "E2KVS01 Virtual Server Name" - Online Work 5. Select Group "E2KVS01" - New Resource - Resource Type: Microsoft Exchange System Attendent, Name "Microsoft Exchange System Attendent (E2kvs01) "- Encourse Cluster1, Cluster2 into" Possible Owners "- Add Disk 2 (Entity Disk Resources)," E2KVS01 IP Address "," E2kvs01 Virtual Server Name "Add to" Dependence "- Do not perform online work 6.
"Microsoft Exchange System Attendent" starts to do online work, until "MS Exchange Search Instance (E2kvs01). 7. Cluster Transfer: Click" Microsoft Exchange System Attendent (E2kvs01) "- work offline, click Group "E2KVS01" - Mobile group. Sorry everyone, this post I sent it in the evening, my mind is a bit confused, I am correcting a few points: 1. It should be installed on the host, as an AD, virtual 2 servers as a cluster node My expression is not clear, please forgive me.
2. About the download and registration of VMware GSX Server, I provide the Download address of the 嬴 嬴 (http://soft.winzheng.com), if the download can't be downloaded
Try a few more times,
VMware GSX Server Registration Code: 8TTR5-MH8DM-N7MA2-1LMV4
VMware Workstation: Download address: http://download3.vmware.com/software/wkst/vmware-workstation-3.2.1-2237.exe
Registration code: 68M29-DKQ4N-7FQA1-3V0CD
3. About PlainMaker.exe, there is definitely this file in the GSX installation directory, I will pass this file to the Internet, please download. After this file has
You can create a shared disk array in VMware WorkStation and GSX Server.
Let me talk about the method of creating a shared disk array in VMware:
1. Take PlainMaker.exe to the directory of the first virtual machine, such as "C: / VMWIN2K1 / Windows 2000 Professional"
Execute the following command will create a 200M and 2G log disks and shared disks:
PlainMaker Quorum.pln 200
PlainMaker SharedDisk.pln 2000
Confirm that the "C: / VMWIN2K1 / Windows 2000 Professional" directory generates four quorum.pln, shareddisk.pln, quorum1.dat, shareddisk1.dat, open separately
Quorum.pln, shareddisk.pln
Confirm the catalog of Access a line for the current virtual machine.
Such as: Access "C: / VMWIN2K1 / Windows 2000 Professional / Quorum1.dat"
Access "C: / VMWIN2K1 / Windows 2000 Professional / SharedDisk1.dat"
2. In the "Configuration Editor" of the first virtual machine, add the created log disk and share disk: add-harddisk-use an exciting disk-brower-selected Quorum.pln, SharedDisk.pln in the first virtual machine directory
Open the VMX file in the first virtual machine directory, add:
Disk.locking = "false"
SCSI0.Sharedbus = "Virtual"
3. In the "Configuration Editor" of the second virtual machine, add the created log disk and share disk: add-harddisk-use an exciting disk-brower-selected quorum.pln in the first virtual machine directory, SharedDisk.pln
Open the VMX file in the second virtual machine directory, add:
Disk.locking = "false"
SCSI0.Sharedbus = "Virtual"
The second step and third steps will create the log disk and shared disk into shared disk arrays (two virtual machines use quorum.pln, shareddisk.pln in the first virtual machine directory)
4. Open the first virtual machine first, open the second virtual machine, after opening, execute the first virtual machine "Computer Management - Disk Management,
Cancel Welcome to Write Signature and Upgrade Disk Wizard - Right click on Disk 1 - Signature - Signature Disk 1 and Disk 2 after signatures.
"Computer Management - Disk Management of the Second Virtual Machine,
Cancel Welcome to Write Signature and Upgrade Disk Wizard - Right click on Disk 1 - Signature - Signature Disk 1 and Disk 2 after signatures.
Figure:
Welcome everyone to discuss, thank you.
