SQLServer2005故障转移群集详解

PDF文件

Server2005

下载需积分: 3 | 1.03MB | 更新于2025-01-21 | 107 浏览量 | 举报收藏

立即下载

"SQLServer2005FOC是关于微软SQL Server 2005故障转移群集的详细技术文章，由Allan Hirt (Avanade, Inc.) 和 Dave Whitney (Microsoft)撰写，旨在为已经熟悉或计划使用SQL Server 2005故障转移群集的IT专业人士提供深入的指导。该文档由Louis Berner和Tresy Kilbourne在Microsoft进行项目编辑。" SQL Server 2005是微软的一个关键数据库管理系统，提供了高可用性和灾难恢复解决方案，其中故障转移群集(FOC)是其核心特性之一。故障转移群集允许在多个服务器节点之间共享资源，当主服务器发生故障时，可以自动将工作负载转移到备用服务器，确保服务的连续性。本文档主要针对技术受众，而非技术决策者，它补充了SQL Server 2005 Books Online中的现有规划、实施和管理故障转移群集的文档。对于已使用过SQL Server 2000故障转移群集的用户，该白皮书还特别指出了SQL Server 2005中故障转移群集实现与SQL Server 2000之间的差异。 SQL Server 2005的故障转移群集改进可能包括但不限于以下方面： 1. **性能提升**：SQL Server 2005可能在处理速度、内存管理和I/O优化方面有所增强，从而改善了群集的整体性能。 2. **更高级别的自动化**：可能引入了更先进的自动化工具，简化了故障检测和转移过程。 3. **扩展的群集支持**：可能增加了对更多节点的支持，提高了可扩展性和容错能力。 4. **更好的资源管理**：可能改进了群集中资源的分配和监控机制，使得故障转移更加智能。 5. **安全性增强**：SQL Server 2005可能会有新的安全特性，如增强的身份验证和加密，以保护数据安全。 6. **备份和恢复策略**：可能提供了更灵活的备份选项和更快的恢复时间目标(RTO)。 7. **服务连续性**：通过改进的群集架构，可能实现了更高的服务连续性和更低的停机时间。由于市场条件的变化，微软可能在发布后对产品进行更新和改进，因此文档中的信息可能随时间变化。微软不对此类信息的准确性做出保证，但文档仍是了解SQL Server 2005故障转移群集的重要参考资料，对于规划、部署和维护SQL Server 2005高可用性环境的专业人士极具价值。

Failover Clustering for SQL Server 2005 and SQL Server 2005 Analysis Services 12

Directory, not on the individual cluster nodes. These steps may need to be performed

by your Network Administrator.

Important: All accounts and groups must be set up and verified before installing

your cluster. If your server cluster is running SQL Server 2000 and SQL Server 2005

in a side-by-side configuration, never use the same service accounts for your SQL

Server 2005 installation that you use for your SQL Server 2000 instances. Failure to

use a separate set of service accounts will result in unexpected security behavior

between your side-by-side and SQL Server 2005-only server cluster installations

To Create a Group

1. In Control Panel, double-click Administrative Tools, and open Active Directory

Users and Computers.

2. In the left pane, expand the domain that will be used.

3. Right-click Users, point to New, and then click Group.

4. In the New Object – Group dialog, enter an appropriate name in the Group name

text box. Select a group scope of Global. An example is shown in Figure 3.

5. Click OK.

Figure 3. Creating new domain groups at the domain level using Active

Directory Users and Computers.

To Add Users to a Group

1. Select the group which was just created, and double-click.

2. Click the Members tab.

3. Click Add.

Failover Clustering for SQL Server 2005 and SQL Server 2005 Analysis Services 14

In practice, this means that you are limited to a maximum of 22 or 23 usable, named

disks with drive letters (assuming one local system drive, some sort of optical drive

such as a DVD-ROM, and the possibility of a shared quorum drive). Unlike SQL Server

2000 failover clustering, SQL Server 2005 failover clustering does support the use of

mount points (or "mounted volumes") to ease disk expansion and administration. All

disks must be formatted as Basic disks. Dynamic disks are not supported out of the box

in a cluster installation; see Knowledge Base article 237853 Dynamic disk configuration

