about installing dual machines with W2K AD SERVER and SQL2000 Enterprise Edition

Server
about installing dual machines with W2K AD SERVER and SQL2000 Enterprise Edition

　
Cluster installation process:
1. Machine Hardware configuration:
Server A
Model CPU memory hard disk array card NIC 1 network card
ML350G3 2.4G 2G 36.4*1 642 HP Integrated HP NC3123

Server B
Model CPU memory hard disk array card NIC 1 network card
ML350G3 2.4G 2G 36.4*1 642 HP Integrated HP NC3123

SMART Array cluster storage
6 hard drive to do ADG (4 hard disk capacity available, allow arbitrary bad two hard drive)

2. Installation and configuration of the system:
Server A
ML350G3 36G hard Drive (divided into two districts C: and D:) Install W2K AD SERVER+SP4
HP Integrated (Gigabit NIC) for external communication, address: 192.168.0.1
HP NC3123 as a Heart jumper IP address between two hosts: 10.10.10.1
Host name is: Server1
Server B
ML350G3 36G hard Drive (divided into two districts C: and D:) Install W2K AD SERVER+SP4
HP Integrated (Gigabit NIC) for external communication, address: 192.168.0.2
HP NC3123 as a Heart jumper IP address between two hosts: 10.10.10.2
Host name is: Server2

SMART Array cluster storage
6 hard drive to do ADG (4 hard disk capacity available, allow arbitrary bad two hard drive), divided into two logical disk:
HEart 500M to do the heartbeat partition of the cluster (letter Z)
SQL 270G storing related data for SQL (letter s)


Cluster information:
IP Address: 192.168.0.3
NetBIOS Name: Testclust


SQL SErvEr2000 Information:
IP Address: 192.168.0.4
SQL Name: Testsql


Step 1: Configure Network information
Server A powered by Server B SmartArray disk cabinet power off
Install WIN2000 AD Server on Server A to set the host name to SERVER1.
Public network ip:192.168.0.1 (DNS: main 192.168.0.1 auxiliary 192.168.0.2)
Heartbeat ip:10.10.10.1 (Gateway and DNS not populated, speed set to 100M Half-duplex, remove DNS registration, WINS) except for TCP/IP and HP team
Install WIN2000 AD Server on Server B to set the host name to SERVER2.
Public network ip:192.168.0.2 (DNS: main 192.168.0.1 auxiliary 192.168.0.2)
Heartbeat ip:10.10.10.2 (Gateway and DNS not populated, speed set to 100M Half-duplex, remove DNS registration, WINS) except for TCP/IP and HP team


Step 2: Install the Active Directory
Install the Active Directory on Server A and configure DNS.
1. In the beginning of the run Dcpromo
2. Follow the installation wizard for the Active Directory, select Domain controllEr for a new domain and then select Domain in a new forEst. Click
3. Enter DNS name: test.com
4. Check the NetBIOS name and continue to the next step.
5. Continue to select Next, accept the relevant file default location
6. Finally, you will be prompted not to contact the DNS server, choose to install on the computer, configure the DNS service
7. Select compatible with WIN2000 previous system
8. Set the password for future recovery of AD as needed, if there is no special requirement to leave it blank
9. Continue, restart server A after Setup finishes
Install Active Directory on Server B and configure DNS (you can choose to join an existing Active Directory when selecting Active Directory properties), DNS Add DNS option in Add removal program.

Step 3: Configure the Cluster
Server A shuts down, Server B shuts down, and the disk cabinet is powered up until the end of the disk cabinet Self-Test (information on the panel is prompted) SERVER A is powered on.
Execute ACU creates an array of hard disks on the disk cabinet, then creates two logical disks (created in ACU, sees two more physical disks in the WIN2000 Disk Management), one 500M uses the cluster heartbeat information and the rest holds the database data.
In Disk Management, format the 500M disk, assign the letter to Z, set the volume label to heart, format the remaining 270G, assign the letter S, and set the volume label to SQL.
SERVER B powered on
Change the newly occurring two partitions according to the configuration in NodeA: Label the volume labeled Heart as the partition letter Z, and label the volume as SQL with the partition letter S.
SERVER b Shutdown
To configure the cluster on Server A:
1. Adding and configuring Cluster services in Add-Remove Programs
2. In the following wizard, select New cluster

3. Enter cluster name Testclust

* Note
The name of the cluster cannot conflict with any host name or domain name on the web! Users can use the administrator, but it is best to create a new one, so as not to change the password in the future and cause the cluster can not start!
4. Select the heartbeat and the public network adapter in the wizard that follows
5. assigning IP addresses to clusters: 192.168.0.3
6. Follow the wizard default option to complete the cluster installation
SERVER b to boot and add the Cluster service to the Add removal program:
The first step in Server B is to add nodes to the cluster, and then find the cluster that server A does well.
Cluster switching can be tested after the installation is complete:
1. Open Cluster Manager on ServerA
2. Right-click on the Testclust group, as shown, select Toggle Group

3. Observation of resource transfer, after a few 10 seconds, the activity group will be transferred to the ServerB.
4. The switch group is then also performed from the ServerB to observe the resource conversion.

Here we have completed the installation of the integration components! The following database is SQL2000 for installation! ***


Step 4: Install the SQL SERVER 2000 Enterprise

Install SQL SERVER2000
1. Perform the installation on Server A and select SQL Server components on the splash screen.
2. Select Install DatabasE SErvEr
3. In the following window, select Virtual Server to enter the name of SQL Server: Testsql

4. Accept the Software License Agreement and enter the ID number
5. In the subsequent FailovEr clustering interface, select Public, and then enter the IP address of SQL Server: 192.168.0.4
6. In the ClustEr disk SElEction interface, select S disk and continue.
7. Then follow the default related options to configure, after installation, in the Cluster management tool to verify that the related resources of SQL has been in the group.

In the cluster management tool to perform a switch to see if the SQL resources can be successfully switched, test the cluster can be smoothly switched.