site b site a sansansansan

31

Upload: alfred-fields

Post on 23-Dec-2015

224 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Site B Site A SANSANSANSAN
Page 2: Site B Site A SANSANSANSAN

Windows Server 2012 Failover Cluster Disaster RecoveryAlex PubanzSenior Premier Field EngineerMicrosoft Australia

MDC-B355

Page 3: Site B Site A SANSANSANSAN

Agenda

• Cluster Definition and Benefits• Multi-Site Cluster• The Paxos Tag• Restoring a failover cluster from

backup• Cluster Name Object (CNO)

Recovery• Replacing a shared disk• Quorum Recovery

Page 4: Site B Site A SANSANSANSAN

Cluster Definition and Benefits

Page 5: Site B Site A SANSANSANSAN

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

Failover Cluster Workloads include:• Hyper-V• File/Print • SQL• Exchange• and more

Page 6: Site B Site A SANSANSANSAN

Multi-Site Cluster

Page 7: Site B Site A SANSANSANSAN

Benefits of a Multi-Site Cluster

• Protects against loss of an entire location

• Automates failover• Reduced downtime• Lower complexity disaster recovery plan

Site BSite A

SANSAN

But what about deleted or corrupted cluster configuration in the clusdb or Active Directory?

Page 8: Site B Site A SANSANSANSAN

The Paxos Tag

Page 9: Site B Site A SANSANSANSAN

The Paxos Tag

• Consists of 3 numbers separated by a colon

• Stored in HKLM\Cluster• Provides the guarantee of

consistency across the cluster nodes and witness disk

• Used to guarantee data consistency when updates are propagated.

• Can be used to verify if an authoritative restore of the clusdb occurred

Page 10: Site B Site A SANSANSANSAN

The Paxos Tag – What makes it update?• Paxos Tag changes during the following

conditions:• Epoch - Every time a cluster is formed• Sequence - Every time there is an update to the

configuration of the cluster

• Sync process sends out proposal to all nodes in the cluster• Consists of Proposal Number and Sequence Number.• Nodes check local config (registry) to see if sequence

is higher or lower than current proposal• If the node has a lower number then the proposal the

Node sends out acceptance of the proposal• If a majority of the nodes in the cluster (a consensus)

send back acceptance the data is incorporated locally.

Page 11: Site B Site A SANSANSANSAN

The Paxos Tag – What makes it change?• Format can change in the following two

scenarios• Authoritative Restore of the cluster is executed• When the cluster is started using the /forcequorum

switch (/FQ)

date/time format example after an authoritative restore:2013/05/27-15`35`55.889_4:2013/05/27-15`35`55.889_4:294

Page 12: Site B Site A SANSANSANSAN

Restoring a failover cluster from backup

Page 13: Site B Site A SANSANSANSAN

Auth- vs. Non-Authoritative Restore

Non-Authoritative RestoreRestores the node to normal function, but is not rolling back the cluster configuration• used when a damaged cluster node needs to be restored to normal function

Authoritative RestoreRestores the cluster configuration to the configuration stored in the backup• used when deleted or corrupt cluster configuration needs to be

restored

Page 14: Site B Site A SANSANSANSAN

DEMO

BMR restore after a full cluster meltdown using Windows RE and System Center DPM 2012 SP1

Page 15: Site B Site A SANSANSANSAN

DEMO

Authoritative Restore using Windows Server Backup

Page 16: Site B Site A SANSANSANSAN

Cluster Name Object (CNO) Recovery

Page 17: Site B Site A SANSANSANSAN

Cluster Name Object (CNO) Recovery• CNO is the ‘common identity’

for a Failover Cluster and stored in AD

• The CNO creates all other Network Name resources that are created in a Failover Cluster as part of a Client Access Point (CAP)

• The CNO is responsible for synchronizing the domain password for each Virtual Computer Object (VCO) it created

Page 18: Site B Site A SANSANSANSAN

Demo

Recovering a deleted Cluster Name Object (CNO) and Virtual Computer Objects (VCO) in Active Directory

