SVR317 The Best-of-the-Best Practices for Microsoft Clustering, and a Few You Haven't Heard of – But Should

2. SVR317The Best-of-the-Best Practices for Microsoft Clustering, and a Few You Haven't Heard of – But Should Rodney R. Fournier Microsoft MVP - Windows Server - Clustering www.clusterhelp.com – rod@clusterhelp.com www.nw-america.com – rod@nw-america.com

3. Agenda • High Availability • Hardware • Operating System • Cluster Service • Microsoft DTC • Application Support • Virtual Server Host Clustering • Microsoft Cluster Configuration Validation Tool • Windows Server Code name “Longhorn”

4. High Availability • Risk Audit • Identify risks to application • Provide mitigation proposals • Compare risks to costs to mitigate • Examples: Hardware failures, Power, Weather, Theft • Service Level Management • Service Level Agreements (SLAs) • Operating Level Agreements (OLAs)

5. Buy the Right Hardware • Ask your preferred vendor for help • Get guarantees! • Purchase support agreements that align with availability needs Purchase support agreements that align with availability needs • Remember a PSS contract, too! • Hardware that supports Unique ID’s • Ensure all nodes are identical • Same HBA model • Disk drives revisions • Availability requirements, budget, 8th & 9th layer

6. Hardware Considerations • Buy systems from the Windows Server Catalog: Cluster Solution – Hardware 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 components

7. Hardware Considerations • Uninterruptible power supply (UPS) • Generator • Fault tolerant hardware components (dual power, fans) in each node • Apply latest system BIOS, device firmware and drivers • Check with hardware manufacturer first to ensure latest versions have been tested • Use Storport mini-port

8. Server Cluster Topology Client PCs Public Network Private Network Cluster Nodes Redundant Fibre Channel Switched Fabric Shared Disk Storage

9. RAID Arrays • LUN is the smallest unit of failover in a cluster • Create multiple LUNs with 1 partition on each • Partitions are treated as disks and lumped together • Mount points are fully supported and maybe required • Use the right RAID for the support level you require • Master Boot Record (MBR) • Basic Disk • Formatted as NTFS • Label all volumes with a meaningful name (example - Quorum)

10. Shared Disk • Create Quorum partition on shared disk • 500 MB - 2 GB recommended • Dedicated Logical Unit Number (LUN) • Cluster disks • Shared –Share nothing model • Separate disk controller • Fibre Channel • iSCSI • Parallel-SCSI • SAS • RAID • Hardware - always • Software - never

11. Fibre Channel vs. iSCSI • Storage blocks • Full iSCSI support after SP1 or later

12. Zoning • Configure Once • Updates Dynamically • Overlapping Zones – isolate clusters through zoning • Arbitrated Loop forSmall Implementations (1 cluster limit, 2 nodes) • Switched Fabric for Large Implementations JBOD Blue zone Fibre Channel Fabric Array Server Tape system Green zone Red zone

13. Configure Networks • Rename connections: Private Network and Public Network (heartbeat) • Public • Teaming is supported on the Public network, configure each connection to different switches • Put on top of binding order • Private • Disable NetBIOS and DNS on Private Network • Use 10 MBs/Half-Duplex unless vendor says otherwise • Give highest priority order in Cluster Administrator • Bind TCP/IP and Network Monitor (if installed) only • Do not use teaming

14. Operating System • Operating configuration • Windows Server 2003 Enterprise, Windows Server 2003 Datacenter, or R2 of either • Add Nodes to Domain as member servers • DCs are not recommended (and in some cases, not supported) on clustered nodes • Install Windows Support Tools • Install Resource Kit Tools – Several cluster tools included • Use cluster aware Monitoring software like Microsoft Operations Manager 2005 (MOM 2005)

15. Operating System Configuration • Service packs – SP1 is a strong recommendation • Disable unnecessary services • Patches • 895092 Recommended hotfixes for Windows Server 2003-based server clustershttp://support.microsoft.com/default.aspx?scid=kb;EN-US;895092 • Drivers • Anti-virus support • Exclude the Quorum • Exclude SQL or Exchange Databases and data • User Mode Hang Detection • 815267 How to enable User Mode Hang Detection on a server cluster in Windows Server 2003 and in Windows 2000 Server SP4 http://support.microsoft.com/default.aspx?scid=kb;EN-US;815267

16. Cluster Service Account • Properties • 6 rights see 269229 How to manually re-create the Cluster service account http://support.microsoft.com/?id=269229 • Restrict logon location in Active Directory to the cluster nodes • Password settings – per your security guidelines • Local administrator on every node • Group Policy Objects can adversely affect your cluster, put each node in a dedicated Organizational Unit • Regular Domain User account • Never apply Application permissions • Windows 2003 domain recommended

17. Cluster Service • Do not install applications into the default Cluster Group • Do not delete or rename the default Cluster Group or remove any resources from that resource group • Do not set the Cluster service account to be a member of the domain administrator group • Turn off cluster event log replication if auditing is enabled and security logging is heavy, or if you do not want event log entries to be replicated (224969) • DNS - required • WINS – not required, and should not to be used if following security best practices

18. Microsoft DTC • Install Network DTC with Windows http://support.microsoft.com/kb/817064 • Install Clustering • Create MSDTC Resource within the cluster http://support.microsoft.com/default.aspx?scid=kb;en-us;301600 • Exchange Server – requires MSDTC for installation and service packs – put into Cluster Group. Also, no DTC network access needed • Applications that use work flows could require a dedicated group • SQL Server – only required if an application uses it – and the create a Dedicated IP, Network Name, and Group

