Find and fix the Root cause code Recover the client experience Repair the symptom Remove complexity

Easier deployment and management Fewer things that can fail

X

Forget about replacing disks as they fail Probability you’ll need to replace more than monthly: =(1-BINOM.DIST(spares + 1, disks per server, AFR/12, TRUE))*servers

Probe engine: data collection and notifications mechanism, feeding into… Monitor engine: contains business logic to evaluate health of customer- impacting features Responder engine: set of recovery actions that can be taken to recover degraded state of the monitored resource

… OneCopyMonitor UNHEALTHY

Maximum Preferred Actives Optimized for load Still allows mount Example: 19 Designed optimum Result of Redistribute- ActiveDatabases.ps1 Example: 14

Move-Activ boxDatabase -SkipMaximumActiveDatabaseChecks skips both

ToolParameterValueInstanceUsage Suspend- MailboxDatabaseCopy ActivationOnly N/APer database copy Keep active off a working but questionable drive Set-MailboxServer DatabaseCopyAutoActivationPolicy “Blocked” or “Unrestricted” Per server Used to control active/passive SR configurations and maintenance Can force admin move Set-MailboxServer DatabaseCopyActivationDisabledAndMoveNow $true or $falsePer server Used to do faster site failovers and maintain database availability Databases are not blocked from failing back Continuous move-off operation

Majority of 7 required

X X X Majority of 4 requiredMajority of 7 required

X X X X Majority of 3 required

X X X X X Majority of 2 required

X X X X X

X X X X X 1 0

X X X X X 0 1

X X X X X 0 1 X

X X X X X 0 1 X X

NameDynamicWeightNodeWeightState EX111Up

Deployment scenarioRecommendations DAG(s) deployed in a single datacenterLocate witness server in the same datacenter as DAG members; can share one server across DAGs DAG(s) deployed across two datacenters; No additional locations available Locate witness server in primary datacenter; can share one server across DAGs DAG(s) deployed across two+ datacentersLocate witness server in third location; can share one server across DAGs

Witness Offline Witness vote gets removed by the cluster Witness Online If necessary, Witness vote is added back by the cluster Witness Failure Witness vote gets removed by the cluster Windows Server 2012 R2 and later

cas3cas4cas1cas2

mbx1mbx2mbx3mbx4 Assuming MBX3 and MBX4 are operating and one of them can lock the witness.log file, automatic failover should occur witness

mbx1mbx2mbx3mbx4 1.Mark the failed servers/site as down: Stop-DatabaseAvailabilityGroup DAG1 –ActiveDirectorySite:Redmond 2.Stop the Cluster Service on Remaining DAG members: Stop-Clussvc 3.Activate DAG members in 2 nd datacenter: Restore-DatabaseAvailabilityGroup DAG1 –ActiveDirectorySite:Portland

mbx1mbx2mbx3mbx4 1.Mark the failed servers/site as down: Stop-DatabaseAvailabilityGroup DAG1 –ActiveDirectorySite:Redmond 2.Stop the Cluster Service on Remaining DAG members: Stop-Clussvc 3.Activate DAG members in 2 nd datacenter: Restore-DatabaseAvailabilityGroup DAG1 –ActiveDirectorySite:Portland