Presentation is loading. Please wait.

Presentation is loading. Please wait.

Implementing Exchange Server 2013

Similar presentations


Presentation on theme: "Implementing Exchange Server 2013"— Presentation transcript:

1 Implementing Exchange Server 2013
April 2014

2 About the Presenters Abram Jackson Brian Day
Program Manager for the High Availability Microsoft Exchange Server Team Microsoft Corporation Brian Day Senior Program Manager Office Deployment, Adoption & Readiness Team Brian Shiers at Technet

3 Implementing Exchange Server 2013
April 2014

4 Course Topics Planning for Exchange Server 2013
01 | Upgrade and Deploy Exchange Server 2013 02 | Plan it the right way: Exchange Server 2013 Sizing 03 | Exchange Server 2013 Virtualization Best Practices 04 | High Availability and Site Resilience 05 | Outlook Connectivity

5 High Availability and Site Resilience
Abram Jackson – Program Manager, Microsoft Brian Day – Sr. Program Manager, Microsoft

6 Agenda Responding to failures HA monitoring and server maintenance
Tech Ready 15 9/12/2018 Agenda Responding to failures HA monitoring and server maintenance Best Copy Selection (BCS) Site Resilience © 2012 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.

7 Not on 2013? You’re missing out
Databases recover themselves Services recover themselves Servers recover themselves Datacenters recover themselves Failover time decreased by 50% 58% faster reseeds

8 MEC 2014 9/12/ :30 PM © 2014 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.

9 Responding to failures
9/12/ :30 PM Responding to failures © 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.

10 What should we do about failures?
MEC 2014 9/12/ :30 PM What should we do about failures? Find and fix the root cause code Recover the client experience Repair the symptom Remove complexity recover remove repair root © 2014 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.

11 DAGs without CAAPs Much easier to set up Fewer things that can fail
MEC 2014 9/12/ :30 PM DAGs without CAAPs Much easier to set up Fewer things that can fail Let Exchange manage, or use robust PowerShell © 2014 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.

12 Dag Management service
MEC 2014 9/12/ :30 PM Dag Management service Runs non-critical aspects of maintaining high availability Checking for sufficient redundancy and availability Loose Truncation monitoring Lag manager Separates Log Replication and HA decision making from non-core functions to isolate failure modes © 2014 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.

13 Don’t let databases dismount!
MEC 2014 9/12/ :30 PM Don’t let databases dismount! Active Loose Truncation Passive Loose Truncation © 2014 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.

14 Lagged DB copy management
MEC 2014 9/12/ :30 PM Lagged DB copy management Failed backups are worse than no backups Lagged database copies will play forward beyond their configured value when: The database has a bad page and needs a patch There isn’t enough space to keep all the logs Risk of losing all available copies of a database © 2014 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.

15 AutoReseed overview Restoring redundancy so you don’t have to
MEC 2014 9/12/ :30 PM AutoReseed overview Restoring redundancy so you don’t have to Configured by setting mount points for volumes In-Use Storage X Spares © 2014 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.

16 Demo AutoReseed Microsoft Office365 9/12/2018
© 2012 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.

17 AutoReseed – why? Now extremely robust
MEC 2014 9/12/ :30 PM AutoReseed – why? Now extremely robust 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 © 2014 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.

18 Recovering from storage failures
Exchange Server 2010 ESE Database Hung IO (4 min) Failure Item Channel Heartbeat (0.5 min) System disk Heartbeat (2 min) Exchange Server SP1 Cluster service repeated crashes (60 min) Exchange Server 2013 System Bad State (5 min) Long I/O times (.6 min) Repl memory threshold (4GB) Repl won’t restart (65 min) Store timeout (1 min)

19 World’s largest Exchange deployment
MEC 2014 9/12/ :30 PM World’s largest Exchange deployment 125,000+ databases at 99.98% availability 15 second average DB failover time Site switchovers/month: 100s planned, 10s unplanned 26 locations worldwide © 2014 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.

20 HA monitoring and server maintenance
9/12/ :30 PM HA monitoring and server maintenance © 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.

21 MEC 2014 9/12/ :30 PM Managed Availability Fundamental purpose of Managed Availability is to: Detect customer impacting service degradation Attempt to recover from failure If recovery fails – escalate to Exchange administrators © 2014 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.

