7/27/2019 20417A_07.pdf

1/40

MicrosoftJump Start

M7: Implementing FailoverClustering

Rick Claus | Technical Evangelist | MicrosoftEd Liberman | Technical Trainer | Train Signal

7/27/2019 20417A_07.pdf

2/40

Meet Rick Claus

Microsoft Technical Evangelist Developer & Platform Evangelism (DPE) Windows Server, core infrastructure

Engages worldwide technical community

More than 20 years IT experience, 7+ w/ Microsoft Enterprise consulting, core infrastructure services,

Virtualization technologies of all kinds, systemsmanagement, deployments

Design & architecture for government, financialinstitutions, SMB

Infrastructure design and architecture, implementation,roll-out

@RicksterCDN

7/27/2019 20417A_07.pdf

3/40

Meet Ed Liberman

Technical Trainer & MVP, Train Signal Teaching style that encourages people tohave fun while they learn

Prepares students to pass exams while helping themdevelop the skills needed to succeed in the real world

In technology for 20 years, instructor since 1998 Has helped thousands get started or advance their

careers in the IT industry

When not in classroom, helping corporations withnetwork infrastructure as an independent consultant

Ed also volunteers in as a math tutor for strugglinggrade school children in his local community

@TrainSignal_Ed

7/27/2019 20417A_07.pdf

4/40

Jump Start Expectations

Tailored for Windows Server Experts

Fast-paced

Lots of real-world explanations and demos

Assumes experience with Windows Server

You are curious about technology and want tolearn MORE!

7/27/2019 20417A_07.pdf

5/40

Assumed Knowledge

Extensive knowledge of Windows Server 2008 / R2

Some knowledge of Windows Server 2012

Install and Config experience

Basics of Active Directory, sites, trusts, & topology

DNS & related technologies

Some Windows PowerShell 2.0

Virtualization experience

Day to day management experience

7/27/2019 20417A_07.pdf

6/40

Course 20417A

This Jump Start is an accelerated version of a five-day course Course 20417A: Upgrading Your Skills to MCSA

Windows Server 2012

For deeper hands-on experience, take thefollowing course from a Learning Partner http://www.microsoft.com/learning/en/us/Course.aspx?I

D=20417A&Locale=en-us

http://www.microsoft.com/learning/en/us/Course.aspx?ID=20417A&Locale=en-ushttp://www.microsoft.com/learning/en/us/Course.aspx?ID=20417A&Locale=en-ushttp://www.microsoft.com/learning/en/us/Course.aspx?ID=20417A&Locale=en-ushttp://www.microsoft.com/learning/en/us/Course.aspx?ID=20417A&Locale=en-ushttp://www.microsoft.com/learning/en/us/Course.aspx?ID=20417A&Locale=en-ushttp://www.microsoft.com/learning/en/us/Course.aspx?ID=20417A&Locale=en-ushttp://www.microsoft.com/learning/en/us/Course.aspx?ID=20417A&Locale=en-ushttp://www.microsoft.com/learning/en/us/Course.aspx?ID=20417A&Locale=en-us

7/27/2019 20417A_07.pdf

7/40

Jump Start Target Agenda | Day One

Day 1 Day 2

Module 1: Installing and ConfiguringServers Based on Windows Server2012

Module 7: Implementing FailoverClustering

Module 2: Monitoring andMaintaining Windows Server 2012

Module 8: Implementing Hyper-V

Module 3: Managing Windows Server2012 by Using PowerShell 3.0

Module 9: Implementing FailoverClustering with Hyper-V

- MEAL BREAK - - MEAL BREAK -

Module 4: Managing Storage forWindows Server 2012

Module 10: Implementing DynamicAccess Control

Module 5: Implementing NetworkServices

Module 11: Implementing ActiveDirectory Domain Services

Module 6: Implementing Direct Access Module 12: Implementing ActiveDirectory Federation Services

7/27/2019 20417A_07.pdf

8/40

Module Overview

Overview of Failover Clustering

Implementing a Failover Cluster

Configuring Highly-Available Applications andServices on a Failover Cluster

Maintaining a Failover Cluster

Implementing a Multi-Site Failover Cluster

7/27/2019 20417A_07.pdf

9/40

What Is Availability?

Availability is a level of service expressed as apercentage of time

Highly-available services or systems are availablemore than 99 percent of the time

High availability requirements differ based on howavailability is measured

Planned outages typically are not included when

calculating availability

7/27/2019 20417A_07.pdf

10/40

Failover Clustering Improvements

The improvements in Failover Clustering in Windows Server2012 include:

Increased scalability

Improved CSVs

Cluster-Aware Updating

Active Directory integration improvements

Management improvements

Cluster.exe command-line tool, Cluster Automation Server(MSClus) COM interface, and Add-ClusterPrintServerRolecmdlet are some of the removed features in Windows Server2012

7/27/2019 20417A_07.pdf

11/40

Failover Cluster Components

Node 1 Node 2

Cluster storage

Clients

Service orapplication

A dedicated networkconnects the failover

cluster nodes

A network connects

the failover clusterand clients