unavailable for server cluster disk resources. Third-party tools may be employed to

utilize dynamic disks with a cluster installation.

If you define more than one logical disk per physical logical unit number (LUN), that

disk will appear as one drive to the cluster, not two. So unless you are placing Analysis

Services and the relational engine in the same cluster group (which is not a

recommended configuration), there is no benefit to carving out two logical disks on one

LUN in a cluster, since that LUN will be in a single cluster group.

Mount points are fully supported in a clustered configuration of SQL Server 2005, but

they require the use of a drive letter just like a standard disk resource. As with a

standard cluster disk resource, mount points must be added to the resource group

containing SQL Server, and added as a dependency.

Whether or not your storage area network (SAN) shares disks for creating LUNs, make

sure that the SAN engineer properly zones and masks the LUNs so that only the cluster

nodes can see the LUNs it needs to see, and no one else can see or access them.

If Analysis Services is clustered in the same group with the Database Engine, Setup will

place any shared system files for both products on the default drive selected during

Setup itself. After that, Microsoft recommends providing Analysis Services with its own

disk resources not only for availability, but to ensure that Analysis Services has what it

needs to perform properly.

Note: SQL Server 2005 supports iSCSI, and adheres to any Windows iSCSI support

requirements. However, SQL Server installations require a dedicated, not shared,

adapter for iSCSI devices.

Number of SQL Server Instances per Cluster

With SQL Server 2005, the maximum number of supported instances that can be

deployed on a Windows Server failover cluster in a clustered SQL Server configuration

is 25 for Enterprise Edition and 16 for Standard Edition. These are different from the

limitation on a stand-alone system, which is a tested limit of 50. With SQL Server 2000,

the limit was 16.

Even though you technically can configure up to 25 instances, the maximum number of

instances you can deploy depends upon the hardware resources available, including

available drive letters. Therefore, 25 deployed instances would mean that there is only

one local drive for Windows, you are using a Majority Node Set (local quorum) server

cluster that does not use a drive letter for a quorum disk, and you are only assigning

one cluster disk per instance.

Before installing and configuring a multiple instance cluster, think about why you may

need multiple instances of SQL Server: Is it for consolidation? Mixed version levels for

supporting multiple applications with specific requirements? Easier administration?

Meeting individual service level agreements (SLAs)? Maximizing hardware usage? These

Failover Clustering for SQL Server 2005 and SQL Server 2005 Analysis Services 15

and other issues must be thought out at the planning stage because the appropriate

hardware must meet the expected capacity at any given moment.

In a clustered configuration, however, you must also take into account the failover

scenario when planning multiple instances: if in a worst case scenario you have multiple

nodes fail in the cluster and are down to one node, can a single node run all of your

instances given the capacity planning that was done? If not, then capacity was likely

not given sufficient consideration.

Installing a SQL Server 2005 Failover Cluster

Before installing SQL Server SQL Server 2005 in a clustered configuration, the

underlying Windows failover cluster must be installed and fully tested. This installation

must also include the configuration of a clustered Microsoft Distributed Transaction

Coordinator (MS DTC). Since SQL Server is built upon the Windows layer, if it is not

installed and verified before the SQL Server installation, the SQL Server setup process

will fail.

Install your SQL Server 2005 failover cluster in the following order:

1. Install and cluster Windows, and make sure that all relevant patches are applied

as per the Knowledge Base articles, Recommended hotfixes for Windows 2000

Service Pack 4-based server clusters or Recommended hotfixes for Windows

Server 2003-based server clusters. For step-by-step instructions on how to

configure a Windows Server 2003 failover cluster, read the Guide to Creating

and Configuring a Server Cluster Under Windows Server 2003.

2. Configure a clustered MS DTC. For information on installing MS DTC, consult

either Knowledge Base article 301600, How to configure Microsoft Distributed

Transaction Coordinator on a Windows Server 2003 cluster or Knowledge Base

article 204209, How to rebuild or move a MSDTC installation to be used with a

SQL failover cluster.

3. Verify that the underlying Windows failover cluster is properly configured and

working.

4. Verify that there is at least one dedicated shared disk on the cluster for the SQL

