Windows Server 2008 Building High Availability Infrastructures

8/7/2019 Windows Server 2008 Building High Availability Infrastructures

1/39

Windows Server 2008

High Availability

Ramnish SinghIT AdvisorMicrosoft Corporation


2/39

Agenda

Failover ClustersNetwork Load Balancing


3/39


4/39

Overview

Windows Server 2008failover cluster changes

What is a failovercluster?

Benefits of a failovercluster

Failover clustercomponents


5/39

New Features

SimplicityCluster managementand operations

Setup and migration

Stability

Maximizing availability

Storage configurationand management

Security Improvement tonetworking and security


6/39

Improvements to Setup

A new stream-lined Cluster Setup wizard for one stepcluster installation.

Fully scriptable cluster installation and configuration

Capture and apply resource group settings fromWindows Server 2003 server clusters to WindowsServer 2008 Server failover clusters

Simulated clustered actions to test cluster capability

Node tests

Network tests

Storage tests


7/39

Improvements to Cluster Managementand Operations

Quickly add clustered resources

Command line (cluster.exe) and WMI clustermanagement

Troubleshoot a cluster with Windows EventTracing

New, simplified, task-oriented clusteradministrator MMC snap-in

Backup cluster configuration data with theVolume Shadow Copy Service

Better control of Shared folders


8/39

Improvements to Storage Configurationand Management

Fibre Channel, iSCSI, and SAS storage support

Better storage performance and stability, largerthan 2TB partitions

Perform disk maintenance more easily

On-line hot-add of disks to other clusterapplication

Perform disk maintenance more easily


9/39

Improvements to Security

Cluster access auditing

Kerberos only authentication, no NTLM

Enhanced encryption

Cluster Service runs under the LocalSystem eliminating theneed for the Cluster Service Account (CSA)


10/39

Improvements to Networking

Name resolution without NETBios for DNS onlynetworks

Support for DHCP assigned cluster IP addressand heartbeat IP addresses

Support for IPv6 on production and privatenetworks

No more single subnet limit, routable clustercommunication


11/39

Technical Background

Cluster Migrations

Cluster Validation Tool

Failover Cluster Requirements

Cluster Administrator

Maximizing Availability

Geographically DispersedFailover Clusters

Cluster Configuration


12/39

Maximizing Availability

Up to 16 nodes in a cluster with x-64 edition ofWindows Server 2008 Server

Majority-based cluster membershipWho and what gets a vote is fullyconfigurable

4 quorum models

Witness Disk QuorumMajority Quorum (Shared Disk)

Majority Node Set Quorum

Shared Witness Quorum hybrid of Majority

Node Set and Shared Disk


13/39

Witness Disk Quorum Model

SAN

Node 1 Node 2

Shared Storage

Device is masterVote

Only the Disk gets a voteLegacy quorum model

Nodes have no vote quorum disk is the master

Cluster stays up even if only 1 node can talk to thedisk


14/39

Majority Quorum Model

SAN

Node 1 Node 2

Shared Storage

Device gets 1

vote

VoteVote

Vote

Each node

counts as 1 vote

New majority-based quorum modelDisk is optional witness to have a vote in decidingmajority

3 total votes, with 2 needed for majority

The Cluster can survive the loss of any 1 vote


15/39

Majority of Nodes Quorum Model

Node 3Node 1 Node 2

VoteVote

Vote

Replicated Storage Devices

Only Nodes get votes

3+ Node votes without Shared Storage vote

Majority of votes needed to operate cluster

No shared disk vote


16/39

Shared Witness Quorum Model

File Share on an

independent server

VoteVote

Witness

Each nodecounts as 1 vote

Node 1 Node 2

Allows a cluster with no shared disk (hybrid of Majorityof Nodes + Witness Based Quorum)

Improved from Windows Server 2003 to support greaterthan 2 nodes

Excellent solution for GeoCluster (file share in a 3rd site)

Single server could serve as the witness for multipleclusters


17/39

Geographically Dispersed Failover Clusters

Routable and configurable heartbeats ease thecreation of geographically dispersed failover clusters.

Witness

Site1

Site2

Site

3


18/39

Failover Cluster Requirements

Access by each node to a shared storage device (fibre

channel, iSCSI, SAS) for clusters with shared data needs

Operating system: Windows Server 2008 Enterprise orDatacenter Edition

Multiple network adapters on each node, connected todifferent IP subnets (production and heartbeat)


19/39

Cluster Migrations

Capture and apply resource group settings froma Windows Server 2003 server cluster to a

Windows Server 2008 failover cluster

Cluster Migration Tool facilitates migration of acluster using a roll forward model

FailoverClusteringServerClustering


20/39

Cluster Configuration Validation Wizard(ClusPrep v.2)

Identifies hardware and configuration problemsprior to releasing a cluster into a productionenvironment

Runs a focused set of tests on cluster nodes,networks, and storage to verify the feasibility ofinstalling a cluster on a set of servers

Can be used as adiagnostic tool

Required for Microsoftsupport


21/39

Cluster Node Inventory and Validation

Inventory:Operating systemversions

Hot fix and servicepack consistency

CPU architectureMemory

Domain membership

