Presentation is loading. Please wait.

Presentation is loading. Please wait.

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.

Similar presentations


Presentation on theme: "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."— Presentation transcript:

1

2

3

4 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

5

6 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

7

8 Customer Touch Points

9

10 —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”

11

12 Exchange 2013 Server Managed Availability

13 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]

14

15

16

17 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

18

19

20 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 1 60 4 ComponentOnlineTrue 512 288 5Large MoveClusterGroupTrue240 N/A14803 ResumeCatalogTrue548512 WatsonDumpTrue480N/A17204

21

22 USER SYSTE M

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

24

25

26 See Appendix for property name definitionsAppendix

27

28

29 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”

30 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

31

32

33

34 http://microsoft.com/msdn www.microsoft.com/learning http://channel9.msdn.com/Events/TechEd http://microsoft.com/technet

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49


Download ppt "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."

Similar presentations


Ads by Google