Clustering and High Availability

What Every MCT Needs What Every MCT Needs to Know about to Know about Clustering and High Clustering and High Availability Availability

Rodney R. FournierRodney R. FournierMicrosoft MVP - Windows Server - Microsoft MVP - Windows Server - Clustering Clustering Net Working America, Inc.Net Working America, Inc.

AgendaAgenda

Terms you need to knowTerms you need to know

Four Types of ClusteringFour Types of Clustering

What is Clustering?What is Clustering?

Overview of Exchange ClusteringOverview of Exchange Clustering

Overview of SQL Server Failover ClusteringOverview of SQL Server Failover Clustering

MSDTCMSDTC

ResourcesResources

AgendaAgenda

Terms you need to knowTerms you need to knowFour Types of ClusteringFour Types of Clustering




MSDTCMSDTC

ResourcesResources

Terms you need to knowTerms you need to knowActive/Passive vs. Active/Active vs. InstanceActive/Passive vs. Active/Active vs. Instance

Failover & FailbackFailover & Failback

HeartbeatHeartbeat

Quorum vs. Majority Node SetQuorum vs. Majority Node Set

Shared StorageShared Storage

Resources vs. Resource GroupsResources vs. Resource Groups

High-availability vs. Fault ToleranceHigh-availability vs. Fault Tolerance

Scalability vs. AvailabilityScalability vs. Availability

Mean Time To FailureMean Time To Failure

Mean Time To RecoverMean Time To Recover

Node, Virtual Server, IP, Name, etc.Node, Virtual Server, IP, Name, etc.

Cluster awareCluster aware

AgendaAgenda


Four Types of ClusteringFour Types of ClusteringWhat is Clustering?What is Clustering?



MSDTCMSDTC

ResourcesResources


High Performance ComputingHigh Performance Computing

Component Load BalancingComponent Load Balancing

Network Load BalancingNetwork Load Balancing

Server ClusteringServer Clustering

High Performance High Performance Computing (HPC)Computing (HPC)

Super ComputingSuper Computing

Also called HPC Clusters or Also called HPC Clusters or SuperclusterSupercluster

As many as 256 nodesAs many as 256 nodes

Strong competition for UNIX/LinuxStrong competition for UNIX/Linux

http://www.microsoft.com/windowsserver2003/hpc/default.mspx

Special applicationsSpecial applications



Component Load Balancing Component Load Balancing (CLB)(CLB)

Component Object Model (COM+) Component Object Model (COM+) components load balancingcomponents load balancing

Calls to activate COM+ components are Calls to activate COM+ components are load balanced to different servers load balanced to different servers within the COM+ clusterwithin the COM+ cluster

http://www.microsoft.com/applicationcenter/techinfo/deployment/2000/AppCenterCLBTechOver.doc

Application Center 2000Application Center 2000




Network Load Balancing Network Load Balancing (NLB)(NLB)

Up to 32 nodesUp to 32 nodesLayers 2 and 3 of the OSI Layers 2 and 3 of the OSI modelmodelCan provide ScalabilityCan provide ScalabilityProvides AvailabilityProvides AvailabilitySupported on version of Supported on version of Windows Server 2003Windows Server 2003http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/clustering/nlbbp.mspx

IIS, SharePoint Portal IIS, SharePoint Portal Server, VPN Remote Server, VPN Remote Access, ISA, Terminal Access, ISA, Terminal ServerServer

http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/clustering/nlbbp.mspx




Server ClusteringServer ClusteringWINSWINS

DHCPDHCP

Exchange ServerExchange Server

SQL ServerSQL Server

File SharesFile Shares

PrintersPrinters

Message QueuingMessage Queuing

Distributed Transaction CoordinatorDistributed Transaction Coordinator

Generic Service or ScriptGeneric Service or Script

Volume Shadow Copy Service TaskVolume Shadow Copy Service Task

Microsoft Search ServiceMicrosoft Search Service

AgendaAgenda


Types of ClusteringTypes of Clustering

What is Clustering?What is Clustering?Overview of Exchange ClusteringOverview of Exchange Clustering


MSDTCMSDTC

ResourcesResources

Shared Nothing ModelShared Nothing Model

Network HeartbeatNetwork Heartbeat

External Storage ArrayExternal Storage Array

Node ANode A

Node BNode B

PublicPublic

PublicPublic““Shared Nothing”Shared Nothing”For more information, see For more information, see 293289

http://support.microsoft.com/?id=293289

BasicsBasics

Quorum = ClusteringQuorum = ClusteringStores most current configuration data in Stores most current configuration data in quorum recovery logs and registry checkpointsquorum recovery logs and registry checkpointsMaintains resource checkpointsMaintains resource checkpointsProvides persistent physical storageProvides persistent physical storage

Recovery Logs used toRecovery Logs used toEnable any node to form a clusterEnable any node to form a clusterEnable nodes to maintain a clusterEnable nodes to maintain a clusterGuarantee that a single cluster is formedGuarantee that a single cluster is formed

Cluster.Log fileCluster.Log fileLogs cluster activity; great for troubleshootingLogs cluster activity; great for troubleshooting

Server Cluster Components Server Cluster Components (Windows-based)(Windows-based)

Server Cluster

Public Network

Shared Disk Array

Node A Node B

Heartbeat

Virtual serverVirtual serverFrom client/application perspective, the server From client/application perspective, the server names or IP addresses used for accessnames or IP addresses used for access

Hardware components of server clusters:Hardware components of server clusters:Cluster nodesCluster nodes