Shared bus or

iSCSI connection

7/27/2019 20417A_07.pdf

12/40

What Are Failover and Failback?

During failover, clustered instance and allassociated resources moved from one node toanother

Failover occurs when:

The node that currently hosts the instance becomesinactive for any reason

One of the resources within the instance fails

An administrator forces a failover

Cluster service can failback after the offline nodebecomes active again

7/27/2019 20417A_07.pdf

13/40

Failover Cluster Networks

One network can support both client and nodecommunications

Multiple network cards are recommended toprovide enhanced performance and redundancy

Network Description

Public network Clients use this network to connect to

the clustered servicePrivate network Nodes use this network to

communicate with each other

Public-and-

private network

Required to communicate with

external storage systems

7/27/2019 20417A_07.pdf

14/40

Failover Cluster Storage

Failover clusters require shared storage to provideconsistent data to a virtual server after failover

Shared storage options include: SAS

iSCSI Fibre channel

7/27/2019 20417A_07.pdf

15/40

What Is Quorum?

In failover clusters, quorum defines the consensusthat enough cluster members are available toprovide services

Quorum:

Is based on votes in Windows Server 2008 Allows nodes, file shares, or a shared disk to have a

vote, depending on the quorum mode

Allows the failover cluster to remain online whensufficient votes are available

7/27/2019 20417A_07.pdf

16/40

Quorum Modes in Windows Server 2012 FailoverClustering

QuorumMode

What Has the Vote? When Is QuorumMaintained?

NodeMajority

Only nodes in thecluster have a vote

Quorum is maintainedwhen more than half ofthe nodes are online

Node andDiskMajority

The nodes in the clusterand a disk witness havea vote

Quorum is maintainedwhen more than half ofthe votes are online

Node andFile Share

Majority

The nodes in the clusterand a file share witness

have a vote

Quorum is maintainedwhen more than half of

the votes are onlineNoMajority:Disk Only

Only the quorum-shared disk has a vote

Quorum is maintainedwhen the shared disk isonline

7/27/2019 20417A_07.pdf

17/40

What Are Cluster Shared Volumes?

The benefits of CSVs include:

Fewer LUNs required

Better use of disk space

Resources in a single logical location

No special hardware required Increased resiliency

To implement CSV:

1. Create and format volumes on shared storage

2. Add the disks to failover cluster storage

3. Add the storage to the CSV

7/27/2019 20417A_07.pdf

18/40

Preparing for Implementing Failover Clustering

Use failover clustering when:

High availability is required

Scalability is not required

Application is stateful

Client automatically reconnects to the application

Application uses IP-based protocols

H d R i F il Cl

7/27/2019 20417A_07.pdf

19/40

Hardware Requirements: Failover ClusterImplementation

Server hardware components must be markedwith the Certified for Windows Server 2012 logo

Server nodes should all have the sameconfiguration and contain the same or similar

components All tests in the Validate a Configuration Wizardmust be passed

N t k R i t F il Cl t

7/27/2019 20417A_07.pdf

20/40

Network Requirements: Failover ClusterImplementation

Network hardware components must be markedwith the Certified for Windows Server 2012 logo

The server should be connected to multiplenetworks for communication redundancy, or to a

single network with redundant hardware, toremove single points of failure

The network adapters should be identical andhave the same IP protocol versions, speed, duplex,and flow control capabilities

7/27/2019 20417A_07.pdf

21/40

Infrastructure Requirements for Failover Cluster

Nodes in cluster must use DNS name resolution

All servers in the cluster must be in the sameActive Directory domain

User account that creates the cluster must have

administrator rights and permissions on allservers, and the Create Computer Objectspermission in the domain

Failover cluster infrastructure recommendations: The same roles should be installed on each cluster node The AD DS role should not be installed on any of the

cluster nodes

S ft R i t F il Cl t

7/27/2019 20417A_07.pdf

22/40

Software Requirements: Failover ClusterImplementation

All nodes must run the same edition of WindowsServer 2012, which can be any of the following: Windows Server 2012 Enterprise, Full or Server Core

installation

Windows Server 2012 Datacenter, Full or Server Coreinstallation

All nodes must run the same processorarchitecture (32-bit, x64-based, or Itanium

architecture-based) All nodes should have the same service pack andupdates

7/27/2019 20417A_07.pdf

23/40

DEMO: Validating and Configuring a Failover Cluster

In this demonstration, you will validate andconfigure a cluster

7/27/2019 20417A_07.pdf

24/40

Identifying Cluster Resources and Services

Clustered services: Are services or applications that are made highly

available by installing them on a failover cluster

Active on one node, but can be moved to another node

Resources: Are the components that make up a clustered service

Are moved to another node when one node fails

Can only run on one node at a time

Include components such as shared disks, names, and IPaddresses

7/27/2019 20417A_07.pdf

25/40

The Process for Clustering Server Roles

1. Install the failover clustering feature

2. Verify the configuration and create a cluster

3. Install the role on all cluster nodes, using ServerManager

4. Create a clustered application by using the FailoverClustering Management snap-in

5. Configure the application

