Implementing Exchange2003 clusters with VMWAREGSX and W2K3

CPU:AMD Athon xp2000+

MEM:768MB '

Hard drive: 80G

Os:winxp+sp1

VMWare GSX Server 3.0

Windows 2003 Enterprise edition+exchange2003

Enterprise Edition

With VMware GSX Server, three Win2003 systems are allocated, each system allocates 192MB of memory, and memory is set to 576MB in the "HOST" of VMware GSX server.

When installing three Win2003, I first add a network card before each installation, set the first NIC as Vnet0, plus set to Vnet1

Set up for each machine:

CLU1:

vnet0:192.168.61.2

mask:255.255.255.0

dns:192.168.61.10

vnet1:10.1.1.2

CLUS2:

vnet0:192.168.61.3

mask:255.255.255.0

dns:192.168.61.10

vnet1:10.1.1.3

Clussev:

vnet0:192.168.61.10

mask:255.255.255.0

dns:192.168.61.10

vnet1:10.1.1.10

Configure Clussev to the AD service server (set to AD and DNS servers only), and choose Custom if it is set up by default it installs a firewall and the client pings the AD service server. (with 192.168.61.2 or 192.168.61.3 ping 192.168.61.10, but with 10.1.1.2 or 10.1.1.3ping of the pass 10.1.1.10, do not know why)., ad domain name is work.com

Clus1 and Clus2 are made into Clussev member servers and logged in by the administrator. (I am the domain that joins Clus1 and Clus2 to CLUSSEVR)

Two. Create a shared disk cabinet

I read the article on the Internet that the VMware GSX server's program directory has plainmake.exe, but I did not, I downloaded from the Internet.

Copy it to the directory where you want to store the shared disk cabinet file., assuming the K:SCSI

Cluster shared disk cabinets require at least one Quorum disk and a shared disks, so we need to create two SCSI disks. Enter into command mode:

Plainmaker QUORUM.PLN 200

Plainmaker SHAREDDISK.PLN 2000

This creates a file in the E:SCSI directory

Quorum.pln

Shareddisk.pln

Quorum1.dat

Shareddisk1.dat

Add two virtual SCSI disks to Clus1 and Clus2., when adding SCSI mode to select Scsi1:0 and Scsi1:1. When I first tried, I chose scsi0:1 and Scsi0:2, and when I did cluster I said I couldn't find the arbitration disk. The system disk and the arbitration disk cannot be completed on a whole line. Select the existing virtual disk, select VMware Plain disks in the open file type, filename quorum.pln, SHAREDDISK.PLN.

The most important step is to open the. vmx file in each virtual machine and add disk.locking= "FALSE" (You can open it in Notepad) at the end.