Internal heartbeatInternal heartbeat

External networkingExternal networking

Shared clusterShared clusterdisk array:disk array:

Quorum diskQuorum disk

Data disksData disks

Hardware ConsiderationsHardware ConsiderationsBuy systems from the Windows Server Buy systems from the Windows Server Catalog: Cluster Solution – Hardware Catalog: Cluster Solution – Hardware Compatibility List (HCL) Compatibility List (HCL)

http://www.microsoft.com/windows/catalog/server/default.aspx?xslt=categoryproduct&subid=22&pgn=8b712458-b91c-4a7d-8695-23e9cd3ae95b

Entire systems, not individual componentsEntire systems, not individual components

Ask your preferred vendor for helpAsk your preferred vendor for helpGet guarantees!Get guarantees!

Buy a support agreement that matches your level Buy a support agreement that matches your level of availabilityof availability

Remember a PSS contract, too!Remember a PSS contract, too!

Availability requirements, budget, 8Availability requirements, budget, 8thth & 9 & 9thth layerlayer




Shared Disk ConfigurationShared Disk Configuration

Instance-to-disk ratio: Two resources cannot Instance-to-disk ratio: Two resources cannot share a physical disk share a physical disk Basic disks only; mount points and dynamic Basic disks only; mount points and dynamic disks are not supported disks are not supported File compression and encryption are not File compression and encryption are not supportedsupportedUse Fibre Channel if you can; use SCSI if Use Fibre Channel if you can; use SCSI if cost is a factor or iSCSIcost is a factor or iSCSIUse hardware-based RAID only; Software-Use hardware-based RAID only; Software-based RAID is not supportedbased RAID is not supportedEach RAID controller is differentEach RAID controller is different

Turn writeback caching off if controller in server nodesTurn writeback caching off if controller in server nodes

……continuedcontinued


Be sure all disks are dependencies of the Be sure all disks are dependencies of the SQL Server/Exchange resourceSQL Server/Exchange resource

Disk is single point of failure. Store spare Disk is single point of failure. Store spare drives and have a secondary form of high drives and have a secondary form of high availabilityavailability

DataDataRecommended: RAID 10 array of mirrored sets Recommended: RAID 10 array of mirrored sets that are then stripedthat are then striped

RAID 5 okayRAID 5 okay

LogsLogsRAID 1 or possibly mirrored sets that are then RAID 1 or possibly mirrored sets that are then striped; not RAID 5striped; not RAID 5

Network-attached storage (NAS)Network-attached storage (NAS)Not supported for clustersNot supported for clusters

Storage area networks (SANs)Storage area networks (SANs)Only those on the HCL Cluster list or the Only those on the HCL Cluster list or the Cluster/Multi-Cluster Device list can Cluster/Multi-Cluster Device list can be usedbe used

Get verification that it is set up properly Get verification that it is set up properly Setup is usually done by the vendorSetup is usually done by the vendor

Do not accept the default configuration—it Do not accept the default configuration—it will probably be for a file systemwill probably be for a file system

iSCSI is now supported with 2003 SP1iSCSI is now supported with 2003 SP1


Software ConsiderationsSoftware Considerations

Exchange/SQL Server 2000 Enterprise Exchange/SQL Server 2000 Enterprise EditionEdition

Operating systems:Operating systems:Windows Server 2003 Enterprise EditionWindows Server 2003 Enterprise Edition

Windows Server 2003 Datacenter EditionWindows Server 2003 Datacenter Edition

Network ConfigurationsNetwork Configurations

Cluster nodes with Windows domains, DNS, Cluster nodes with Windows domains, DNS, and WINSand WINS

You may still need WINS for NetBIOS resolutionYou may still need WINS for NetBIOS resolution

Nodes and virtual server must be able to access Nodes and virtual server must be able to access the domainthe domain

All nodes have to be in the All nodes have to be in the samesame domain domain

Network Card SettingsNetwork Card SettingsDo not set NICs to AutodetectDo not set NICs to Autodetect

You need at least 4 static IP addresses: 1 for each node, You need at least 4 static IP addresses: 1 for each node, 1 for the server cluster, 1 for Clustered Service/Application1 for the server cluster, 1 for Clustered Service/Application

Recommend 6 (additional dedicated heartbeat NICs)Recommend 6 (additional dedicated heartbeat NICs)

Multiple IP AddressesMultiple IP AddressesUse separate subnets for IP addressesUse separate subnets for IP addresses

BandwidthBandwidth

Network ConfigurationNetwork Configuration

Server Cluster

Public Network

Shared Disk Array

Node A Node B

Heartbeat

Processor/MemoryProcessor/Memory ConfigurationConfiguration

Configure each cluster node with processing power Configure each cluster node with processing power sufficient to handle the load for any process that sufficient to handle the load for any process that may run on itmay run on it

Set Processor Affinity to N–1 if necessarySet Processor Affinity to N–1 if necessary

Test your application before putting it into Test your application before putting it into productionproduction

Monitor processor usage. Use System MonitorMonitor processor usage. Use System Monitor

MemoryMemorySingle-instance: No issues unless other services or Single-instance: No issues unless other services or applications are runningapplications are running

Multiple-instance: Be sure that one instance will not Multiple-instance: Be sure that one instance will not diminish the resources of other processes or instances diminish the resources of other processes or instances in the event of a failoverin the event of a failover

External Storage ArrayExternal Storage Array

Node ANode A

Node BNode BXXNetwork HeartbeatNetwork Heartbeat