22 Managed Availability XYZ_Monitor
MEC 2014 9/12/ :30 PM Managed Availability XYZ_ResetAppPool XYZ_Probe\ Resource1 XYZ_Probe\ Resource2 XYZ_Probe\ Resource3 XYZ_Monitor XYZ_Restart XYZ_Restart XYZ_Failover XYZ_Reboot Monitor engine: pivotal to MA – contains business logic of evaluating health of customer impacting features XYZ_Escalate Probe engine: measurements taking and notifications mechanism, feeding into… Responder engine: set of recovery actions that can be taken to recover degraded state of the monitored resource © 2014 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.

23 Managed Availability Get-ServerHealth Get-HealthReport
provides status of all monitors tracking a particular server Get-HealthReport provides a rollup of health sets for a server or for group of servers Complete set of monitors, probes and responders can be found in Windows crimson log channel

24 HA Managed Availability
HA uses MA to monitor data redundancy, cluster health, physical storage health and database logical corruption HA Probes, Monitors and Responders are grouped into DataProtection and Clustering HealthSets

25 HA Monitors ClusterEndpointMonitor ClusterGroupMonitor
MEC 2014 9/12/ :30 PM HA Monitors ClusterEndpointMonitor ClusterGroupMonitor ClusterHangMonitor ClusterNetworkMonitor ClusterServiceCrashMonitor ServerOneCopyMonitor ServerOneCopyInternalMonitorMonitor ServerWideOfflineMonitor ServiceHealthActiveManagerCheckMonitor ServiceHealthMSExchangeReplCrashMonitor ServiceHealthMSExchangeReplEndpointMonitor DatabaseHealthLogGenerationRateMonitor DatabaseHealthUnMonitoredDatabaseMonitor DatabaseHealthCircLoggingMonitor DatabaseHealthDbCopyFailedAndSuspendedMonitor DatabaseHealthDbCopyStalledMonitor DatabaseHealthDbCopySuspendedMonitor DatabaseHealthLogCopyQueueMonitor DatabaseHealthLogReplayQueueMonitor EseDbTimeTooNewMonitor EseDbTimeTooOldMonitor EseInconsistentDataMonitor EseLostFlushMonitor StorageDbIoHardFailureItemMonitor LowLogVolumeSpaceMonitor © 2014 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.

26 ServerOneCopyMonitor
MEC 2014 9/12/ :30 PM ServerOneCopyMonitor HA’s most important redundancy protection Once a minute each database on a server is checked: Copy is (Healthy || Mounted) && ServerComponentState is NOT Offline && Copy is NOT Activation Blocked && Server is NOT exceeding MaxActive && Copy Queue Length < MountDial && Server is NOT Activation Disabled © 2014 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.

27 HA Monitors – ServerOneCopyMonitor
30 consecutive failures are considered as a Escalating condition Immediately after that OneCopyMonitor is notified and becomes “Unhealthy” OneCopyMonitor Healthy OneCopyMonitor UNHEALTHY OneCopyEscalate OneCopy notification 1 2 3 30

28 ServiceHealthMSExchangeReplEndpointMonitor
MEC 2014 9/12/ :30 PM ServiceHealthMSExchangeReplEndpointMonitor Monitor has three probes and five responders: RestartResponder ReplEndpointProbe\ RPC RestartResponder2 ReplEndpontMonitor ReplEndpointProbe\ TCP FailoverResponder RebootResponder ReplEndpointProbe\ ServerLocator EscalateResponder © 2014 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.

29 DAG member maintenance
In Exchange 2013 the story is a little bit more complicated than in Exchange 2010 Mailbox Server has multiple roles installed In order to prevent outages we need to make sure server is not serving any client protocol

30 Exchange 2013 server maintenance
Put server into maintenance Set Transport and UM to draining their queues Set messaging redirection to (preferably) another server in the DAG Suspend cluster node Set server to be Activation Disabled Set server to be Activation Blocked Set all ServerComponentStates Offline Confirm All ServerComponentStates are offline Server is activation blocked and activation disabled Cluster node is “Paused” Transport queues are empty

31 Demo High Availability Monitoring Microsoft Office365 9/12/2018
© 2012 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.

32 Best Copy Selection (BCS)
9/12/ :30 PM Best Copy Selection (BCS) © 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.

33 Best Copy and Server Selection
Tech Ready 15 9/12/2018 Best Copy and Server Selection What’s the same? Still Active Manager algorithm Performed at *over time Uses extracted system health Same replication criteria and phases What’s new? Cap replay queue to limit mount time New max actives soft limit BCS criteria includes protocol stack health Protocol health prioritized to control impact Tuned replication health criteria thresholds MA failover responder targets not worse server © 2012 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.

