70-412 Chapter 3: Configuring Failover Clustering In Windows Server 2012

Front 1

the goal is for System Administrators to provide services for their users with no downtime with a redundancy solution called Failover Clustering

Back 1

High Availability (Continuous Availability)

Front 2

enables us to drill through a Hyper-V server, into the VM, into the guest 0S, down to the service level and receive alerts that arise up to the host, when errors occur.

Back 2

VM Monitoring

Front 3

• What is Failover Clustering?

Back 3

This isn’t a Microsoft concept; Failover clustering is intrinsically tied to High availability

Front 4

is a service level for a given app or service (Workload);

Back 4

High Availability (HA)

Front 5

is a contract between a network service provider and a customer that specifies, usually in measurable terms, what services the network service provider will furnish

Back 5

SLA(Service Level Agreement)

Front 6

HA method that protects a given services or app from downtime.

Back 6

Failover Clustering

Front 7

refers to the automatic transition of these highly available resources, when a node goes offline

Back 7

Failover

Front 8

means whenever “Node A” comes back online, we want the resources that were failovered to “Node B”, now to come back over “Node A”

Back 8

Failback

Front 9

simply refers to a server (physical server) that is participating in a failover cluster

Back 9

Node

Front 10

this configuration is where we have a one designated node that owns particular resources(roles) and any other nodes in the cluster are “passive-and they?

Back 10

Active/Passive configuration

The passive nodes receive those workloads(services or applications) in the event of a failover.

Front 11

situation, where we have work coming in from our user connections actually being handle by more than one node in the cluster.

Back 11

Active/Active configuration

Front 12

• Failover Clustering Improvements in Windows Server 2012

Back 12