““Shared Nothing”Shared Nothing”For more information, see For more information, see 293289

FailureFailureFailureFailure

PublicPublic

PublicPublic


So Why Cluster?So Why Cluster?

Provide High-AvailabilityProvide High-AvailabilityFailover mitigates outage when hardware Failover mitigates outage when hardware failure occursfailure occursStrengthened by fault tolerant designStrengthened by fault tolerant designMeasured in 9sMeasured in 9s

Managed maintenance/upgradesManaged maintenance/upgradesRolling UpgradesRolling Upgrades

TermTerm NinesNines Downtime per YearDowntime per Year

NirvanaNirvana 100.00100.00 0 seconds0 seconds

5 Nines5 Nines 99.99999.999 5 minutes5 minutes

4 Nines4 Nines 99.9999.99 52 minutes52 minutes

3 Nines3 Nines 99.999.9 8.7 hours8.7 hours

2 Nines or Fired2 Nines or Fired 9999 3.7 days3.7 days

What Don’t You Get?What Don’t You Get?

Does not protect against:Does not protect against:

Loss of or damage to shared storageLoss of or damage to shared storage

Network failuresNetwork failures

Application failures or database Application failures or database corruptioncorruption

DisastersDisasters

Human errorsHuman errors

Does not load balance mailboxesDoes not load balance mailboxes

Cannot move running applications, and Cannot move running applications, and shared state is lost!shared state is lost!

AgendaAgenda




Overview of Exchange ClusteringOverview of Exchange ClusteringOverview of SQL Server Failover ClusteringOverview of SQL Server Failover Clustering

MSDTCMSDTC

ResourcesResources

Overview Of Exchange Overview Of Exchange ClusteringClustering

Exchange Virtual Server (EVS)Exchange Virtual Server (EVS)Physical Disk resource: SCSI, Fibre Physical Disk resource: SCSI, Fibre Channel (FC), or Internet SCSI (iSCSI)Channel (FC), or Internet SCSI (iSCSI)

IP Address resourceIP Address resource

Network Name resourceNetwork Name resource

System Attendant resource and resources System Attendant resource and resources created by System Attendantcreated by System Attendant

Resources created by an administrator Resources created by an administrator (for example, protocol virtual servers)(for example, protocol virtual servers)

Clustering ExchangeClustering ExchangeClient PCsClient PCs

Node ANode A Node BNode B

Disk cabinet ADisk cabinet A

Disk cabinet BDisk cabinet B

HeartbeatHeartbeatEVSEVS Passive NodePassive Node

Failure Failure Occurs!Occurs!

SCSISCSIReserveReserveBrokenBroken

EVS fails overEVS fails overand is available to and is available to

clientsclients

EVSEVS

New Reservation New Reservation EstablishedEstablished

7+1 Active/Passive7+1 Active/Passive

2+0 Active/Active – Not Recommended2+0 Active/Active – Not Recommended

1+1 Active/Passive1+1 Active/Passive

Overview Of Exchange Overview Of Exchange ClusteringClusteringOverview Of Exchange Overview Of Exchange ClusteringClustering

Requirements For Requirements For Clustering Exchange 2003Clustering Exchange 2003Windows Server 2003Windows Server 2003

Enterprise Edition and Datacenter EditionEnterprise Edition and Datacenter Edition2-node Active/Active2-node Active/ActiveUp to 8-node Active/PassiveUp to 8-node Active/Passive

Exchange Cluster ModelsExchange Cluster Models

Active/Passive is the Active/Passive is the strongly preferredstrongly preferred modelmodelFewer EVS’ than nodesFewer EVS’ than nodes

Must use if more than two nodesMust use if more than two nodes

Active/Active is the Active/Active is the strongly discouragedstrongly discouraged model modelMaximum of two nodes and maximum of two EVS’Maximum of two nodes and maximum of two EVS’

Maximum one RSG per cluster (Maximum one RSG per cluster (824126))

Limits number of concurrent MAPI users per node to 1,900Limits number of concurrent MAPI users per node to 1,900

Limits average CPU utilization on each node to 40%Limits average CPU utilization on each node to 40%

Two instances of store running in one Store.exe process; not Two instances of store running in one Store.exe process; not enough contiguous virtual memory to bring enough contiguous virtual memory to bring resource onlineresource online

Exchange Virtual Server LimitsExchange Virtual Server LimitsWith two nodes, you can have up to two EVS’With two nodes, you can have up to two EVS’With three or more nodes you can have With three or more nodes you can have n-1n-1 where where nn = number of = number of nodes in clusternodes in cluster

Requirements For Requirements For Clustering Exchange 2003Clustering Exchange 2003Requirements For Requirements For Clustering Exchange 2003Clustering Exchange 2003


Active/ActiveActive/ActiveSystem AttendantSystem Attendant

Information StoreInformation Store

POP3, IMAP4, SMTP, HTTPPOP3, IMAP4, SMTP, HTTP

Microsoft Search (full-text indexing)Microsoft Search (full-text indexing)

SMTP and routing group connectorsSMTP and routing group connectors

Active/PassiveActive/PassiveMessage Transfer AgentMessage Transfer Agent

Support For Clustering Support For Clustering Exchange 2003Exchange 2003Support For Clustering Support For Clustering Exchange 2003Exchange 2003

NOT SupportedNOT SupportedActive Directory Connector (ADC)Active Directory Connector (ADC)

Exchange Event ServiceExchange Event Service