Page 19: Site B Site A SANSANSANSAN

Replacing a shared disk

Page 20: Site B Site A SANSANSANSAN

Replacing a Shared Disk• Enable Disk Maintenance Mode on (failed) disk to suspend all

Basic\Thorough health checks and all Persistent Reservation processes

• Attach a new disk• Online and initialize the disk is disk management (MBR or

GPT)• Create a new volume • Format as either FAT32, NTFS or ReFS (depending on

requirements)• Right-click the disk resource in Failover Cluster Manager,

‘More actions…’, ‘Repair’. This will launch the ‘Repair a Disk Resource’ window.• Bring the new resource online• Copy/restore data to the new drive

Page 21: Site B Site A SANSANSANSAN

Demo

Failover Cluster Manager’s built in ‘repair’ disk functionality

Page 22: Site B Site A SANSANSANSAN

Quorum Recovery

Page 23: Site B Site A SANSANSANSAN

The Four Quorum Models• Default model when you create a cluster without storage

• Recommended model when your cluster has an odd number of nodes

Node Majority• Default model when you create a cluster with

storage (and at least one disk with an NTFS file system)

• \Cluster folder will be created which contains a complete copy of the cluster registry HIVE HKLM\Cluster

• Recommended when you have an even number of nodes

Node and Disk Majority

• Needs to be configured manually• Connection to a SMB network share required• FSW contains log file with Paxos tag information

Node and File Share Majority

• Manual configuration required• Single point of failure• Useful when the majority of cluster nodes is not

available (hardware failure?)

No MajorityDisk Only

Page 24: Site B Site A SANSANSANSAN

Demo

Recovering a failed file share witness quorum resource

Page 25: Site B Site A SANSANSANSAN

AppendixMicrosoft Premier Proactive ServicesCSRES – Cluster Server Recovery Execution Service (ask your TAM about it!)http://download.microsoft.com/documents/australia/services/datasheets2012/Cluster Service Recovery Execution Service (CSRES).pdf

Understanding Backup and Recovery Basics for a Failover Clusterhttp://technet.microsoft.com/en-us/library/cc771973.aspx

Recovering a Deleted Cluster Name Object (CNO) in a Windows Server 2008 Failover Clusterhttp://blogs.technet.com/b/askcore/archive/2009/04/27/recovering-a-deleted-cluster-name-object-cno-in-a-windows-server-2008-failover-cluster.aspx

SC 2012 SP1 – DPM: Leveraging DPM ScaleOut feature to protect VMs deployed on a big clusterhttp://blogs.technet.com/b/dpm/archive/2013/05/01/sc-2012-sp1-dpm-leveraging-dpm-scaleout-feature-to-protect-vms-deployed-on-a-big-cluster.aspx

Page 26: Site B Site A SANSANSANSAN

Related contentMDC-B337 Failover Cluster Networking EssentialsMDC-B336 Cluster in a Box in 2013: How Real Customers Are Making Their Businesses Highly-Available with Windows Server 2012Find Me Later At...

Page 27: Site B Site A SANSANSANSAN

Track resourcesLearn more about Windows Server 2012 R2 Preview, download the datasheet and evaluation bits on http://aka.ms/WS2012R2Learn more about System Center 2012 R2 Preview, download the datasheet and evaluation bits on http://aka.ms/SC2012R2

Page 28: Site B Site A SANSANSANSAN

msdn

Resources for Developers

http://microsoft.com/msdn

Learning

Microsoft Certification & Training Resources

www.microsoft.com/learning

TechNet

Resources

Sessions on Demand

http://channel9.msdn.com/Events/TechEd

Resources for IT Professionals

http://microsoft.com/technet

Page 29: Site B Site A SANSANSANSAN

Complete an evaluation on CommNet and enter to win!

Page 30: Site B Site A SANSANSANSAN

Evaluate this session

Scan this QR code to evaluate this session and be automatically entered in a drawing to win a prize

Page 31: Site B Site A SANSANSANSAN

© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows 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.