Exchange 2013 Haute disponibilité et tolérance aux sinistres (Session 2/2 deuxième partie)

Infrastructure, communication & collaboration

Exchange Server 2013

High Availability and Site Resilience (2/2)

Scott SchnollSenior Content Developer

Microsoft Corporation

scott.schnoll@microsoft.comhttp://aka.ms/Schnoll

Twitter: @Schnoll

#mstechdays Infrastructure, communication & collaboration

• DAG Architecture• Witness Server

Agenda – Part 1

#mstechdays Infrastructure, communication & collaboration

• Dynamic Quorum• DAG member maintenance

Agenda – Part 2

Infrastructure, communication & collaboration

#mstechdays

DYNAMIC QUORUM

#mstechdays Infrastructure, communication & collaboration

• In Windows Server 2008 R2, quorum majority is fixed, based on the initial cluster configuration

• In Windows Server 2012 (and later), cluster quorum majority is determined by the set of nodes that are active members of the cluster at a given time

• This new feature is called Dynamic Quorum, and it is enabled for all clusters by default

Dynamic Quorum

#mstechdays Infrastructure, communication & collaboration

• Cluster dynamically manages vote assignment to nodes, based on the state of each node– When a node shuts down or crashes, the node loses its

quorum vote– When a node rejoins the cluster, it regains its quorum vote

• By adjusting the assignment of quorum votes, the cluster can dynamically increase or decrease the number of quorum votes required to keep running

Dynamic Quorum

#mstechdays Infrastructure, communication & collaboration

• By dynamically adjusting the quorum majority requirement, a cluster can sustain sequential node shutdowns to a single node– This is referred to as a “Last Man Standing”

scenario

Dynamic Quorum

#mstechdays Infrastructure, communication & collaboration

• Does not allow a cluster to sustain a simultaneous failure of majority of voting members– To continue running, the cluster must always

maintain quorum after a node shutdown or failure

• If you manually remove a node’s vote, the cluster does not dynamically add the vote back

Dynamic Quorum

#mstechdays Infrastructure, communication & collaboration

Dynamic QuorumMajority of 7 required

#mstechdays Infrastructure, communication & collaboration

Dynamic Quorum

XX

X

Majority of 4 requiredMajority of 7 required

#mstechdays Infrastructure, communication & collaboration

Dynamic Quorum

XX

XX

Majority of 3 required

#mstechdays Infrastructure, communication & collaboration

Dynamic Quorum

XX

XXX

Majority of 2 required

#mstechdays Infrastructure, communication & collaboration

Dynamic Quorum

XX

XX

X

Majority of 2 required

#mstechdays Infrastructure, communication & collaboration

Dynamic Quorum

XX

XX

X

1

0

Majority of 2 required

#mstechdays Infrastructure, communication & collaboration

Dynamic Quorum

XX

XX

X

0

1

Majority of 2 required

#mstechdays Infrastructure, communication & collaboration

Dynamic Quorum

XX

XX

X

0

1

Majority of 2 required

X

#mstechdays Infrastructure, communication & collaboration

Dynamic Quorum

XX

XX

X

0

1

Majority of 2 required

XX

#mstechdays Infrastructure, communication & collaboration

Use Get-ClusterNode to verify DynamicWeight property

0 = does not have quorum vote1 = has quorum vote

Get-ClusterNode <Name> | ft name, *weight, state

Dynamic Quorum

Name DynamicWeight NodeWeight State---- ------------- ---------- -----EX1 1 1 Up

#mstechdays Infrastructure, communication & collaboration

• Works with most DAGs– Third-party replication DAGs not tested

• All internal testing has it enabled• Office 365 servers use it• Exchange is not dynamic quorum-

aware• Does not change quorum

requirements

Dynamic Quorum

#mstechdays Infrastructure, communication & collaboration

• Cluster team guidance:– Generally increases the availability of the cluster– Enabled by default, strongly recommended to leave

enabled– Allows the cluster to continue running in failure scenarios

that are not possible when this option is disabled

• Exchange team guidance:– Leave it enabled for majority of DAG members– In some cases where a Windows 2008 R2 DAG would have