Foreign Mail System ConnectorsForeign Mail System Connectors

Network News Transport Protocol (NNTP)Network News Transport Protocol (NNTP)

Site Replication Service (SRS)Site Replication Service (SRS)


Cluster certified hardware onlyCluster certified hardware onlyWindows Server Catalog – Cluster or Geographic Windows Server Catalog – Cluster or Geographic ClusterCluster

http://www.microsoft.com/windows/catalog/server

SCSI, FC or iSCSI external storageSCSI, FC or iSCSI external storage

Identical hardware for all nodesIdentical hardware for all nodes

Microsoft support for Exchange failover clusters (Microsoft support for Exchange failover clusters (810987) OS – 32-bit only) OS – 32-bit onlyWindows Server 2003 Enterprise EditionWindows Server 2003 Enterprise EditionWindows Server 2003 Datacenter EditionWindows Server 2003 Datacenter Edition

Microsoft Distributed Transaction Coordinator (MSDTC) Microsoft Distributed Transaction Coordinator (MSDTC) installed.installed.

Exchange Server 2003 Enterprise EditionExchange Server 2003 Enterprise Edition


http://www.microsoft.com/windows/catalog/server


Design storageDesign storageFour storage group maximum on nodeFour storage group maximum on nodeShared disks must be NTFS/BASIC (Shared disks must be NTFS/BASIC (237853))Use Diskpart to align sectors at storage levelUse Diskpart to align sectors at storage levelUse separate disk resources for logs/databases in EVSUse separate disk resources for logs/databases in EVSUse separate resource group for quorumUse separate resource group for quorumVolume mount points supported on Windows 2003 (Volume mount points supported on Windows 2003 (318458))Some iSCSI (Some iSCSI (839686) and NAS () and NAS (839687) devices are now ) devices are now supported for use with Exchange and Exchange clusterssupported for use with Exchange and Exchange clusters

You cannot use NAS for quorum resource (You cannot use NAS for quorum resource (cluster FAQ))

Additional disk resources need to be added as dependencyAdditional disk resources need to be added as dependency

Building An Exchange Building An Exchange ClusterClusterBuilding An Exchange Building An Exchange ClusterCluster


http://support.microsoft.com/default.aspx?scid=kb;EN-US;318458

http://support.microsoft.com/default.aspx?scid=kb;en-us;839686


http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/clustering/sercsfaq.mspx

Building An Exchange Building An Exchange ClusterClusterBuilding An Exchange Building An Exchange ClusterCluster

Design networkDesign networkUse multiple networks with Use multiple networks with dedicated dedicated private networksprivate networks ( (258750))

Do not use teaming or DHCPDo not use teaming or DHCP ( (254101))

Need an IP address and Network Name Need an IP address and Network Name resource forresource for

Each physical nodeEach physical node

The cluster resource groupThe cluster resource group

Each Exchange Virtual ServerEach Exchange Virtual Server

Use consistent naming standardsUse consistent naming standards



Building An Exchange Building An Exchange ClusterCluster

Step 1 - Prepare HardwareStep 1 - Prepare HardwareApply latest system BIOSApply latest system BIOS

Apply latest device firmwareApply latest device firmware

Gather latest software driversGather latest software drivers

Disable unnecessary hardwareDisable unnecessary hardware

Follow your hardware manufacturer recommendations Follow your hardware manufacturer recommendations

to ensure you are using only drivers or firmware that to ensure you are using only drivers or firmware that

have been tested for clustershave been tested for clusters


Step 2 – Install operating system and other Step 2 – Install operating system and other prerequisitesprerequisites

Install operating system (Windows Server 2003 Install operating system (Windows Server 2003 preferred)preferred)

SMTP, W3SVC and NNTP servicesSMTP, W3SVC and NNTP services

Add nodes to domain as member serversAdd nodes to domain as member serversDomain controllers are not supported for Exchange Domain controllers are not supported for Exchange cluster nodes (cluster nodes (810986))

Windows Support ToolsWindows Support Tools

Windows Update / Security hotfixesWindows Update / Security hotfixes

If 1 GB or more of memory, tune with /3GB and If 1 GB or more of memory, tune with /3GB and /USERVA=3030 in Boot.ini/USERVA=3030 in Boot.ini



Step 3 – Prepare Nodes for Cluster ServiceStep 3 – Prepare Nodes for Cluster ServiceDisable unnecessary servicesDisable unnecessary servicesConfigure NetworksConfigure Networks

Rename connections: Private Network and Public NetworkRename connections: Private Network and Public NetworkDisable NetBIOS and DNS on private (heartbeat) interfaceDisable NetBIOS and DNS on private (heartbeat) interfaceDisable Media Sense on NICs – Hard-code (Disable Media Sense on NICs – Hard-code (258750))Use 10MBs/Half-Duplex if not sure what speed to useUse 10MBs/Half-Duplex if not sure what speed to useGive private network highest binding orderGive private network highest binding orderUnbind MS Client and File and Print on private network and Unbind MS Client and File and Print on private network and bind IP and Network Monitor onlybind IP and Network Monitor only

Create/Select cluster service accountCreate/Select cluster service accountDomain account w/local Administrator rights on each nodeDomain account w/local Administrator rights on each node

Does NOT need Exchange Full Admin roleDoes NOT need Exchange Full Admin role

Create Quorum partition on shared diskCreate Quorum partition on shared disk50MB min; 500MB-1GB recommended50MB min; 500MB-1GB recommended

Create and format additional disks/arraysCreate and format additional disks/arrays



