SQL Server 2000 MS Win2003 Cluster Service Configuration One, Demand
Many companies have adopted SQL Server to provide business system background data services. With the operation of the company's dependence on these business systems, how to improve these systems, high availability has increasingly attracting attention. In order to meet the high availability of enterprise systems, Microsoft recommends users using Windows Server 2003 Enterprise Edition, SQL Server 2000 Enterprise Edition to build its business application and collaboration office platform. Since Windows Server 2003, SQL Server 2000 built-in Cluster cluster function, plus a total of disk cabinets or SANs, 2 servers can implement cluster configuration, SQL Server 2000 (Node Server 1) provides services to each other to serve each other, With server hardware resources, it has greatly improved the high availability of the entire business application and collaborative office system, as shown in the figure:
First, program
Since Microsoft's Cluster cluster configuration must have domain environment support, depending on whether the domain controller has a separate physical server, the configuration scheme can be divided into two major classes, temporarily called standard configuration and streamline configuration, the specific situation is as follows.
Scheme 1: Standard Configuration This configuration, 2 domain controllers independently, bears AD domain authentication, DNS services and other functions.
Solution 2: In some cases, the user's environment does not exist, and there is only one server, at which point 2 cluster servers can also be used as the AD domain controller and the DNS server. This mixed streamlined configuration can reduce the reliability and availability of the system, and Microsoft strongly recommends using separate domain controllers.
First, step
The following is an example of a thin configuration, to explain the system installation configuration and verify its feasibility.
3.1 Windows Server 2003 Cluster Installation Configuration For installation configuration details for Windows Server 2003 cluster systems, please refer to
http://blog.9cbs.net/longrujun/archive/2005/01/08/244617.aspx
3.2 Installing the Microsoft Distributed Transaction Coordinator
You must first install the Microsoft Distributed Transaction Coordinator (MSDTC) on the cluster on the cluster on the server running on the server running Windows Server 2003. 1. Log in to any node in the cluster, such as Nodea;
2. Click Start, point to "All Programs", then point to Administrative Tools, and then click Cluster Manager;
3. Under the "Cluster Group", right-click "Cluster Group", point to "New", and then click Resources;
4. In the "New Resources" box, type name, such as "MSDTC"; in the Resource Type list, select Distributed Transaction Coordinator (DTC) ", in the Group list, make sure Select the "cluster group",
NEXT,
1. Verify that all nodes (nodeb) have appeared in the "Possible Owner" list,
NEXT,
6. Select Arbitration Disk "QDisk: Q" and "Cluster Name" resources as dependent resources.
OK
7, ok,
Right-click "Cluster Group", click "Bring Online", make the Distributed Transaction Coordinator "MSDTC" online.
3.2 SQL Server 2000 Cluster Installation Configuration
SQL Server 2000 cluster installation has been directly integrated into the Database Setup Wizard of SQL Server 2000, automatically recognizes the cluster system on Windows Server 2003 and enables database virtual server options to implement SQL Server 2000 cluster virtual servers on 2 servers. Automatically install configuration. Remember, after the installation is complete, you must install the SQL2000 SP3 patch package. The following is a simple and automatic installation configuration process in a screenshot. To ensure that the SQL Server 2000 cluster is automatically installed on 2 servers, 2 servers Nodea and NodeB, and shared disk cabinets must be on-line. A. Install SQL Server 2000 Install SQL2000_ENT on Node Server Nodea, put it into the SQL Server 2000 Enterprise Edition installation disc, start SQL Server 2000 installation wizard; install the WIT INTF to the Computer Name interface, automatically identify Windows Server 2003 The cluster system enables the "Virtual Server" option, select this option, enter the virtual SQL Server name virsqlcluster, next, user information interface, Next, User License Protocol interface Click "Yes", "Failover Cluster" interface, enter IP Address "172.17.
0.100 "
, Select the network "public", click Add, make it added to the list, as shown in Figure NEXT,
"Cluster Disk Selection" interface, select "Group
0 "
"Disk s:",
NEXT,
The Cluster Management interface ensures that Nodea and NodeB are in the "Configured Node" list, as shown
NEXT,
Remote Information interface, enter your username, password and domain name, as shown
NEXT,
Instance name "interface, select" Default ", as shown
Next, "Install Type" interface, select "Typical", due to the previous disk selected "Group
0 "
"DISK S:", "Data File" of "Destination Folder" is automatically positioned to the S: disk, and the SQL program file is automatically installed to 1 and 2 local disk related directories, as shown
NEXT,
"Service Account" interface, select "Using the same account for each service", because it is a cluster configuration, "Using the Local System Account" option automatically invalid, enter username, password and domain name,
NEXT,
.......
NEXT,
"Select License Mode" interface, select "Processor License", as shown in the figure,
NEXT,
The installation wizard enters the automatic installation configuration process.
Waiting until "Installation" interface OK, the installation has completed the "Cluster Manager", you can see more than two SQL Server resources in "Resource Type", because SQL Server 2000 Enterprise Edition is Cluster-Aware Application system, automatically adds service components that support Cluster when installing configuration;
"Group
0 "
It can be seen in addition to the original "Disk S:", there is a new SQL resource, and it has been online, indicating that the SQL Server 2000 cluster installation configuration is completed; test results
Figure
B, install SQL Server 2000 SP3 patch package
Start SQL Server 2000 Service Pack 3 installer, "Welcome" interface, Next, Computer Name screen, enter Cluster Virtual Server Name Virsqlcluster, click Next, "Connect to Server" interface, select "Windows Authentication", NEXT, "Rear Compatibility List" Interface, Select "Upgrade Microsoft Search and Apply SQL Server 2000 SP3 (Required)", Next, Error Report interface, NEXT, "Remote Information" interface, enter your username, password and domain name, Next The installation wizard performs the required operation on the cluster node (Nodea and Nodeb), waiting to be switched to "Cluster Manager" during the installation waiting process, and see several Cluster-Aware services of SQL are offline; SP3 After the installation is complete, the following message box will be displayed, click [OK]; "Installation" interface, select "Yes, I want to restart the computer now", click [Finish], Node Server Nodea Restart; Nodea Launched After completing, restart the node server nodeb to this, the SQL Server 2000 cluster installation configuration is complete.
For details on installation configurations for the SQL Server 2000 cluster system, see
Http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/sql/deploy/confeat/failclus.asp
Document Download 1.Win2003 ClusterHttp: //www.51-net.com/flash/win2003 Cluster (DOC) .rarhttp: //www.41-net.com/flash/win2003 Cluster (PDF) .rar2.sql Server 2000 ClusterHttp: //www.51-net.com/flash/sql2000 cluster.rar
