CAS Exchange 2013 architecture For a given mailbox’s connectivity, the protocol being used is always served by the server that hosts the active database copy Exchange Online service changed the engineering approach to monitoring Scale drives automation Component based monitoring does not tell the story User DAG1 MBX-A MBX-B MBX-A Layer 4LB

Bringing the learnings from the service to the enterprise Monitoring based on the end user’s experience Protect the user’s experience through recovery oriented computing

Customer Touch Points

—OWA send —OWA failure —OWA fast recovery —OWA verified as healthy —OWA send —OWA failure —OWA fast recovery —Failover server’s databases —OWA verified as healthy —Server becomes “good” failover target (again) LBCAS-1 CAS-2 DAG MBX-1 DB1 DB2 MBX-2 OWA DB1 DB2 MBX-3 OWA DB1 DB2 OWA DB1 “stuff breaks and the Experience does not”

Exchange 2013 Server Managed Availability

System Level Checks 1.Mailbox Self Test (e.g. OWA MST) [detection 5m] 2.Protocol Self Test (e.g. OWA PST) [detection 20 secs] 3.Proxy Self Test (e.g. OWA PrST) [detection 20 secs] End User Experience Level Checks 4.Customer Touch Point – CTP (e.g. OWA CTP) [detection 20m]

Monitor States Sampling DetectionRecovery Probe Probe Definition Monitor Monitor Results (Alerts) Monitor Definition Responder Responder Results (Responses) Responder Definition Healthy T1 T2 T3 00:00:00 00:00:10 00:00:30 Restart Responder Reset AppPool Responder Failover responder Bugcheck responder Offline Responder Escalate Responder Sequenced HA Responder Pipeline Example Named Times Probe Results (Samples) Notification Item

RecoveryActionEnabled Per ServerPer Group Minutes Between Actions Max Allowed Per Hour Max Allowed Per Day Minutes Between Actions Max Allowed Per Day ForceRebootTrue720N/A16004 SystemFailoverTrue60N/A1604 RestartServiceTrue 60 N/A1604 ResetIISPoolTrue60N/A1604 DatabaseFailoverTrue120 N/A11204 ComponentOfflineTrue 60N/A ComponentOnlineTrue Large MoveClusterGroupTrue240 N/A14803 ResumeCatalogTrue WatsonDumpTrue480N/A17204

USER SYSTE M

Protocol Health Set Proxy Health Set CTP Health Set OWA OWA.Proxy OWA.Protocol *See slide 13 to view monitoring layer details

See Appendix for property name definitionsAppendix

The Bottom Line —OWA send —OWA failure —OWA failure detected —OWA restart App pool —OWA restart complete —OWA verified as healthy —OWA send —OWA failure —OWA failure detected —OWA restart App pool —OWA restart failed —Failover server’s databases —OWA service restarts —OWA verified as healthy —Server becomes “good” failover target (again) NLB CAS-1 CAS-2 DAG MBX-1 DB1 DB2 MBX-2 OWA DB1 DB2 MBX-3 OWA DB1 DB2 OWA DB1 Managed Availability + Retries…“stuff breaks and the Experience does not”

Bringing the learnings from the service to the enterprise Monitoring based on the end user’s experience Protect the user’s experience through recovery oriented computing