Step 4 – Install Cluster Service on each node.Step 4 – Install Cluster Service on each node.Move TEMP/TMP folder off %Systemroot%Move TEMP/TMP folder off %Systemroot%

Run Run Cluster Diagnostics and Verification Tool

Step 5 – Install Network DTC on each node Step 5 – Install Network DTC on each node (MSKB 817064, 301600)(MSKB 817064, 301600)

Step 6 – Install Exchange 2003Step 6 – Install Exchange 2003Unattended setup not supportedUnattended setup not supported

Binaries installed locally in same location on Binaries installed locally in same location on each nodeeach node

Install one node at a time and reboot each node Install one node at a time and reboot each node when finishedwhen finished

http://www.microsoft.com/downloads/details.aspx?familyid=9d467a69-57ff-4ae7-96ee-b18c4790cffd&displaylang=en


Step 7 – Install Exchange 2003 Service Step 7 – Install Exchange 2003 Service Packs and UpdatesPacks and Updates

Always update one node at a time, then Always update one node at a time, then the EVS via Cluster Administrator (for the EVS via Cluster Administrator (for SP1) SP1) 867624

Step 8 – Create Exchange Virtual Step 8 – Create Exchange Virtual ServerServer

Create Resource GroupCreate Resource GroupDisk ResourceDisk ResourceIP Address ResourceIP Address ResourceNetwork Name ResourceNetwork Name ResourceExchange System Attendant ResourceExchange System Attendant Resource



Step 9 – (Optional) Repeat Step 8 if Step 9 – (Optional) Repeat Step 8 if creating additional EVS’creating additional EVS’Step 10 – Configure EVS resourcesStep 10 – Configure EVS resources

Increase pending time-out on Active/Active Increase pending time-out on Active/Active clustersclustersConfigure Restart and Affect the Group Configure Restart and Affect the Group settingssettings

Configure Information Store and System Configure Information Store and System Attendant resources for 1 restartAttendant resources for 1 restart

Step 11 – Bring resources onlineStep 11 – Bring resources onlineStep 12 – Configure failover and failback Step 12 – Configure failover and failback ((197047))



Prior to Putting into ProductionPrior to Putting into ProductionTest failover policiesTest failover policiesTest hardware (simulate failures)Test hardware (simulate failures)Exchange Server Load Simulator 2003 Exchange Server Load Simulator 2003 (LoadSim)(LoadSim)

Test under heavy network, disk I/O, and services loadsTest under heavy network, disk I/O, and services loadsTest under large number of simultaneous logon Test under large number of simultaneous logon attemptsattemptsClean up after LoadSimClean up after LoadSim

Manually remove everything or flatten cluster and rebuildManually remove everything or flatten cluster and rebuild

Exchange Server 2003 Jetstress 2004 ToolExchange Server 2003 Jetstress 2004 Tool Microsoft Exchange Server Best Practices Microsoft Exchange Server Best Practices Analyzer ToolAnalyzer Toolhttp://www.microsoft.com/exchange/exbpa

http://www.microsoft.com/exchange/exbpa


Additional Best PracticesAdditional Best PracticesDo not install applications into the default Cluster Do not install applications into the default Cluster GroupGroup

Do not delete or rename the default Cluster Do not delete or rename the default Cluster Group or remove any resources from that Group or remove any resources from that resource groupresource group

Do not use APM/ACPI power-saving featuresDo not use APM/ACPI power-saving features

Do not set the Cluster service account to be a Do not set the Cluster service account to be a member of the domain administrator groupmember of the domain administrator group

Turn off cluster event log replication if auditing is Turn off cluster event log replication if auditing is enabled and security logging is heavy, or if you enabled and security logging is heavy, or if you do not want event log entries to be replicated (do not want event log entries to be replicated (224969))


AgendaAgenda





Overview of SQL Server Failover Overview of SQL Server Failover ClusteringClusteringMSDTCMSDTC

ResourcesResources

SQL Server Virtual ServersSQL Server Virtual Servers

Virtual servers: Instances of clustered Virtual servers: Instances of clustered SQL Server serversSQL Server servers

From client/application perspective, the server names or IP From client/application perspective, the server names or IP addresses used for accessaddresses used for access

Cluster resources configured during install of a Cluster resources configured during install of a virtual server:virtual server:

SQL Server IP AddressSQL Server IP Address

SQL Server Network NameSQL Server Network Name

SQL Server (clustered instance of the SQL Server (clustered instance of the SQL Server 2000 service)SQL Server 2000 service)

SQL Server AgentSQL Server Agent

SQL Server FulltextSQL Server Fulltext

SQL Server virtual server administrator account SQL Server virtual server administrator account

SQL Server Cluster TypesSQL Server Cluster Types

Single-Instance ClusterSingle-Instance ClusterOnly one SQL Server virtual server Only one SQL Server virtual server running; Can be a default or running; Can be a default or named instancenamed instanceReplaces term Replaces term active/passiveactive/passive

Multiple-Instance ClusterMultiple-Instance ClusterUp to 16 SQL Server virtual servers are Up to 16 SQL Server virtual servers are supported per server cluster:supported per server cluster:

1 default instance + up to 15 named instances 1 default instance + up to 15 named instances OROR

Up to 16 named instances onlyUp to 16 named instances only

Replaces term Replaces term active/activeactive/active

The Failover ProcessThe Failover Process

Operating-system checksOperating-system checksHeartbeat checks availability of nodes and Heartbeat checks availability of nodes and virtual servervirtual server

