© 2012 Microsoft Corporation. All rights reserved.saharapcc.skills4success.co/spcc/it/ws2012/Module...

Microsoft Confidential

© 2012 Microsoft Corporation. All rights reserved.

Windows Server 2012 Failover Clustering

Module 1: Introduction


Conditions and Terms of Use

This training package is proprietary and confidential, and is intended only for uses described in the training materials. Content and software

is provided to you under a Non-Disclosure Agreement and cannot be distributed. Copying or disclosing all or any portion of the content

and/or software included in such packages is strictly prohibited.

The contents of this package are for informational and training purposes only and are provided "as is" without warranty of any kind,

whether express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, and non-

infringement.

Training package content, including URLs and other Internet Web site references, is subject to change without notice. Because Microsoft

must respond to changing market conditions, the content should not be interpreted to be a commitment on the part of Microsoft, and

Microsoft cannot guarantee the accuracy of any information presented after the date of publication. Unless otherwise noted, the companies,

organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious, and no

association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should

be inferred.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this

document. Except as expressly provided in written license agreement from Microsoft, the furnishing of this document does not give you any

license to these patents, trademarks, copyrights, or other intellectual property.

Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this

document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic,

mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.

For more information, see Use of Microsoft Copyrighted Content at

http://www.microsoft.com/about/legal/permissions/

Microsoft®, Internet Explorer®, and Windows® are either registered trademarks or trademarks of Microsoft Corporation in the United

States and/or other countries. Other Microsoft products mentioned herein may be either registered trademarks or trademarks of Microsoft

Corporation in the United States and/or other countries. All other trademarks are property of their respective owners.

Copyright and Trademarks © 2012 Microsoft Corporation. All rights reserved.


http://www.microsoft.com/about/legal/permissions/

What You Will Learn

After completing this module, you will be familiar with the

following:

High availability with Windows Server 2012

Failover clustering history and concepts

Creating a Windows Server 2012 Failover Cluster

What's new in Windows Server 2012

Microsoft Confidential3

Failover Cluster Fundamentals

High availability with Windows Server 2012

Failover clustering history and concepts

Creating a Windows Server 2012 Failover Cluster


High Availability With Windows Server 2012

Most service level agreements do not allow for much

downtime

High availability technologies are designed to ensure

minimal downtime

Windows Server 2012 was designed for high availability at

every layer


History of Clustering

Microsoft Confidential 6

Operating System Nodes Storage Bus

Windows NT 4.0 Enterprise Edition

Windows 2000, Advanced Server

Windows 2000, Datacenter Edition

Windows Server 2003, Enterprise Edition

Windows Server 2003, Datacenter Edition

1-2 SCSI

Windows NT 4.0 Enterprise Edition

Windows 2000, Advanced Server

1-2 Fibre Channel

Windows 2000, Datacenter Edition 1-4 Fibre Channel

Windows Server 2003, Enterprise Edition, x86/x64/IA64

Windows Server 2003, Datacenter Edition, x86/x64/IA64

Windows Server 2008, Enterprise Edition, x86/x64/IA64

Windows Server 2008, Datacenter Edition, x86/x64/IA64

1-8

(1-16 when x64)

(1-16 when x64)

Fibre Channel,

iSCSI or SAS

Windows Server 2008R2, Enterprise x64 Edition

Windows Server 2008R2, Datacenter x64 Edition

1-16 Fibre Channel,

iSCSI or SAS

Windows Server 2012, All Editions 1-64 Fibre Channel,

iSCSI or SAS

Cluster Definition and Benefits

A cluster is a group of independent servers that function as

a single system

Clusters are managed as a single unit

Benefits:

High Availability

Scalability

Reduced Total Cost of Ownership


Cluster Definition and Benefits, Continued


Failover Clustering Requirements

Hardware must be logo’d

Successful validation


Installing Failover Cluster Feature

Install remotely

Use Server Manager

Windows PowerShell


Validation

Validates the hardware configuration to determine

suitability for clustering

This is half of your supportability statement

Recommended to run before and after creating a cluster


Creating a Failover Cluster

Create a cluster using Failover Cluster Manager or Windows

PowerShell (New-Cluster)

Can use a Distinguished Name format to place CNO in

specific Organizational Unit

Example: CN=2012Cluster,OU=Clusters,DC=Demo,DC=Local

Cluster objects follow cluster nodes in Active Directory

containers

Unless you pre-stage them


Testing A Failover Cluster

Cluster validation after cluster has been built

Manually test your Failover Cluster:

Simulate failure action

Drain nodes

Switch off a node to simulate a power failure


Lab 1: Create Your Cluster

Time: 1 hour


High Availability Vs. Fault Tolerance

A Windows Failover Cluster provides high availability,

NOT fault tolerance

If it was a fault tolerant system – what would never happen

again?


Shared Nothing Model and CSV

Physical Disk resources and can be online on only one

node at a time (Shared Nothing model)

Cluster Shared Volumes allow access to a volume by all

nodes in a cluster at the same time


Groups and Resources

Resources are the smallest entities in a failover cluster

Resources are put together into Resource Groups

Only Resource Groups can move between nodes


Resource Dependencies

Resource dependencies control the online and offline order

of those resources

Resources can be dependent on multiple resources in the

same resource group

Example:

If a Network Name depends on an IP Address, and that IP Address

fails, the Network Name will fail as well


Automated Failover of Resources

Resource Monitor tracks resource state with resource

specific tests:

Basic Health Check (LooksAlive)

Thorough Health Check (IsAlive)

First failure triggers a restart of the resource by default

By default, if second restart does not work, the Resource

Group is moved to another node


Windows Server 2012 Failover Behavior


RESOURCE GROUP

on Node 1

RESOURCE GROUP’s

Preferred Owners list:

Node 1

Node 3

Node 2

Scenario Group with

Preferred Owners

Group without

Preferred Owners

Node

Failure

Group is moved to

the next node in

its failover list,

which consists of

the preferred

owners + group’s

unique order list.

In this case the

next candidate

node would be

Node 3.

Group is moved to a

node with the fewest

groups.

Triggered

Group

Failover

Group is moved to

the next node in its

unique failover list.

AntiAffinityClassNames could be used to identify groups

that shouldn’t be hosted on the same node.

When guest role is a Hyper-V virtual machine and no preferred owners list is set, the

workload is placed depending on nodes’ available resources (primarily memory).

What’s New in Windows Server 2012

New features in Failover Clustering

Microsoft Confidential - For Internal Use Only22

New Features in Failover Clustering

Improved Scalability

Enhanced Hyper-V Integration

Cluster-Aware Updating

New and improved Cluster Validation Tests


New Features in Failover Clustering, Continued

Cluster storage improvements

Quorum model improvements

Task scheduler integration

Cluster networking improvements


New Features in Failover Clustering, Continued

Resource Hosting Subsystem improvements

Usability improvements

Security


Module Review Questions

Other than passing Cluster Validation without errors, what

requirement is there regarding the Failover Cluster

hardware?

Where does the Cluster Name Object get created in your

Active Directory?

Which two resource specific tests does the Resource

Monitor run against all cluster resources?

What is the new Quorum-feature in a Windows Server

2012 Failover Cluster?

Can you name a Cluster storage improvement?


Questions?

Microsoft Confidential 6/4/201231

© 2012 Microsoft Corporation. All rights reserved.saharapcc.skills4success.co/spcc/it/ws2012/Module...

Documents

Transcript of © 2012 Microsoft Corporation. All rights reserved.saharapcc.skills4success.co/spcc/it/ws2012/Module...