Server instance.

5. Verify that a dedicated and unique IP address and name (whether it will be a

default or a named instance) has been reserved for SQL Server.

6. Create the users and groups at the domain level for use with your clustered

instance(s) of SQL Server 2005.

7. Add the groups to your local nodes and give the groups the proper rights on

each node as per the SQL Server 2005 Books Online topic Setting Up Windows

Service Acccounts.

8. Cluster SQL Server 2005.

9. Perform any post-installation tasks.

Once the Windows and MS DTC portions of the installation are complete, the

administrator must create a cluster group for the intended SQL Server installation, and

that group must contain at least one shared cluster disk for use by SQL Server. Detailed

requirements for installation are described in Installing SQL Server 2005

and Before

Installing Failover Clustering.

Failover Clustering for SQL Server 2005 and SQL Server 2005 Analysis Services 16

Note: Before installation, all settings and policies should be identical across all

nodes of the cluster for consistent behavior, including all security-related policies,

hotfix installations, driver installations, and locales. If a change is made after

installation, that change must be reflected on all nodes as well.

Before installation, we recommend logging off all users on the cluster nodes except the

node where setup is being started.

Best Practice: SQL Server 2005 requires the .NET Framework version 2.0 on all

nodes. While Setup will do install .NET Framework 2.0 on its own, we recommend

installing this prerequisite before attempting to install SQL Server 2005 to speed up

the installation process.

SQL Server 2005 failover clustering can be installed in one of three ways:

• Running Setup.

• From the command prompt with switches.

• From the command prompt with a fully configured .ini file.

For more information about using Setup, see Appendix A as well as How to: Create a

New SQL Server 2005 Failover Cluster (Setup). For more information about installing

from the command prompt, see How to: Install SQL Server 2005 from the Command

Prompt. A template for the .ini file can be found on the installation media under

\Servers with the name template.ini. Examples can also be found in Appendix C.

Installation from the command prompt is an enhancement to SQL Server 2005. Other

enhancements to the Setup process include the following:

• The current node's name is written at startup to the SQL Server log and to the

Windows Event log.

• Installation proceeds in parallel on all nodes.

• The installation rolls back on all nodes if Setup fails on any one node.

• Logging of Setup operations is improved.

• Error messages during Setup are improved.

• Setup Consistency Checker detects the state of machines before installation.

• Setup now includes error reporting.

• Unattended setup has feature maintenance, allowing you to later add, remove, or

reconfigure your SQL Server installation.

• The Installation Wizard includes progress reporting, and Setup can be canceled.

Installing on a Domain Controller

Because of the performance requirements of a SQL Server 2005 failover cluster,

clustered installations are not supported on a node that is a domain controller. If you

install on a domain controller and encounter a problem, you may be required to

reconfigure the cluster. Here are some of the problems associated with installing on a

domain controller:

• Overhead associated with running a domain controller. A domain controller that is

otherwise idle can use anywhere between 130 to 140 MB of RAM, which includes

running Windows Clustering. There is also replication traffic if the domain controller

has to replicate with another domain controller within the domain and across

domains.

剩余107页未读，继续阅读

sandos

粉丝: 0

SQLServer2005故障转移群集详解

foc.rar_ foc matlab_dspic foc_foc_foc control_风机 FOC

STM32-FOC-SDK-使用指南中文版_foc_stm32foc教程_stm32-foc_

foc.rar_FOC MATLAB_FOC-control_foc_foc simulation_foc_

FOC.rar_FOC 异步_FOC控制_Foc 教学_foc_异步电机 FOC

FOC.rar_FOC_FOC控制_foc_matlab foc_磁场导向

FOC.rar_FOC 离散模型_foc_foc 电动机_motor_异步电动机foc

Simulation_FOC.rar_FOC MATLAB_direct foc _foc_in

FOC_foc_FOC控制_synchronousmotor_永磁同步电机FOC仿真_

FOC.zip_FOC转速环设计_MATLAB FOC_SIMULINK_foc双闭环仿真_simulink FOC

MC-FOC.zip_FOC_FOC视频教程_Foc教程_focmc.com_foc程序教程

最新资源