34 Activation controls Load management limits
Controls server max load Server-level activation controls Controls server usage Database-level activation control Prevent copy activation – questionable database copy?

35 Load management limits
MEC 2014 9/12/ :30 PM Load management limits Maximum Preferred Actives Optimized for load Still allows mount Example: 19 Designed optimum Result of Redistribute- ActiveDatabases.ps1 Example: 14 © 2014 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.

36 Load management limits
MEC 2014 9/12/ :30 PM Load management limits MaximumActiveDatabases Hard limit for activation– i.e. worst case Enforced by BCS Dismount databases over limit Control “exceptional failure” load Set to most mdbs you want per server Follow role requirements calculator guidance MaximumPreferredActive Databases Soft limit for activation – new in SP1 Copies deprioritized in BCS Catalog and copy queue health Failovers can exceed limit Load balancing optimizes to this limit Checks can be skipped in Move-Activ boxDatabase Parameter “SkipMaximumActiveDatabaseChecks” skips both; be careful! © 2014 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.

37 Best Copy and Protocol Health
Normal *over behavior All health sets healthy All medium priority health sets and above are healthy All health sets on target server are better than source server All health sets on target server are the same as source server Server health not considered MA failover responder behavior Skip target if not better than source server All health sets healthy All medium priority and above are healthy All health sets better than source server

38 9/12/ :30 PM Site Resilience © 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.

39 DatabaseDisabledAndMoveNow
New server setting to improve site resilience Get all active databases off server – FAST! Last resort to not move an active! Proactively continue move databases attempts Server can still be in service Databases mounted and mail delivery!

40 Contrast Activation Block Modes
Tool Parameter Value Instance Usage Suspend-MailboxDatabaseCopy ActivationOnly N/A Per 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….. DatabaseCopyActivationDisabledAndMoveNow $true or $false Used to do faster site failovers and maintain database availability. Databases are not blocked from failing back. Continuous move off operation .

41 Maintenance Mode vs. Site Resilience
Server is out of service No active databases No PAM No mailflow Used for: Software installation Hardware or software repair Site Resilience CAS out of service REMOVED from name space NOT in maintenance mode Mailboxes not out of service Can be forced to provide active service VS.

42 Dynamic Quorum Scenarios
9/12/2018 Dynamic Quorum Scenarios Windows Server 2012 and later Node Shutdown Node removes its own vote Node Crash Remaining active nodes remove vote of the downed node Node Join On successful join the node gets its vote back © 2012 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.