6. Test the failover

7/27/2019 20417A_07.pdf

26/40

DEMO: Clustering a File Server Role

In this demonstration, you will cluster a file server role

7/27/2019 20417A_07.pdf

27/40

Failover Cluster Management Tasks

Managing nodes

Managing networks

Managing permissions

Configuring cluster quorum settings

Migrating services and applications to a cluster

Configuring new services and applications

Removing the cluster

7/27/2019 20417A_07.pdf

28/40

Managing Cluster Nodes

To manage cluster nodes, you can:

Add nodes after you create a cluster

Pause nodes, which prevents resources from

running on that node

Evict nodes from a cluster, which removes the nodefrom the cluster configuration

All of these actions are available in the Failover ClusterManagement Actions pane

7/27/2019 20417A_07.pdf

29/40

Configuring Application Failover Settings

Considerations for using preferred owners include: Preferred owners are set on the clustered application

Multiple preferred owners can be set in an ordered list

Setting preferred owners gives control over: Order in which an application will select a node to run on

Applications that can be run on the same nodes in anActive/Active configuration

Options to modify failover and failback settings:

Setting the number of times the cluster service willrestart a clustered application in a set period of time

Setting or preventing failback of the clusteredapplication to the preferred node when it becomesavailable

7/27/2019 20417A_07.pdf

30/40

Tools for Monitoring Failover Clusters

Event Viewer

Tracerpt.exe

Performance and Reliability Monitor snap-in

MHTML-formatted cluster configuration reports

Validate a Configuration Wizard

Backing Up & Restoring Failover Cluster

7/27/2019 20417A_07.pdf

31/40

Backing Up & Restoring Failover ClusterConfiguration

When backing up failover clusters, keep in mind Windows Server Backup is Windows Server 2012 feature

You install Windows Server Backup as a feature

Backup and restore operations involve the VolumeShadow Copy Service (VSS)

Third-party tools available to perform backups/restores

You must perform system-state backups

A non-authoritative restore completely restores a

single node in the cluster An authoritative restore restores the entire clusterconfiguration to a point in time

7/27/2019 20417A_07.pdf

32/40

Troubleshooting Failover Clusters

Reviewing events in logs (cluster, hardware,storage)

Use the Validate a Configuration Wizard

Define process for troubleshooting failover

clusters Review storage configuration

Check for group and resource failures

7/27/2019 20417A_07.pdf

33/40

What Is Cluster-Aware Updating?

Cluster-Aware Updating is an automated feature, specific to

Windows Server 2012, that updates nodes in a cluster withminimal or zero downtime

Cluster-Aware Updating can work in two modes:

Remote-Updating Mode

Self-Updating Mode

7/27/2019 20417A_07.pdf

34/40

DEMO: Configuring Cluster-Aware Updating

In this demonstration, you will configure Cluster-Aware

Updating

7/27/2019 20417A_07.pdf

35/40

What Is a Multi-Site Cluster?

A multi-site cluster is a cluster that has been extended so

that different nodes in the same cluster reside in separatephysical locations

Site A Site B

SAN SAN

7/27/2019 20417A_07.pdf

36/40

Synchronous and Asynchronous Replication

In synchronous replication, host receives a write complete response from the

primary storage after the data is written successfully to both storage locations

In asynchronous replication, the host receives a write complete response fromthe primary storage after the data is written successfully on the primary storage

Primary

Storage

SecondaryStorage

WriteRequest

WriteComplete

Replication

Data Data

Site A Site B

f

7/27/2019 20417A_07.pdf

37/40

Choosing a Quorum Mode for Multi-Site Clusters

When designing automatic failover forgeographically-dispersed clusters:

Use Node Majority or Node Majority with File

Share quorum Use three locations to allow automatic failover of asingle virtual server: All three locations must be linked directly to each other

One location is only a file-share witness

h ll f l i l i i l

7/27/2019 20417A_07.pdf

38/40

Challenges for Implementing a Multi-Site Cluster

Storage Challenge Description

Requires a separateor third-party datareplication solution

Hardware (block level) storage-based replication Software (file system level) host-based replication

Application-based replication (such as Exchange 2007Cluster Continuous Replication)

Can be eithersynchronous or

asynchronousreplication

Synchronous. No acknowledgement of data changes madein Site A until the data is successfully written to Site B

Asynchronous. Data changes made in Site A will eventuallybe written to the storage in Site B

Inter-node communications are time sensitive; you mightneed to configure these thresholds to meet the higher WAN

latency DNS replication might impact client reconnect times when

failover is based on hostname

Some applications might require all of the nodes to be in the

same Active Directory site

Active Directory replication latency might effect applicationdata availability

D l i C id i f M l i Si Cl

7/27/2019 20417A_07.pdf

39/40

Deploying Considerations for a Multi-Site Cluster

Ensure that the business requirements are met bythe solution

Use a hardware vendor to create a full solution formulti-site clusters

Choose the correct quorum mode to properlymaintain functionality in the event of failures

Choose the correct storage replication solution to

meet these needs

7/27/2019 20417A_07.pdf

40/40