SQL Server 2000+ MS WIN2003 Cluster service configuration

Server SQL Server 2000+ MS WIN2003 Cluster service configuration



I. Demand

Many enterprises use SQL Server to provide business system background data Services, as the enterprise operation on these business systems, how to improve the reliability of these systems, high availability has attracted more and more attention of enterprises.

To meet the high availability fault-tolerant business needs of enterprise systems, Microsoft strongly recommends that users use Windows Server 2003 Enterprise Edition, SQL Server 2000 Enterprise Edition to build their business application and collaboration Office platform. Because of the built-in cluster clustering features in Windows Server 2003, SQL Server 2000, and a shared disk cabinet or san,2 server that enables cluster configuration, SQL Server 2000 (node server 1) provides a hot standby for external services, That is, the full use of the server hardware resources, but also greatly improve the entire business application and collaboration Office system high availability, as shown in the figure:





I. Programme

Since Microsoft's cluster cluster configuration must have a domain environment support, depending on whether the domain controller has a separate physical server to bear, the configuration can be divided into two categories, called standard configuration and streamlined configuration, as follows.

Scenario One: Standard configuration
In this configuration, 2 domain controllers are independent and assume the functions of AD Domain user authentication, DNS service, and so on.




Programme II: Streamlined configuration
In some cases, the user's environment has no domain presence, and there are only 2 servers, at which point an attempt is made to double 2 clustered servers as AD domain controllers and DNS servers. This hybrid streamlined configuration reduces system reliability and availability, and Microsoft strongly recommends that you use a stand-alone domain controller.



First, step

The following is an example of a streamlined configuration scenario to explain the installation configuration of the system and verify its feasibility.

3.1 Windows Server 2003 cluster installation configuration
For more information about installation configuration for Windows Server 2003 cluster systems, refer to

Http://blog.csdn.net/longrujun/archive/2005/01/08/244617.aspx

3.2 Installing the Microsoft Distributed Transaction Coordinator

Before you install SQLSERVER2000 on a server running Windows Server 2003, you must first install the Microsoft Distributed Transaction Coordinator (MSDTC) on the cluster.

1. Log in to any node in the cluster, such as NodeA;

2. Click Start, point to All Programs, point to Administrative Tools, and then click Cluster Administrator.

3. Under cluster group, right-click Cluster Group, point to New, and then click Resources;

4. In the name box of the new resource, type a name, such as MSDTC, in the Resource type list, select Distributed Transaction Coordinator (DTC), and in the group list, make sure Cluster Group is selected.




Next,

1. Verify that all nodes (Nodea,nodeb) are already present in the "Possible owners" list.




Next,

6. Select the quorum disk "Qdisk:q" and "Cluster Name" resources as dependent resources,





Ok

7, Ok,

Right-click Cluster Group, and then click Bring Online to make the Distributed Transaction Coordinator resource "MSDTC" on-line.




3.2 SQL Server 2000 cluster installation configuration



The cluster installation of SQL Server 2000 has been integrated directly into the SQL Server 2000 Database Setup Wizard to automatically identify the cluster system on Windows Server 2003 and enable the database Virtual server option to implement SQL Server 2000 the automatic installation configuration of the cluster virtual server on 2 servers. Remember to install the SQL2000 SP3 patch package when the installation is complete. Here is a screenshot of the way to see its simple and automatic installation configuration process.
To ensure that the SQL Server 2000 cluster is installed automatically on 2 servers, 2 servers NodeA and NodeB, and shared disk cabinets must be on the power-on online state.
A, install SQL Server 2000

Install Sql2000_ent on the node server NodeA, put it into the SQL Server 2000 Enterprise installation CD, and start the SQL Server 2000 Installation Wizard;



When the Setup wizard enters the computer name interface, the cluster system for Windows Server 2003 is automatically recognized and the virtual Server option is enabled.




Select this option to enter the virtual SQL Server name Virsqlcluster, Next,

User information interface, next,

User License Agreement Interface Click Yes,

Failover clustering interface, enter the IP address "172.17.0.100", select Network "Public" and click "Add" to add it to the list, as shown in




Next,

Cluster disk Selection interface, select "Disk S:" for "Group 0",




Next,

Cluster management interface to ensure that both NodeA and NodeB are in the configured nodes list, as shown in




Next,

Remote Information "interface, enter user name, password and domain name, as shown in




Next,

Instance name interface, select "Default", as shown in




Next,

The installation type interface, select Typical because the previous disk has selected "Disk S:" for "Group 0", and the "Destination folder" data file is automatically positioned to the S: disk, while the SQL Program files are automatically installed in the 1 and 2 Local disk-related directories, as shown




Next,

Service Accounts interface, select Use the same account for each service, and because of the cluster configuration, the "Use Local System Account" option automatically expires, enter a username, password, and domain name,




Next,

.......

Next,

Select the licensing mode interface and select Processor License, as shown in




Next,

The Setup Wizard enters the automatic installation configuration process,




Wait until the "Installed" interface appears



Ok, the installation is complete.

Open Cluster Administrator to see more than two SQL Server resources in the resource type, because SQL Server 2000 Enterprise Edition is a cluster-aware application system that automatically adds the serviced components that support cluster when the configuration is installed;




"Group 0" to see the addition of the original "Disk S:" New 5 SQL resources are added, and are online,



Describes the SQL Server 2000 cluster installation configuration complete; test results

As shown in figure




B, install SQL Server SP3 patch Package

Start SQL Server Service Pack 3 Installer, "Welcome" interface, Next,
Computer name interface, enter the cluster virtual server name Virsqlcluster, click Next,
Connect to server interface, select Windows Authentication, Next,
Back Compatibility List interface, select Upgrade Microsoft Search and apply SQL Server SP3 (required), Next,
Error reporting interface, Next,
Remote Info interface, enter username, password and domain name, next,
The Setup Wizard performs the required operation on the cluster nodes (NodeA and NodeB) and waits;
Switch to Cluster Administrator during the installation wait process to see several SQL Cluster-aware services in the offline state;
After the SP3 installation is complete, the following message box appears, click OK;
"Install finished" interface, select "Yes, I want to restart computer Now", click [Finish], node server NodeA reboot;
Restart the node server after the NodeA boot completes NodeB

The SQL Server 2000 cluster installation configuration is complete.

For installation configuration details on SQL Server 2000 cluster systems, see

Http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/sql/deploy/confeat/failclus.asp



Document download
1.win2003 Cluster
http://www.51-net.com/flash/win2003 cluster (DOC). rar
http://www.51-net.com/flash/win2003 cluster (pdf). rar

2.SQL Server Cluster
http://www.51-net.com/flash/SQL2000 Cluster.rar