lost quorum, a Windows 2012 DAG can maintain quorum– Don’t factor it into availability plans

Dynamic Quorum

Infrastructure, communication & collaboration

#mstechdays

DATABASE AVAILABILITY GROUP MEMBER MAINTENANCE

#mstechdays Infrastructure, communication & collaboration

• Exchange 2010 guidance– Run StartDagServerMaintenance.ps1– Perform the maintenance (e.g., install the SP or UR)– Run StopDagServerMaintenance.ps1– Optionally rebalance the DAG by running

RedistributeActiveDatabases.ps1

• Exchange 2013 guidance different due to architectural changes– http://aka.ms/DAG2013MM

DAG Member Maintenance

#mstechdays Infrastructure, communication & collaboration

Go into maintenance modeSet-ServerComponentState <Server> -Component HubTransport -State Draining -Requester MaintenanceRestart-Service MSExchangeTransportSet-ServerComponentState <Server> -Component UMCallRouter –State Draining –Requester MaintenanceRedirect-Message -Server <Server> -Target <FQDNTarget>Suspend-ClusterNode <Server>Set-MailboxServer <Server> -DatabaseCopyActivationDisabledAndMoveNow $TrueSet-MailboxServer <Server> -DatabaseCopyAutoActivationPolicy BlockedSet-ServerComponentState <Server> -Component ServerWideOffline -State Inactive -Requester Maintenance

Verify production modeGet-ServerComponentState <Server> | ft Component,State -AutosizeGet-MailboxServer <Server> | ft DatabaseCopy* -AutosizeGet-ClusterNode <Server> | flGet-Queue

DAG Member Maintenance

#mstechdays Infrastructure, communication & collaboration

Go into productionSet-ServerComponentState <Server> -Component ServerWideOffline -State Active -Requester MaintenanceSet-ServerComponentState <Server> -Component UMCallRouter –State Active –Requester MaintenanceResume-ClusterNode <Server>Set-MailboxServer <Server> -DatabaseCopyActivationDisabledAndMoveNow $FalseSet-MailboxServer <Server> -DatabaseCopyAutoActivationPolicy UnrestrictedSet-ServerComponentState <Server> -Component HubTransport -State Active -Requester MaintenanceRestart-Service MSExchangeTransport

Verify production modeGet-ServerComponentState <Server> | ft Component,State -AutosizeGet-MailboxServer <Server> | ft DatabaseCopy* -AutosizeGet-ClusterNode <Server> | flGet-Queue

DAG Member Maintenance

#mstechdays Infrastructure, communication & collaboration

• Exchange 2013 Dimensionnement et Performance – 12/02/14 – 17:45-18:30, salle 252B

Related Content

Infrastructure, communication & collaboration

#mstechdays

APPENDIX – RESOURCES

#mstechdays Infrastructure, communication & collaboration

• Office Blogs – http://blogs.office.com/• Exchange Team Blog –

http://aka.ms/ehlo• Lync Team Blog –

http://aka.ms/lyncblog• SharePoint Blog –

http://aka.ms/spblog• Yammer Blog – http://

aka.ms/yammerblog• Outlook Blog – http://

aka.ms/outlookblog

Office-related Blogs

#mstechdays Infrastructure, communication & collaboration

• Excel Blog – http://aka.ms/excelblog• Power Bi Blog – http://aka.ms/pbiblog• Office 365 for Business Blog – http://

aka.ms/o365fbblog• Project Blog – http://

aka.ms/msprojectblog• OneNote Blog – http://

aka.ms/onenoteblog

Office-related Blogs

#mstechdays Infrastructure, communication & collaboration

• Access Blog – http://aka.ms/accessblog

• OneDrive Blog – http://blog.onedrive.com/

• PowerPoint Blog – http://aka.ms/pptblog

• Word Blog – http://aka.ms/wordblog• Office for Mac Blog –

http://aka.ms/ofmblog

Office-related Blogs

Join the conversation

#iammec

Sign up for the newsletter

<mecupdates>

Promote with customers

www.iammec.com

Internal site for all info

aka.ms/MECfield

Infrastructure, communication & collaboration

#mstechdays

QUESTIONS?

Thank You!

© 2014 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 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.

Digital is business