Windows Cluster installation: 1) preparations before installation

Preface with the step-by-step strengthening of Windows, the cluster application and development under Windows are also gradually evolving. Although it seems that there is still some Yang Chun, without the power and perfection of UNIX, Microsoft has always been a backend engineer. Who dares to say that Microsoft's clusters will not become popular in the future? I am not even prepared to write a series of articles about Windows clusters based on my first experience. From the initial installation to subsequent development, I hope you can give me more encouragement and comments, do not only perform (I) nternet (C) opy (P) aste. Xianzhu shaoxu, look! The Windows version used here is Windows 2008, which supports a cluster with a maximum of eight nodes and does not know about Windows 2008. The following uses Windows 2003 EE as an example to create a cluster with three nodes using VMWare. Due to restrictions, there are not enough physical machines to run, and there is not enough hardware to run eight virtual machines. The two were too few, so they had to run three. VMWare Virtual Machine creation operations ,... Find the corresponding tutorial.

1) system hardware configuration

The following figure shows the even hardware configuration ):

CPU: Xeon 2.8 HT memory: dual-channel 2G (512X4) 266 MHz (133 MHz X2) Hard Drive: SATA 70G

Virtual Machine Configuration:

Operating System: Windows 2003 Enterprise Edition CPU: 1 memory: 384 M first hard disk: SCSI0: 0 lsilogic 8G second Hard Disk: SCSI1: 0 lsilogic 8g nic: Bridging (Bridged) X2

2) cluster configuration

Before installation, check the configuration required by the cluster: Operating System: the Active Directory of the operating system that supports the cluster (such as the Windows 2000 Advanced Server or Windows 2003): Activate Directory domain, the cluster must be installed on the domain computer. Two NICs: one for server communication and the other for cluster communication. Of course, one network card works, but when the cluster is installed, the system will prompt that a single network card is prone to spof. Therefore, we recommend that you use two modules, which are virtual drops and there is no cost. Arbitration Resource: An NS (Network Storage Device) that can be accessed by all nodes. Generally, it is an external disk that uses fiber channel physically. We can't afford it. Fortunately, VMWare provides shared disks. This is why the second hard disk is used in "hardware configuration. Note that the second hard disk must be at least a SCSI device and cannot be on the same bus as the hard disk of the operating system. 3) Open the. vmx file for the shared disk configuration in Vmware and add the following lines:

disk.locking="FALSE"scsi1:0.sharedBus="virtual"

3) install the system

Install Windows 2003 EE now .... Of course, it is the installation disk with SP1, and then upgrade to R2. Since I did not respond for a long time when installing SP2, I canceled the installation of SP2. Settings during installation:

Computer Name: Node0 WORKGROUP: WORKGROUP Nic 1: 192.168.0.200/255.255.255.0, without DNS Nic. 0.0.1/255.255.255.0, without DNS secondary disk: After formatting, the drive letter is set to X

First install a system, assuming it is placed in the Node0 directory. After the installation is complete, shut down VMWare and copy Node0 to the Node1 and Node2 directories. In this way, there are three virtual machines.

4) solve the SID Problem

Because Node1 and Node2 are directly copied versions, their SID is the same as Node0. Later, because you want to upgrade Node0 to a domain server, Node1 and Node2 will not be able to log on to the domain due to SID issues. Therefore, you need to use a tool under Support/Tools of the Windows 2003 installation disk to solve this problem. The procedure is as follows:

Step 1: Run Node1, extract SysRep. Ext and Setupctl. Exe from Support/Tools/Deploy. CAB on the installation disk, and then run SysRep. Exe.

Note: select "Do not reset the activation grace period", set the shutdown mode to "restart", and click "re-encapsulate ". After the system restarts, the SID is reset, and the serial number, region and time, Nic IP address, domain, and so on are required.

Node 1 IP settings:

Nic 1: 192.168.0.201/255.255.255.0, DNS: 192.168.0.200 Nic. 0.0.2/255.255.255.0, DNS: 10.0.0.1

Node 2 IP settings:

Network Adapter 1: 192.168.0.202/255.255.255.0, DNS: 192.168.0.200 Network Adapter. 0.0.3/255.255.255.0, DNS: 10.0.0.1 after logging on to the system, you can also disable it directly. The operation to solve the SID problem can also be performed after the domain is complete. In this way, you can directly set the domain.