-More scalability: Each cluster can now have up to 64 nodes/4000 VMs (virtual per cluster….Server 2008 only had 16 nodes & 1000 VMS per cluster
-*CSVs (Cluster Shared Volume)-these were introduced in 2K8 R2 strictly for the Hyper-V workload; Now we can also use them for “File Sharing Services”
-Has a new version of server message block(SMB3.0)
-SOFS(Scale-Out File Server)
-Cluster-Aware Updating (CAU)
-Cluster.exe is deprecated and replace with PowerShell v3

Front 13

- a way to provide fault tolerant file shares

Back 13

SOFS

Front 14

allows us to configure a cluster to update itself with no downtime

Back 14

Cluster-Aware Updating (CAU)

Front 15

`refers a piece or segment of your storage area network

Back 15

LUN (Logical Unit Number)

Front 16

`How do CSVs benefit Administrators?

Back 16

-Historically, if you need to failover a VM from Host 1 to Host 2, it would require un-mounting and re-mounting LUNs, because one LUN can only be mounted by one cluster node at a time

-The outcome: Failing over a VM resource, meant failing over the entire LUN, which involves downtime for anything else that happens to be on that LUN as well.

-*CSVs: enable multiple clustered nodes to access a single LUN concurrently, and doesn't require unmounting and remounting the LUN.

Front 17

What are the additional benefits of using a Cluster Shared Volume?

Back 17

With this storage, every node in the cluster has a simultaneous connection to the same LUN

This method doesn’t require spawning a drive letter, CSVs actually show up as local mounts on the c:\ drive of each node (server).

each VM that is hosted on Node 1, has a slice of the CSV, which means if we want to live migrate both or just one of the VMs to Node2, we won’t have to un-mount and re-mount the entire LUN and halt and other resources(apps, services, or VMs)

Front 18

allows you to put shared folders in the CSV as well with same local mount point on your nodes( c:\), which makes the share online and available, even if an node that owned it goes offline.

Back 18

Scale-Up File Server

Front 19

refers to a minimum number/quantity required to get some work done; Ex: In a business meeting, we could say we have 10 people that need to be at the meeting, but the quorum is only 6; In a cluster, this represents the # of nodes/elements required to keep the cluster online

Back 19

Quorum

Front 20

can be a node but can also be the share storage, arbitrary file share that gets a vote in the quorum

Back 20

Elements

Front 21

QUORUM TYPE:

Only your cluster nodes have a vote in quorum, and you have more than half voting, stating yes we’re online, the cluster continues; this is used when you have an odd # off nodes

Back 21

Node Majority

Front 22

QUORUM TYPE:

Used if we have an even number of nodes;and your shared storage serves as an voting member (disk witness)-serves as a tie-breaker in quorum voting

Back 22

Node and Disk Majority

Front 23

QUORUM TYPE:

uses an arbitrary file share, so if the file share is only it votes yes and serves as the tie-breaker, which is also optimized for an even # of nodes

Back 23

Node and File Share Majority

Front 24

QUORUM TYPE:

where you are so concerned with keeping the cluster online on-line, you are willing to go the last node standing, still requires connectivity to the shared disk.

Back 24

No Majority

Front 25

What does the CAU ( Cluster Aware Updating) accomplish

Back 25

transparently, one-by-one takes a node offline, drains any roles to another node
-Applies updates (WSUS or Microsoft Update), reboot if necessary
-Comes back online and automatically claims all of its hosted roles
-Updates moves to the next node in the cluster, and follows the same procedure

Front 26

Failover Cluster CMDLETS

Make a new disk available for use in a failover cluster. The disk (LUN) must be exposed to all nodes in the failover cluster, and should not be exposed to any other servers.

Back 26

Add-ClusterDisk

Front 27

Failover Cluster CMDLETS

Create a clustered file server (resource group that includes one or more disks, on which you can create shared folders for users).

Back 27

Add-ClusterFileServerRole

Front 28

Failover Cluster CMDLETS

Configure high availability for an application that was not originally designed to run in a failover cluster.

Back 28

Add-ClusterGenericApplicationRole

Front 29

Failover Cluster CMDLETS

Configure an application controlled by a script that runs in Windows Script Host, within a failover cluster.

Back 29

Add-ClusterGenericScriptRole

Front 30

Failover Cluster CMDLETS

Configure high availability for a service that was not originally designed to run in a failover cluster.

Back 30

Add-ClusterGenericServiceRole

Front 31

Failover Cluster CMDLETS

Add an empty resource group to the failover cluster configuration, in preparation for adding clustered resources to the group.

Back 31

Add-ClusterGroup

Front 32

Failover Cluster CMDLETS

Add a node (server) to a failover cluster. Before adding the new node, you should run validation tests on the existing nodes together with the proposed new node.

Back 32

Add-ClusterNode

Front 33

Failover Cluster CMDLETS

Create a clustered print server (a resource group that includes a printer and a disk for storing print job information and printer drivers).

Back 33

Add-ClusterPrintServerRole

Front 34

Failover Cluster CMDLETS

Add a resource to a clustered service or application (resource group) in a failover cluster.

Back 34

Add-ClusterResource

Front 35

Failover Cluster CMDLETS

Add a resource to the list of resources that a particular resource depends on (using AND as the connector) within a failover cluster. Existing dependencies will remain in the list.

Back 35

Add-ClusterResourceDependency

Front 36

Failover Cluster CMDLETS

Add a resource type to a failover cluster, and specify information such as the dynamic-link library (DLL) to use with that resource type.

Back 36

Add-ClusterResourceType

Front 37

Failover Cluster CMDLETS

Add a group containing only a client access point and storage to the failover cluster configuration.

Back 37

Add-ClusterServerRole

Front 38

Failover Cluster CMDLETS


Make a volume available in Cluster Shared Volumes in a failover cluster.

Back 38

Add-ClusterSharedVolume

Front 39

Failover Cluster CMDLETS

Create a clustered virtual machine, that is, a virtual machine that can be failed over if necessary to a different server in the failover cluster.

Back 39

Add-ClusterVirtualMachineRole

Front 40

Failover Cluster CMDLETS

Prevent the specified user or users from accessing a failover cluster.

Back 40

Block-ClusterAccess

Front 41

Failover Cluster CMDLETS

Clear the persistent reservation on a disk in a failover cluster.

Back 41

Clear-ClusterDiskReservation`

Front 42

Failover Cluster CMDLETS

Clear the cluster configuration from a node that was evicted from a failover cluster.

Back 42

Clear-ClusterNode

Front 43

Failover Cluster CMDLETS

Get information about permissions that control access to a failover cluster.

Back 43

Get-ClusterAccess

Front 44

Failover Cluster CMDLETS

Get information about the disks that can support failover clustering and are visible to all nodes, but are not yet part of the set of clustered disks.

Back 44

Get-ClusterAvailableDisk

Front 45

Failover Cluster CMDLETS

Create a log file for all nodes (or a specific node) in a failover cluster.

Back 45

Get-ClusterLog

Front 46

Failover Cluster CMDLETS

Get information about one or more networks in a failover cluster.

Back 46

Get-ClusterNetwork

Front 47

Failover Cluster CMDLETS

Get information about one or more network adapters in a failover cluster.

Back 47

Get-ClusterNetworkInterface

Front 48

Failover Cluster CMDLETS

Move a clustered resource from one clustered service or application to another within a failover cluster.

Back 48

Move-ClusterResource

Front 49

Failover Cluster CMDLETS

Move a Cluster Shared Volume to ownership by a different node in a failover cluster.

Back 49

Move-ClusterSharedVolume

Front 50

Failover Cluster CMDLETS

Move the ownership of a clustered virtual machine to a different node.

Back 50

Move-ClusterVirtualMachineRole

Front 51

Failover Cluster CMDLETS

Control specific properties of an object in a failover cluster, such as a resource, a group, or a network.

Back 51

Set-ClusterParameter

Front 52

Failover Cluster CMDLETS

Run validation tests for failover cluster hardware and settings. Tests can be run both before and after a cluster is set up.

Back 52

Test-Cluster

Front 53

Failover Cluster CMDLETS

Simulate a failure of a cluster resource.

Back 53

Test-ClusterResourceFailure

Front 54

Failover Cluster CMDLETS

Renew or release the DHCP lease for an IP address resource in a failover cluster.

Back 54

Update-ClusterIPResource

Front 55

Failover Cluster CMDLETS

Refresh the configuration of a clustered virtual machine within a failover cluster.

Back 55

Update-ClusterVirtualMachineConfiguration

Front 56

Cmdlet that installs the ISCI Target Role Service

Back 56

Install-WindowsFeature FS-ISCSITarget-Server

Front 57

Cmdlet that creates a virtual ISsi volume

Back 57

New-ISCSIVirtualDisk

Front 58

Cmdlet that creates the iSCSI Target that will use to allow access to iSCSI virtual disks(volumes)

Back 58

New-iSCSIServerTarget -Targetname Cluster1 -InitiatorIDs dnsname:server.domain.com