43 Dynamic Witness Scenarios
9/12/2018 Dynamic Witness Scenarios Windows Server 2012 R2 and later Witness Offline Witness vote gets removed by the cluster Witness Failure Witness vote gets removed by the cluster Witness Online ` © 2012 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.

44 Dynamic Quorum and DAGs
MEC 2014 9/12/ :30 PM Dynamic Quorum and DAGs Exchange is not dynamic quorum or witness - aware DAGS use dynamic quorum to reduce Restore-DAG usage No quorum requirements changes for DAGs Internal DAG testing used dynamic quorum Enabled in Office 365 for servers on Windows Server 2012 Guidance: Use it; it will help DAG availability If using Dynamic Quorum and Restore-DAG make sure excluded nodes are powered off and will not automatically power on © 2014 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.

45 Exchange Server 2013 Witness Servers
Microsoft Exchange 9/12/2018 Exchange Server 2013 Witness Servers New Witness Server placement options available Right answer based on biz needs and available options Third location DAG witness server improves DAG recovery behaviors Automatic recovery on datacenter loss; Third location network infrastructure must have independent failure modes Deployment scenario Recommendations DAG(s) deployed in a single datacenter Locate 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+ datacenters Locate witness server in third location; can share one server across DAGs © 2012 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.

46 Site Resilience Frontend/Backend recovery are independent!!!
Tech Ready 15 9/12/2018 Site Resilience Frontend/Backend recovery are independent!!! DNS resolves to multiple IP addresses Most protocol access in Exchange Server 2013 is HTTP HTTP clients have built-in IP failover capabilities Clients skip past IPs that produce hard TCP failures © 2012 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.

47 Tech Ready 15 9/12/2018 Site Resilience Admins can switchover by removing VIP from DNS or disabling Namespace no longer a single point of failure No dealing with DNS latency Single or multiple name space options © 2012 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.

48 Best Practices Automate your recovery logic; make it reliable
Think of it as rack/site maintenance? Exercise it regularly Recovery times directly dependent on detection & decision times! “Flip the bit” – don’t ask repair times, “if outage go…” Humans are the biggest threat to recovery times

49 9/12/ :30 PM © 2014 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. © 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.

50 9/12/ :30 PM Appendix © 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.

51

52 Automatic Reseed; Implementation Steps
Tech Ready 15 9/12/2018 Automatic Reseed; Implementation Steps Configure Storage subsystem with spare disks Create DAG, add servers with configured storage Create directory and mount points Configure DAG, including AutoDAG properties Create mailbox databases and database copies \ AutoDagVolumesRootFolderPath (DAG) AutoDagDatabasesRootFolderPath (DAG) ExchVols ExchDbs MDB1 MDB2 Vol1 Vol2 Vol3 AutoDagDatabaseCopiesPerVolume (DAG) == 1 MDB1 MDB2 Manipulate the settings with Set/Get-DatabaseAvailabilityGroup Drive replacement remains manual because of SKU MDB1.db MDB1.log MDB1.db MDB1.log Mount point © 2012 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.

53 Automatic Reseed Periodically scan for failed and suspended copies (15 m) (1 hr) Resume copy three times (45 m) Pre-reqs, then remap a spare Start the seed Verify that healthy copy Release the original spare

54 Tie Breaker Cluster will survive simultaneous loss of 50% votes
Especially useful in multi-site DR scenarios with even split Cluster always ensures total number of votes are Odd One site automatically elected to win By default, cluster randomly selects a node to take its vote out LowerQuorumPriorityNodeID cluster common property identifies a node to take its vote out Cluster Site1 Site2

55 Single Common Namespace Example Geographical DNS Solution
Sue (traveling in APAC) Sue (somewhere in NA) mail.contoso.com DNS Resolution DNS Resolution via Geo-DNS Round-Robin between # of VIPs Round-Robin between # of VIPs VIP #1 VIP #2 VIP #3 VIP #4 DAG DAG

56 Best Copy and Protocol Health
MEC 2014 9/12/ :30 PM Best Copy and Protocol Health Managed Availability failover responder behavior All Healthy Checks for a server hosting a copy that has all health sets in a healthy state Up to Normal Healthy Checks for a server hosting a copy that has all health sets Medium and above in a healthy state All Better than Source Checks for a server hosting a copy that has health sets in a state that is better than the current server hosting the affected copy Same as Source Checks for a server hosting a copy of the affected database that has health sets in a state that is the same as the current server hosting the affected copy © 2014 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.

57 Dynamic Quorum DQ = 7

58 Dynamic Quorum DQ = 4 X

59 Dynamic Quorum DQ = 4 X

60 X Dynamic Quorum DQ = 3 Node weight = 0 Node weight = 0

61 X Dynamic Quorum DQ = 3 Node weight = 0 Node weight = 0

62 Site Resilience - CAS With multiple VIP endpoints sharing the same namespace, if one VIP fails, clients automatically failover to alternate VIP and just work! Removing failing IP from DNS puts you in control of in service time of VIP X mail.contoso.com: mail.contoso.com: , primary datacenter: Redmond alternate datacenter: Portland VIP: VIP: cas1 cas2 cas3 cas4

63 Site Resilience - Mailbox
Tech Ready 15 9/12/2018 Site Resilience - Mailbox Mark the failed servers/site as down: Stop-DatabaseAvailabilityGroup DAG1 –ActiveDirectorySite:Redmond Stop the Cluster Service on Remaining DAG members: Stop-Clussvc Activate DAG members in 2nd datacenter: Restore-DatabaseAvailabilityGroup DAG1 –ActiveDirectorySite:Portland X X X primary datacenter: Redmond alternate datacenter: Portland dag1 mbx1 mbx2 mbx3 mbx4 witness © 2012 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.

64 Site Resilience - Mailbox
Mark the failed servers/site as down: Stop-DatabaseAvailabilityGroup DAG1 –ActiveDirectorySite:Redmond Stop the Cluster Service on Remaining DAG members: Stop-Clussvc Activate DAG members in 2nd datacenter: Restore-DatabaseAvailabilityGroup DAG1 –ActiveDirectorySite:Portland X primary datacenter: Redmond alternate datacenter: Portland dag1 mbx1 mbx2 mbx3 mbx4 alternate witness witness


Download ppt "Implementing Exchange Server 2013"

Similar presentations


Ads by Google