Professional Documents
Culture Documents
High Availability With Windows Server 2008: Failover Clustering
High Availability With Windows Server 2008: Failover Clustering
Why is HA Important?
Server downtime is unavoidable Keep your business running and competitive
Update
Hot Fix, Security Patch
Failover Clustering
2+ machines (nodes) Redundancy everywhere
Storage, NICs, HBAs, MPIO, etc.
Shared storage accessible by all nodes 1 node will host a HA application Application writes data to storage
Failover Clustering
Nodes monitor health of other nodes If that node fails, health monitoring will cause a failover of the resource Another node starts the application and reads the last saved information from the storage Clients experience a slight interruption in service
Shared Storage
Terminology Changes
Beta 1997 2000 2003 2008 R2
Software Requirements
Clustering comes as an in-box feature on:
Windows Server 2008 Datacenter Windows Server 2008 Enterprise Windows Server 2008 for Itanium-Based Systems Windows Unified Data Storage Server Enterprise
Architecture:
x64: up to 16 nodes x86: up to 8 nodes IA64: up to 8 nodes
10
11
3 Networks
Public Private (heartbeat) Storage / iSCSI
HA Roles
Validated by Microsoft Failover Cluster Configuration Program More information: http://www.microsoft.com/windowsserver2008/ en/us/clustering-program.aspx
14
Clustering Storage
Windows Server 2008/R2 Supported Shared Bus Types:
Fibre Channel iSCSI SAS
SCSI-3 SPC-3 compliant SCSI Commands Persistent Reservations (PRs) Parallel-SCSI deprecated in 2008 Multipath IO (MPIO) recommended Basic GPT and MBR disks supported
15
Networking
Key clustering component
Public network clients Private network cluster communication Storage network nodes access shared storage
Multiple networks for added redundancy Integrated with new TCP/IP Stack Full IPv6 Support DHCP Support for IPv4 and IPv6 Resources Nodes can reside in different subnets
16
17
18
19
Validating a Cluster
For Microsoft support, cluster must pass the built-in Validate a Cluster Configuration (Validate) test Run during configuration and/or after deployment Series of end-to-end tests on all cluster components Configuration info for support and documentation Networking issues Troubleshoot in-production clusters More information http://go.microsoft.com/fwlink/?LinkID=119949
20
Validate Inventories
OS Binary Consistency
Architecture
Same OS version And version that supports clustering Same Hotfix and Service Pack level
Configuration
Devices
21
Validate Verifies
Infrastructure
Inter-node communication SCSI compatibility with Persistent Reservations
Hardware
Software
Multiple NICs per server Shared disks accessible from all machines and uniquely identifiable
Functionality
22
Software Configuration
1. Install Windows Server 2008 2. Install Failover Clustering feature on each node
If necessary: install highly available workload
3. Open the Failover Cluster Management 4. Run Validate a Cluster Configuration 5. Run Create a Cluster Wizard 6.
23
Creating a Cluster
24
25
HA Workloads
The resources, services, roles, features and application you want HA Resource Group
Application-specific DLL Network Name IP Address Physical Disk Resource
Most in-box server roles Extensible model with 3rd party apps
26
Other
DFS-Namespace DFS-Replication (R2) DHCP DTC iSNS MSMQ NFS Remote Desktop (R2) WINS Other Server
Generic Containers
Generic Application Generic Script Generic Service
3rd Party
Many different roles
27
Standalone host 1
29
Standalone host 2
VMs
VMs
30
Physical Cluster 1
Virtual Cluster 2
Physical Cluster 2
HA Resources
31
32
SCVMM
33
Less need to service cluster stays online longer Can still manage with GUI using Remote Server Administrator Tools (RSAT) > Start /w ocsetup FailoverCluster-Core
34
Multi-Site Clustering
Nodes in different physical locations Unlimited distance Disaster recovery Survive the loss of an entire datacenter Storage at both sites with replication Also known as: geographically dispersed or stretched clustering
35
Summary
Server downtime is inevitable Failover Clustering keeps your apps running and recovers from disasters Buy certified solutions or reuse hardware Validate simplifies troubleshooting Cluster and HA workloads are easy to create Make almost anything HA Multiple management options
36
37
Resources
Seattle Windows Networking User Group: http://www.winnetusergroup.com Cluster Team Blog: http://blogs.msdn.com/clustering/ Cluster Information Portal: http://www.microsoft.com/windowsserver2008/en/us/clustering-home.aspx Clustering Technical Resources: http://www.microsoft.com/windowsserver2008/en/us/clustering-resources.aspx Clustering Forums: http://forums.technet.microsoft.com/enUS/winserverClustering/threads/ Clustering Newsgroup: https://www.microsoft.com/technet/community/newsgroups/dgbrowser/enus/default.mspx?dg=microsoft.public.windows.server.clustering Failover Clustering Deployment Guide: http://technet.microsoft.com/enus/library/dd197477.aspx TechNet: Configure a Service or Application for High Availability: http://technet.microsoft.com/en-us/library/cc732478.aspx TechNet: Installing a Failover Cluster: http://technet.microsoft.com/enus/library/cc772178.aspx TechNet: Creating a Failover Cluster: http://technet.microsoft.com/enus/library/cc755009.aspx Webcast: TechNet Webcast: Failover Clustering 101 Webcast: TechNet Webcast: Build High-Availability Infrastructures with Windows Server 2008 Failover Clustering
38
2008 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.
39