In addition, Win2003 needs to install SCSI driver, to the VMware Web site can be down to the drive virtual floppy image (address: http://www.vmware.com/download/downloadscsi.html). Then point the virtual floppy drive to the mirror, install the SCSI driver for each virtual machine, and then convert the two SCSI disks into basic disks in Disk Management, create the primary partition, and format it as NTFS. The 200M is set to the Q partition, the volume label Quorum, the 2G one is set to S partition, the volume label Shareddisk

Three.. Configuring Win2003 Clusters

The NIC Vnet2 of each node (CLUS1,CLUS2) is set to a single rate and half-duplex to stabilize the communication between nodes.

Right-click on each node's Nic Vnet2, properties-----Advanced----WINS----Click Disable NetBIOS over TCP/IP

Back to the Network Connections window, click Advanced---Advanced settings---Adapters and bindings---Move the connection "local connection 2" where Vnet2 is located to the first.

The IP for cluster is set to: 192.168.61.5, with the name: Workcluster

1. Turn the clus2 off. Open Clus1

2. On Clus1, click Start > Administration Tools > Cluster Administrator (or run Cluadmin.exe) to open Cluster Administrator.

3. When the cluster connection is turned on to create a new cluster, press OK, the New Server Cluster Wizard appears, and, as Next,

Set the domain to work.com and enter in the cluster Name: Workcluster, press the next step.

4. Set the computer name to Clus1,r next, in the Profiling Settings window, you will check to see if CLUS1 meets the criteria set up for clustering, and if you pass the check, it will tick before each item. If it is not correct, please check. Press the next step when the check is complete.

5. In the IP address bar, enter: 192.168.61.5, press the next step.

6. In the Cluster service account, enter the account, administrator, and password for managing the cluster, and the network domain.

7. In the recommended cluster setting, press quorum to set the quorum disk to Q

8. Start setting up the cluster, and if you do, each item in the analysis will tick, or try again. Check for faults.

9. After the cluster is established, Cluster Administrator displays the cluster hierarchy.

10. In Cluster Administrator, point to the network, connect the Vnet2 to local 2, right-click the property, and click "Allow internal cluster communication only", as determined.

11. Turn on CLUS2, turn on Cluster Administrator, change the contents of the operation to add nodes to the cluster, and enter Workcluster in the cluster name., follow the prompts step by step.

12. Test the cluster functionality. In Cluster Administrator, the cluster group under the right key group, select the Move group, and determine that all resource owners within the group are converted from Clus1 to CLUS2. When the resource is converted to CLUS2, the CLUS1,CLUS2 is turned on to access the Q disk, and the Q disk is found only on the CLUS2, indicating that only the node that owns the resource can access the resources.

Four Building exchange2003 Clusters

When installing the Exchange2003 cluster, the node must be all open and log in Clus1,clus2.

1. Install the Distributed Transaction Coordinator (MSDTC) first. In Clus1, open Cluster Administrator > Group > Cluster Group > select the new > Resource, enter MSDTC Resource in the new resource name, change the resource resource type to a distributed Transaction Coordinator, and Next, Identify all nodes as owners in the potential owner, and in resource dependencies, add the disk Q and cluster names to the right window and press finish. Click on the new MSDTC resource resource and right-click to select Online.

2. If you install exchange2003 on a node, do not install exchange2003 on each node at the same time, which can cause errors. After the installation is complete, you will find that the exchange-related services on each node are only initiated by Exchange manage, others are manual and do not start, When an Exchange Virtual server is established, which node it connects to, the Exchange service for that node starts.

3. Establish an Exchange Virtual server

Start Cluster Administrator > Group > > New > Group on CLUS1, enter Exchange Virtual Server in the name of the new group, and make sure that the usual user does not need to specify a node. The group is offline after it is established. Choose New > Resources in the newly established Exchange Virtual serve group, enter IP address in the name, select IP addresses for the resource type, and next, make sure all nodes are included in the possible owners. In the resource dependencies do not choose, in the TCP/IP address input you are ready to do Exchang IP, such as: 192.168.61.6, network selected VNET1 the connection (local connection).

Also create new network Name. In the newly established Exchange Virtual serve group, on the new > resource, enter Network name in the name, and next, determine that all nodes are included in the possible owner. In resource dependencies, add IP address to the form, and in the network Name parameter, enter the name you want to do Exchang, such as: Exchwork.

Drag the disk S from group 0 in Cluster Administrator into the Exchange Virtual server group. Press Yes. Right-click the Exchange Virtual Server online. When you are online, establish the Microsoft Exchange System attendant. In the Exchange Virtual serve group, select New > Resource > Name enter Microsoft Exchange System attendant, resource type select Microsoft

System attendant, Next, determine that all nodes are included in the possible owners, add network name and disk s to the resource dependencies, and follow the wizard step-by-step. When you are done, click Ehange Virtual Server online. So the exchange2003 cluster is complete.

In Clus1,clus2 two nodes, only the exchanger service that is connected to the Exchange Virtual server is started, opens the node (CLUS1) that is wired to the Exchange Virtual server, and determines that exchange data is placed in disk S. In Cluster Administrator, right-click the Exchange Virtual Server group, select the Move group, and make sure that you can move to the CLUS2 with the Exchange virtualization servers.

The Exchange2003 and exchange2003 cluster presets do not enable the POP3,IMAP4 service, and if you want to enable both services in the Exchange2003 cluster, you first need to set these two services manually on each node without starting the service. Take the example of enabling POP3 services. Open Cluster Administrator on CLUS1, create a new > Resource in the Exchange Virtual Server group, enter Microsost Exchange POP3 in the name, and set the resource type to Microsost Exchange POP3. Make sure all nodes are included in the potential owner and add Microsoft Exchange System Attendan to the resource dependencies. Step by step.

　　

This article is from: http://doc.linuxpk.com/33204.html