SQL Server checksSQL Server checksLooksAlive check runs every five seconds LooksAlive check runs every five seconds IsAlive check runs IsAlive check runs SELECT @@SERVERNAME querySELECT @@SERVERNAME query

Failover to another nodeFailover to another nodeWindows Clustering attempts restart on same Windows Clustering attempts restart on same node or fails over to another nodenode or fails over to another nodeSQL Server service startsSQL Server service startsBrings master onlineBrings master onlineDatabase recovery proceedsDatabase recovery proceedsEnd users and applications must reconnectEnd users and applications must reconnect

Client PCs

Node A Node B

Shared Disk Array

Heartbeat

SQL ServerSQL Server SQL ServerSQL Server

Illustration Of FailoverIllustration Of Failover

Application can keep running; It doesn’t have to be aware of a Application can keep running; It doesn’t have to be aware of a new IP address or server name; Only virtual server fails overnew IP address or server name; Only virtual server fails over

Failover is nearly transparent, except…Failover is nearly transparent, except…SQL goes through a stop/restart and connections are droppedSQL goes through a stop/restart and connections are dropped

Completed transactions in log are rolled forward; Incomplete Completed transactions in log are rolled forward; Incomplete transactions will be rolled back transactions will be rolled back

Plan for and manage failover:Plan for and manage failover:Handle a failover gracefully in code, or have retry logicHandle a failover gracefully in code, or have retry logic

Consider using middleware (MTS/MSMQ/BizTalk) for transactionsConsider using middleware (MTS/MSMQ/BizTalk) for transactions

Use the Clustering API to code cluster-aware applicationsUse the Clustering API to code cluster-aware applications

Non-cluster-aware applications/services may have to be Generic Non-cluster-aware applications/services may have to be Generic Application or Service resourcesApplication or Service resources

Consider the network timeout valueConsider the network timeout value

Failover From A Failover From A Client/Application PerspectiveClient/Application Perspective

Enhancements To Failover Enhancements To Failover Clustering In SQL ServerClustering In SQL Server

SQL Server Setup installs and uninstalls a clusterSQL Server Setup installs and uninstalls a clusterSQL Server failover clustering is a permanent option; SQL Server failover clustering is a permanent option; No unclustering is possible; To remove, you must uninstallNo unclustering is possible; To remove, you must uninstall

Service packs are applied directly to virtual serversService packs are applied directly to virtual servers

SQL Server supports multiple instances and multiple SQL Server supports multiple instances and multiple network addressesnetwork addresses

Extensive support for recovering from a failure Extensive support for recovering from a failure of a server node in the cluster, including a of a server node in the cluster, including a one-node clusterone-node cluster

Number of nodes Number of nodes …continued…continued

Enhancements To Failover Enhancements To Failover Clustering (Continued)Clustering (Continued)

All nodes have local copies of SQL Server tools and All nodes have local copies of SQL Server tools and executablesexecutablesSQL Server failover clustering supports Microsoft SQL Server failover clustering supports Microsoft Search serviceSearch serviceRerunning the Setup program updates failover Rerunning the Setup program updates failover clustering configurationsclustering configurationsSQL Server Service Manager or SQL Server SQL Server Service Manager or SQL Server Enterprise Manager now start and stop Enterprise Manager now start and stop SQL Server servicesSQL Server services

No longer have to use Cluster Administrator to perform No longer have to use Cluster Administrator to perform this taskthis task

Building A SQL 2000 Building A SQL 2000 ClusterCluster

Step 1 - Prepare HardwareStep 1 - Prepare HardwareApply latest system BIOSApply latest system BIOS

Apply latest device firmwareApply latest device firmware

Gather latest software driversGather latest software drivers

Disable unnecessary hardwareDisable unnecessary hardware


Step 2 – Install OS and Pre-ReqsStep 2 – Install OS and Pre-ReqsInstall Windows Server 2003Install Windows Server 2003

Add Nodes to Domain as member serversAdd Nodes to Domain as member serversDCs are not recommended on clustered nodesDCs are not recommended on clustered nodes

Windows Update / Security HotfixesWindows Update / Security Hotfixes

Administration Tools – ADMINPAK.MSIAdministration Tools – ADMINPAK.MSI

Windows Support ToolsWindows Support Tools

Resource Kit ToolsResource Kit Tools


Step 3 – Prepare Nodes for Cluster ServiceStep 3 – Prepare Nodes for Cluster ServiceDisable unnecessary servicesDisable unnecessary services

Configure NetworksConfigure NetworksRename connections: Private Network and Public NetworkRename connections: Private Network and Public Network

Disable NetBIOS and DNS on private (heartbeat) interfaceDisable NetBIOS and DNS on private (heartbeat) interface

Disable Media Sense on NICs – Hard-code (MSKB 258750)Disable Media Sense on NICs – Hard-code (MSKB 258750)

Use 10MBs/Half-Duplex if not sure what speed to useUse 10MBs/Half-Duplex if not sure what speed to use

Give private network highest binding orderGive private network highest binding order

Create/Select cluster service accountCreate/Select cluster service accountDomain account w/local Administrator rights on each nodeDomain account w/local Administrator rights on each node

Create Quorum partition on shared diskCreate Quorum partition on shared disk

50MB min; 500MB-1GB recommended50MB min; 500MB-1GB recommended

Create and format additional disks/arraysCreate and format additional disks/arrays


Step 4 – Install Cluster Service on each node.Step 4 – Install Cluster Service on each node.

