Transcript Exchange Server 2013 Architecture, Part 2

http://justaucguy.wordpress.com/
What version of Exchange are you on?
Exchange 2013?
Exchange 2010?
Exchange 2007?
Exchange 2003?
Exchange 2000?  Really?
•
Features are subject to change
•
Pricing of new capabilities is yet to be determined
This presentation contains preliminary information
that may be changed substantially prior to final
commercial release of the software described herein.
(per Microsoft)
•
•
•
•
•
•
System / AD Requirements
Outlook 2010 +
MAPI / HTTP
IP Less DAGs
IOPS reduction – again
Up to 40% Network traffic reduction
• MAPI / CDO
Operating System Requirements
• Windows Server 2012 R2 or Windows Server 10
• .NET Framework 4.5.2
• Windows Management Framework 4.0
• Unified Communications Managed API (UCMA) 4.0
Domain / Forest Levels (minimum)
•
Windows Server 2008 R2 Forest functional level
•
Windows Server 2008 R2 Domain functional level
•
Windows Server 2008 R2 Global Catalog servers
•
Windows Server 2008 R2 Domain Controllers
Outlook 2016
• Outlook 2013 with SP1 (& KB3020812)
• Outlook 2010 with SP2 (& KB2956191 / KB2965295)
• Outlook for Mac 2011 or later
•
• Outlook 2007
Replacement for RPC over HTTP
Uses standard HTTP commands
Exchange 2013
** NOTE **
• Make sure to configure your MAPI
virtual directory.
• Forgetting to do so might result in a
subpar user experience.
•
Off by default
•
Turned on or off at the organizational level
Exchange 2016
•
On by default
•
Turned on or off at the user level
Introduced in Exchange 2013 SP1
Reduces complexity for installation
Exchange 2013
** NOTE **
• Less IP Addresses needed for
Exchange
• Verify third-party apps will work with
this configuration
•
Not configured by default
•
IP Addresses are required for the DAG
Exchange 2016
•
IP Less DAGs are configured by default
•
Less IP Addresses to assign and remember for Exchange
Exchange 2016
• Reduces IOPS from Exchange 2013
by another 22%.
What does this mean?
•
•
•
•
How were IOPS reduced in 2016?
Less reliance on SAN
Less reliance on RAID
Less reliance on expensive hardware
Lower operating costs
Lagged Copies – adjustments made to reduce IOPS by 22%
Index for active and passive databases are built
from the local database copy – no longer uses the
active copy only.
• For a four copy DAG in 4 datacenters – 40% traffic
reduction
• Less copies/locations will equal less reduction –
20-30% is the estimation
• Possible as a small subset of RPC operations can
now be performed against the passive copies.
•
•
Role Consolidation
•
Collaboration Improved
•
Coexistence Changes
•
Emphasis on the Preferred Architecture
•
Improved Reliability and Performance
•
Data Loss Protection
•
Auditing
•
Outlook Add-Ins and Apps
•
Outlook Search Improvements
•
Modern Attachments
Exchange Server
2007
Exchange Server
2010
Edge Transport Server
Edge Transport Server
Client Access Server
Client Access Server
Hub Transport
Hub Transport
Mailbox Server
Mailbox Server
Unified Messaging
Unified Messaging
Exchange Server
2013
2013
– Pre
– SP1
SP1
Exchange Server
2016
Edge Transport Server
Edge Transport Server
Client Access Server
Mailbox Server
Mailbox Server
Fully on-premises
(documents stored in SharePoint 2016)
On-premises
Exchange Server
2016
SharePoint Server
2016
Office Web Apps
Server
2016
Exchange integration with Outlook and
SharePoint helps solve one of email’s
oldest pain points: working with
attachments
Receiving and editing documents
Sharing documents
Exchange 2016 Coexistence is much better.
•
Exchange 2013 can front end Exchange 2016 and Exchange 2010
OWA Redirect if ExternalURL
exists in remote site.
mail.contoso.com
europe.mail.contoso.com
Layer 4 or 7 LB
IIS
HTTP Proxy
E2010 CAS
E2016
Store
Protocol Head
DB
DB
E2010 MBX
9
Site Boundary
Protocol Head
Layer 7 LB
Protocol Head
E2010 CAS
Store
DB
E2010 MBX
Setup formalizes the Preferred Architecture
•
Building block model with combined Mailbox and Client Access Server role
•
Use commodity hardware
•
Multiple database per volume
•
Battery backed up controller
•
DAGs – symmetric datacenter layout, single network (no replication
network), witness in 3rd datacenter (or Azure), one lagged copy
• Automated Repair
• Find database corruptions via DB divergence detection
• Loose Truncation – long-term outages out-of-space won’t dismount DB
• ReFS Support – Decrease FS corruption, reseeds and rebuilds
• Faster Recovery (now even more HA)
•
•
•
•
Faster database *overs (95%ile @ 18s)
Faster site resilience: Database copy activation suspended and Move Now
DAG Management Service – reducing failure domains
Replay Lag Manager on by default – auto-play down
when insufficient avail copies
• Reduced WAN costs - Search index using passive copy
• Supports bigger disks with less IOPS
(>22% lower than E15 RTM)
• 8 TB, 7200 RPM JBOD
• Delayed lag play-down
DB Maintenance compares active and passive copies to detect logical corruption and data
divergence
• Finds logical corruption due to:
o Controller failures
o Battery failures for controllers
o hardware firmware bugs
o transient memory corruptions
o Minimal increase in log generation - ~ 72MB log db /day
•
•
Logging for this - ESE Event 538, 539 and 540
Builds on hybrid capabilities introduced in previous Exchange
versions
Secure mail routing
Unified address list
Free/busy calendar sharing
Single OWA URL
Hybrid Configuration Wizard now cloud-deployed
• Works with Exchange 2013 and 2016, independent of CU
• Multi-forest support with AADSync, OAuth enhancements for MFA and more
New DLP sensitive
information types
added to Exchange
PolicyTips added to
Excel and other Office
applications
Extension of DLP
capabilities to SharePoint
New auditing architecture
and schema
Same as Office 365 audit log
structure; makes hybrid scenarios
and integration with 3rd party
products easier
Improved search and filtering for
audit data across the
organization
Integrate apps to the Outlook UI
to enable engaging experiences
Multiple integration points:
Ribbon
Command Bar
Context menus (right-click),
Body text (hover)
Task pane
Side-loading – easy peer
deployment of line-of-business
apps
Strong admin control
New add-ins developed by 3rd
parties: DocuSign, Salesforce,
Uber, Boomerang, Do.com, and
more
Sub Second Search in OWA and Outlook
o Directly from Office 365 analysis of searching
• Schema Changes needed in order to make this happen
• Involves:
o Pre-reading as much information as possible
o Moving certain bits of information into different areas to enable the
content to be found faster
•
• Calendar searching in OWA!
• Don’t disable IPV6 completely
• Use High Performance Power Plan
• If using a WAC server (called OOS now), configure this for OWA
• Exchange 2013 can managed 2016 objects
• Exchange 2016 can manage 2013 objects
• Exchange 2010 is a crap shoot for management, use native 2010 tools
• DO NOT restrict the dynamic TCP port range
• Disable Hyper-threading
• Plan your namespace carefully, just like older versions
Damian Scoles | Netrix LLC
Microsoft Exchange Server MVP
[email protected]
http://justaucguy.wordpress.com