Unsigned driverinstallations

PnP devices

Host Bus Adapters(HBAs) and networkadapters

Validation:

Communication betweencluster nodes

SCSI reservationcompatibility among

cluster nodesPresence of multiplenetwork adapters in eachnode and configurationof valid IP addresses

Accessibility of sharedstorage device by eachcluster node

Network and diskinput/output


22/39

Cluster Setup


23/39

Cluster Administrator

The new, simplified, task-based management consoleService and application based administration


24/39

Configuring Highly-Available Resources


25/39

Failover Cluster Events, Logs, and Reports

HTML Based for EasyCollection and RemoteAnalysis


26/39

Command-Line Configuration(Cluster.exe)

Cluster.exe facilitates automation of clusteradministration through scripting

Sample syntax:

- To add a node to the cluster, type:Cluster /add /node:TPA-NODE-01

- To evict a node from the cluster, type:Cluster NODE TPA-NODE-01 /EVICT

- To manually fail over a resource, type:

Cluster GROUP ClusterFS /move:tpa-node-01


27/39

Implementation/Usage Scenarios

Failover clusters are used for servers that runapplications with a shared data set. For example SQLServer 2005, Exchange Server 2007, Microsoft OfficeSharepoint Server 2007, and File and Print Services.


28/39

Failover Clustering


29/39

Recommendations

Validate cluster node hardwareMinimize the services installed on cluster nodes

Ensure the physical security of cluster nodes

Implement consistent security practices to detect and

prevent irregular and unwanted communication to clusternodes

Ensure the security of network services that a failovercluster relies on (Active Directory, DNS, DHCP)

Test and install the latest hot fixes and service packs on

cluster nodesAdminister cluster nodes only from trusted computers


30/39

Summary

Enhanced cluster validation with the Cluster ConfigurationValidation Wizard

Simplified installation procedures and task-based managementwith a new Cluster Administrator MMC snap-in

Increased cluster node support on x64 edition Windows Server

2008 ServerNew Witness disk architecture

Enhanced IP addressing features (IPv6, DHCP)

Elimination of VLAN requirement with routable clustercommunication

Elimination of NetBIOS dependency

Support for fibre channel, iSCSI, and SAS storage architectures


31/39


32/39

Overview

Support for IPv6

Support for NDIS 6.0

WMI Enhancements

Improved DOS attack and time starvation protection

Support for multiple dedicated IP addresses per node

Support for rolling upgrades

Consolidated management through Network LoadBalancing Manager


33/39

Technical Details

NLB is an optional feature, which must be installed inone of three ways:

Server Manager (GUI)

Ocsetup.exe (command line)

Unattended answer file with setup.exe during OSinstallation

NLB can be used to load balance a Terminal Server farm

TS Session Directory keeps track of disconnected sessions

and ensures that users are reconnected to those sessionsHost must be in same subnet

Servers must be in same domain


34/39

Implementation/Usage Scenarios

Ensure high availability for services andapplications

Ensure scalability for services and

applications

Provide highly-available Terminal Servicessessions


35/39

Recommendations

Implement NLB to provide high availabilityand scalability to services and applications

Use only the TCP/IP network protocol onthe cluster adapter

Do not enable Network Load Balancing on acomputer that is part of a failover cluster

Secure the load balanced applications and

hostsSecure the network traffic between nodes


36/39

Summary

NLB provides high availability and scalability for servicesand applications

NLB now provides support for IPv6, NDIS 6.0, multiplededicated IP addresses per node, rolling upgrades, andconsolidated management through the Network Load

Balancing Manager. Also provided are enhancements toWMI and improved protection against Denial of Server(DOS) attacks.

3 Installation options: Server Manager, ocsetup, andduring an unattended installation of the operating system

NLB can provide highly-available terminal servicessessions


37/39

ResourcesWindows Server 2008Product: http://www.microsoft.com/windowsserver2008/audsel.mspx

Home Page: http://www.microsoft.com/windowsserver/Windows Server 2008/default.mspx

Webcasts: http://www.microsoft.com/events/series/windowsserver2008.aspx?tab=webcasts

Forums: http://forums.microsoft.com/TechNet/default.aspx?ForumGroupID=161&SiteID=17

Failover ClusteringWeb Page: http://www.microsoft.com/windowsserver/Windows Server 2008/failover-clusters.mspx

Blog: http://blogs.msdn.com/clustering/archive/2006/10/26/welcome-to-cluster-teams-blog.aspx

Presentation: http://download.microsoft.com/download/5/b/9/5b97017b-e28a-4bae-ba48-

174cf47d23cd/SER119_WH06.ppt

Webcast:

http://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?EventID=1032325410&EventCategory=5&culture=en-US&CountryCode=US

Forum: http://forums.microsoft.com/TechNet/ShowForum.aspx?ForumID=827&SiteID=17
http://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?EventID=1032325410&EventCategory=5&culture=en-US&CountryCode=UShttp://blogs.msdn.com/clustering/archive/2006/10/26/welcome-to-cluster-teams-blog.aspx


38/39


39/39

2007 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 presentati on. 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

Documents

Windows Server 2008 Building High Availability Infrastructures