Step 5 – Install Network DTC on each node Step 5 – Install Network DTC on each node (MSKB 817064, 301600)(MSKB 817064, 301600)

Step 6 – Install SQL 2000 Virtual InstanceStep 6 – Install SQL 2000 Virtual InstanceBinaries installed locally in same location on Binaries installed locally in same location on each nodeeach node

Installs all nodes at the same time!Installs all nodes at the same time!


Step 7 – Install SQL 2000 Service Pack Step 7 – Install SQL 2000 Service Pack 4 and Updates4 and Updates

Always update all nodesAlways update all nodes

Step 8 – (Optional) Repeat Step 6 if Step 8 – (Optional) Repeat Step 6 if using Multiple Instance modelusing Multiple Instance model

Step 9 – Bring Resources OnlineStep 9 – Bring Resources Online


Best PracticesBest PracticesDo not install applications into the default Cluster Do not install applications into the default Cluster GroupGroup

Do not delete or rename the default Cluster Do not delete or rename the default Cluster Group or remove any resources from that Group or remove any resources from that resource groupresource group

Do not use APM/ACPI power-saving featuresDo not use APM/ACPI power-saving features

Give the Cluster service account full rights to Give the Cluster service account full rights to administer computer objects if Kerberos administer computer objects if Kerberos authentication is enabled for virtual serversauthentication is enabled for virtual servers

Do not set the Cluster service account to be a Do not set the Cluster service account to be a member of the domain administrator groupmember of the domain administrator group

Failover Clustering Failover Clustering SQL Server 2005SQL Server 2005

Further refined in SQL Server 2005Further refined in SQL Server 2005

More nodesMore nodesMatch operating system limitsMatch operating system limits

Unattended setupUnattended setup

Support for mounted volumes (Mount Support for mounted volumes (Mount Points)Points)

All SQL Server services participateAll SQL Server services participateDatabase Engine, SQL Server Agent, Database Engine, SQL Server Agent, Analysis Services, Full-Text Search, etc.Analysis Services, Full-Text Search, etc.

Failover ClusterFailover Cluster

Database MirroringDatabase MirroringNew for SQL Server 2005New for SQL Server 2005Database MirroringDatabase MirroringNew for SQL Server 2005New for SQL Server 2005

InstantInstant Standby Standby

Conceptually a fault-tolerant server Conceptually a fault-tolerant server Building block for complex topologiesBuilding block for complex topologies

Database FailoverDatabase FailoverVery Fast … less than three secondsVery Fast … less than three seconds

Zero data lossZero data loss

Automatic or manual failoverAutomatic or manual failoverAutomatic re-sync after failoverAutomatic re-sync after failover

Automatic, transparent client redirectAutomatic, transparent client redirect

Database MirroringDatabase Mirroring

SQL 2005 Failover Solutions SQL 2005 Failover Solutions At A GlanceAt A Glance

Both ProvideBoth ProvideAutomatic detection and failoverAutomatic detection and failover

Manual failoverManual failover

Transparent client connectTransparent client connect

Zero work lossZero work loss

Database Views mitigate DBA or application errorDatabase Views mitigate DBA or application error

Database MirroringDatabase MirroringDatabase scopeDatabase scope

Standard serversStandard servers

Fastest failoverFastest failover

Limited reporting on standbyLimited reporting on standby

Duplicate copy of databaseDuplicate copy of database

Failover ClusteringFailover ClusteringSystem scopeSystem scope

Certified hardwareCertified hardware

Fast failoverFast failover

No reporting on standbyNo reporting on standby

Single copy of databaseSingle copy of database

AgendaAgenda





Overview of SQL Server Failover Overview of SQL Server Failover ClusteringClustering

MSDTCMSDTCResourcesResources

MSDTC Best PracticesMSDTC Best Practices

Install Network DTC with Windows Install Network DTC with Windows http://support.microsoft.com/kb/817064

Install ClusteringInstall Clustering

Create MSDTC Resource within the cluster Create MSDTC Resource within the cluster http://support.microsoft.com/default.aspx?scid=kb;en-us;301600

Exchange – requires MSDTC for installation Exchange – requires MSDTC for installation and service packs – put into Cluster Groupand service packs – put into Cluster Group

SQL – only required if an application uses it – SQL – only required if an application uses it – Dedicated IP, Network Name, GroupDedicated IP, Network Name, Group

http://support.microsoft.com/kb/817064



AgendaAgenda





Overview of SQL Server Failover Overview of SQL Server Failover ClusteringClustering

MSDTCMSDTC

ResourcesResources

Microsoft Windows Server -Microsoft Windows Server -Clustering MVPClustering MVP

www.nw-america.com – Clustering – Clustering

msmvps.com/clustering - Blog - Blog

https://mvp.support.microsoft.com/https://mvp.support.microsoft.com/profile=EDD23402-0C81-4968-916C-profile=EDD23402-0C81-4968-916C-09D62BBD77F5 – MVP Profile09D62BBD77F5 – MVP Profile

http://www.nw-america.com/

https://mct.team.partners.extranet.microsoft.com/MCT%20Utilities/msmvps.com/clustering

http://www.mvps.org/

ResourcesResourcesClustering newsgroup support – Clustering newsgroup support – msnews.microsoft.commsnews.microsoft.com

Microsoft.public.exchange.clusteringMicrosoft.public.exchange.clustering

Microsoft.public.sqlserver.clusteringMicrosoft.public.sqlserver.clustering