19. Application Support • Sharing • Normal File Share • Dynamic File Share • User Home Folder Share • Distributed File Share – stand alone (DFS) • Volume Shadow Service • Printer • Generic • Application • Service • Script • DHCP • WINS • MSMQ or Microsoft DTC (mutually exclusive) • Exchange Server 2003 • SQL Server Cluster 2000/2005 Failover

20. Clustering Exchange Server 2003 • Exchange Server cluster models • Active/Passive is the strongly preferredmodel • Fewer EVS’ than nodes • Must use if more than two nodes • Active/Active is the strongly discouraged model • Maximum of two nodes and maximum of two EVS’ • Maximum one RSG per cluster (824126) • Limits number of concurrent MAPI users per node to 1,900 • Limits average CPU utilization on each node to 40% • Two instances of store running in one Store.exe process; not enough contiguous virtual memory to bring resource online • Exchange Server Virtual Server Limits • With two nodes, you can have up to two EVS’ • With three or more nodes you can have n-1 where n = number of nodes in cluster

21. SQL Server Cluster Failover Types • Instance replaces term active/active • Single-instance cluster • Only one SQL Server virtual server running; Can be a default or named instance • Replaces term active/passive • Multiple-instance cluster • Up to 16 SQL Server virtual servers are supported per server cluster: • 1 default instance + up to 15 named instances OR • Up to 16 named instances only • Patch/Service Pack the default instance first

22. Virtual Server Host Clustering Virtual machine Guests failover from one node to another (script required http://technet2.microsoft.com/WindowsServer/en/Library/9a3de6d0-c820-41ac-860c-de950d271f8d1033.mspx?mfr=true) Guest VM’s can run any OS Hosts are clustered Guests are not clustered Virtual Server is a clustered application running on a cluster .VHD’s reside on shared disk

23. Virtual Server Guest Clustering Applications failover from one Guest to another Guests run Windows Server 2003 Guests are clustered Hosts are not clustered .VHD’s reside on host disk Guests are effectively nodes in a cluster that access shared storage with a NIC and the iSCSI Software Initiator User data resides on shared disk

24. Microsoft Cluster Configuration Validation Wizarda.k.a. ClusPrep

25. Configuration Issues Cabling mistakes SP and Hotfix binaries Driver mismatches Inconsistent Settings Complexity Best Practices Supportability Requirements Hardware Compatibility 48% of Cluster support calls are due to configuration problems -Microsoft PSS 80% of failures are due to human error -Gartner Motivation for ClusPrep If we can eliminate the configuration issues up front, we can ensure a better cluster experience (installation and operation)

26. What Is ClusPrep? • Runs a focused set of tests on a collection of servers that are intended to be a cluster • When executed on a configured cluster it will do a software inventory, perform network testing, validate system configuration • Plan for next version is to be able to validate existing clusters • Catch hardware or configuration problems before the cluster goes in production • Ensures that the solution you are about to deploy is rock solid • Currently in Beta • Planned to be provided as a free download from microsoft.com • Cluster Prep is not public yet – But you can join the beta by sending a message to clspbeta@microsoft.com

27. Same OS version And version that supports clustering Same QFE and SP level What Does ClusPrep Inventory? OS Binary Consistency CPU architecture Memory information Architecture Domain membership and role Analysis of unsigned drivers Configuration PnP device inventory HBA’s and NIC’s Devices

28. Inter-node communication SCSI reserve/release, reservation breaking and reservation defense What Does ClusPrep Validate? Infrastructure Multiple NIC’s per server Shared disks accessible from all machines and uniquely identifiable Hardware Each NIC has different IP address on a dissimilar subnet Software Network and Disk I/O latencies Failover simulation Functionality

29. XML Based for Easy Collection and Remote Analysis Hyperlinks to Testing Details Flags Test Results Easy Web Browser Interface

30. Planned Features for Windows Server code name “Longhorn” • Biggest changes yet – more then any previous release! • Lots of great storage features • Easy to setup, configure and manage clusters • Addresses a long list of special configuration considerations • Install and play with Beta 2 – Today (after this session) • Send comments and feedback • Use the newsgroups • The more feedback we get now, the better the final product will be

31. Microsoft Windows Server -Clustering MVP • www.ClusterHelp.Com – Cluster Training • www.nw-america.com – Clustering • msmvps.com/clustering - Blog • https://mvp.support.microsoft.com/profile=EDD23402-0C81-4968-916C-09D62BBD77F5 – MVP Profile

32. Resources • Clustering newsgroup support – msnews.microsoft.com • Microsoft.public.exchange.clustering • Microsoft.public.sqlserver.clustering • Microsoft.public.windows.server.clustering • Welcome to the Clustering Technologies Community http://www.microsoft.com/windowsserver2003/community/centers/clustering/default.mspx • Server Clusters: Network Configuration Best Practices for Windows 2000 and Windows Server 2003 http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/clustering/clstntbp.mspx

33. Resources • Clustering Windows Server 2003 and SQL Server 2000/2005 http://www.microsoft.com/technet/community/events/windows2003srv/tnt1-150.mspx • SQL Server 2005 Mission Critical High Availability http://www.microsoft.com/technet/prodtechnol/sql/themes/high-availability.mspx • Visit the SQL Server Web site: www.microsoft.com/sql

34. Resources • Exchange Server 2003 planning guide:http://www.microsoft.com/technet/prodtechnol/exchange/Exchange2003/proddocs/library/MessSyst.asp • Exchange Server 2003 Deployment Guide:http://www.microsoft.com/technet/prodtechnol/exchange/Exchange2003/proddocs/library/DepGuide.asp • Exchange Server 2003 Technical Documentation Library:http://www.microsoft.com/exchange/library/

35. Resources

36. Fill out a session evaluation on CommNet for a chance to Win an XBOX 360!

37. © 2006 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.