Microsoft.public.windows.server.clusteringMicrosoft.public.windows.server.clusteringWelcome to the Clustering Technologies Welcome to the Clustering Technologies Community Community http://www.microsoft.com/windowsserver2003/comhttp://www.microsoft.com/windowsserver2003/community/centers/clustering/default.mspxmunity/centers/clustering/default.mspxServer Clusters: Network Configuration Best Server Clusters: Network Configuration Best Practices for Windows 2000 and Windows Server Practices for Windows 2000 and Windows Server 2003 2003 http://www.microsoft.com/technet/prodtechnol/windhttp://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/clustering/owsserver2003/technologies/clustering/clstntbp.mspxclstntbp.mspx

ResourcesResources

SQL Server High Availability SQL Server High Availability resources resources http://www.microsoft.com/sql/techinfhttp://www.microsoft.com/sql/techinfo/administration/2000/availability.aspo/administration/2000/availability.aspVisit the SQL Server Web site: Visit the SQL Server Web site: www.microsoft.com/sqlwww.microsoft.com/sqlSQL Server 2000 Failover Clustering SQL Server 2000 Failover Clustering http://www.microsoft.com/technet/prhttp://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/failclus.odtechnol/sql/2000/maintain/failclus.mspxmspx

ResourcesResources

Exchange Server 2003 planning guide:Exchange Server 2003 planning guide:http://www.microsoft.com/technet/prodtechnol/exhttp://www.microsoft.com/technet/prodtechnol/exchange/Exchange2003/proddocs/library/change/Exchange2003/proddocs/library/MessSyst.aspMessSyst.asp

Exchange Server 2003 Deployment Guide:Exchange Server 2003 Deployment Guide:http://www.microsoft.com/technet/prodtechnol/exhttp://www.microsoft.com/technet/prodtechnol/exchange/Exchange2003/proddocs/library/change/Exchange2003/proddocs/library/DepGuide.aspDepGuide.asp

Exchange Server 2003 Technical Exchange Server 2003 Technical Documentation Library:Documentation Library:http://www.microsoft.com/exchange/librarhttp://www.microsoft.com/exchange/library/y/

ResourcesResources

Learn more about Clustering at Learn more about Clustering at TechEdTechEd

Hands On LabsHands On LabsMGT12 Microsoft System Center Data MGT12 Microsoft System Center Data Protection ManagerProtection ManagerSVR15 Clustering with Virtual Server 2005SVR15 Clustering with Virtual Server 2005

Cabana TalksCabana TalksFind me and buy me a drink Find me and buy me a drink

Community ResourcesCommunity ResourcesAttend a free chat or web castAttend a free chat or web casthttp://www.microsoft.com/communities/chats/default.mspx http://www.microsoft.com/communities/chats/default.mspx http://www.microsoft.com/usa/webcasts/default.asp http://www.microsoft.com/usa/webcasts/default.asp

List of newsgroupsList of newsgroupshttp://communities2.microsoft.com/http://communities2.microsoft.com/communities/newsgroups/en-us/default.aspx communities/newsgroups/en-us/default.aspx

MS Community SitesMS Community Siteshttp://www.microsoft.com/communities/default.mspxhttp://www.microsoft.com/communities/default.mspx

Locate Local User GroupsLocate Local User Groupshttp://www.microsoft.com/communities/usergroups/http://www.microsoft.com/communities/usergroups/default.mspxdefault.mspx

Community sitesCommunity siteshttp://www.microsoft.com/communities/related/default.mspxhttp://www.microsoft.com/communities/related/default.mspx

Where To Learn MoreWhere To Learn MoreOther Tech Ed Sessions:Other Tech Ed Sessions:

BAP200 Microsoft Business Solutions-Great BAP200 Microsoft Business Solutions-Great Plains: Maximizing Your Hardware and Plains: Maximizing Your Hardware and Network InfrastructureNetwork Infrastructure

CSI448 Optimizing Scalability, Performance CSI448 Optimizing Scalability, Performance and Availability with Systems Built on and Availability with Systems Built on the .NET Frameworkthe .NET Framework

DBA308 Ensuring Business Continuance DBA308 Ensuring Business Continuance with SQL Server 2005 Data Availability with SQL Server 2005 Data Availability SolutionsSolutions

MGT315 Update Management and Desktop MGT315 Update Management and Desktop Deployment at MicrosoftDeployment at Microsoft

MSG300 Exchange 2003 Architecture Best MSG300 Exchange 2003 Architecture Best PracticesPractices

Where To Learn MoreWhere To Learn MoreOther Tech Ed Sessions:Other Tech Ed Sessions:

MSG360 Microsoft IT: Exchange Best MSG360 Microsoft IT: Exchange Best Practices from Microsoft ITPractices from Microsoft IT

MSG383 Exchange Server 2003 Cluster MSG383 Exchange Server 2003 Cluster Best PracticesBest Practices

PRT375 SharePoint Products and PRT375 SharePoint Products and Technologies: Performance and Technologies: Performance and Capacity Planning Best Practices and Capacity Planning Best Practices and Lessons LearnedLessons Learned

SVR308 Introducing Windows Server SVR308 Introducing Windows Server 2003, Compute Cluster Edition2003, Compute Cluster Edition

Your FeedbackYour Feedbackis Important!is Important!

Please Fill Out a Survey forPlease Fill Out a Survey forThis Session on CommNetThis Session on CommNet

© 2005 Microsoft Corporation. All rights reserved.This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

Technology

Clustering and High Availability