MOVING TO EXCHANGE SERVER 2013

What You Need to Know Before You Migrate: Behind the Scenes

ABOUT COHESIVE LOGIC

Started in 2010 Continual Organic Growth for Over 100 Successful Projects Headquarters in Issaquah, Washington | Nationwide Footprint 97% of Customers Return for Multiple Projects and/or Support Contracts Focus on Microsoft Infrastructure Exchange Active Directory Lync SharePoint

AGENDA

Quiz Complexity is the Enemy Increasing Mailbox Performance Reducing Client Access Infrastructure Upgrade Considerations Questions

POP QUIZ

COMPLEXITY IS THE ENEMY

REDUCING OPERATIONAL COMPLEXITY

Microsofts Goals for Exchange 2007-2013 Reduce support Improve scalability Simplify operations

Takebacks or Takedowns? MAPI over TCP vs. Outlook Anywhere and EWS Role reduction: Hub, Edge, UM No more MMC-based management Correct setup enables more automation

EXCHANGE 2013 SERVICE HEALTH

Follow the design guidelines Properly sized Properly redundant Properly compartmentalized

Focus on the user experience: MCSE + Red October Dont waste time troubleshooting transient errors Assume all errors are transient unless they repeat Restart faulty components and services Alert on repeating errors that pass thresholds

WEANING US OFF THE HCL

Single Copy Clustering Limited HCL compliance $$$ Complex networking, storage, servers

Storage Redundant components and pathways High-performance spindles Aggregates to provide capacity

Load Balancing L7 CPU-intensive packet/session payload inspection L4 low -CPU packet header inspection (IP addresses and ports)

INCREASING MAILBOX PERFORMANCE

MAILBOX: CAPACITY VS. PERFORMANCE

Reduce disk performance requirements by shifting to CPU and RAM Rewrite IS in managed code to isolate database processes Content indexing during transport pipeline Caching to drive IOPS down by 90% more from Exchange 2003
IOPS Comparison per Mailbox
1.800 1.600 1.400 1.200 1.000 0.800 0.600 0.400 0.200 0.000 50 msgs 100 msgs 150 msgs 200 msgs 250 msgs 300 msgs 350 msgs 400 msgs 450 msgs 500 msgs

Exchange 2007

Exchange 2010

Exchange 2013

Change operational patterns Treat databases as interchangeable generic storage pools Provision exceptions per-mailbox, not per-database

DATABASE FORMAT IMPACT ON USED SPACE

Up to 30%

REDUCING CLIENT ACCESS INFRASTRUCTURE

CLIENT ACCESS: STATELESS OF THE ART

Where did we keep track of state? Client Mailbox role Client Access role Reverse proxy Load balancer(s)

Native protocols to the Client Access role; RPC to the Mailbox role

Client state is why we couldnt have nice things.

CLIENT ACCESS 1-2-3 IN EXCHANGE 2013

Thou shalt be secure and efficient Determine who the user is (pre-authentication) Pool and reuse network connections to the mailbox roles

Thou shalt be stateless Proxy to the appropriate mailbox role Inspect no headers, inject no cookies

Thou shalt perform no client rendering Do not fetch data from the mailbox role Use native protocols, not RPCs

DO I REALLY NEED A LOAD BALANCER?

Yes, you do DNS round robin + CAS down = slow user experiences & troubleshooting WNLB = more servers to allow MB DAG + CAS WNLB Modern options are inexpensive

Why dont I need a load balancer? SSL offload NOT SUPPORTED Layer 7 cookies

What does a load balancer give me I dont otherwise get? Reverse proxy without TMG or home-rolled solution Deployment options for redundancy

THE TRUTH ABOUT TMG

TMG is still available Are your existing TMG servers still working? You can still buy TMG appliances You may still have TMG licenses in your EA/SA plan Dont rip and replace without a good reason If you have a reason, dont hesitate to replace it Other features Other applications Redundancy Monitoring and maintenance No longer sold is not a good reason Was TMG ever truly necessary?

UPGRADE CONSIDERATIONS

THIRD PARTY SERVICES

Do they require MAPI or VSAPI? Upgrade them first Find replacements Do without

Backups Consider Native Data Protection as a baseline Quantify cost savings for NDP vs. current backups Use backups to meet business requirements NDP does not meet Use cost savings as leverage to remove unrealistic requirements

Monitoring Must be Exchange 2013 aware Correlate errors, service health across related components IP pings, WMI, event logs only are not adequate

UPGRADING TO EXCHANGE SERVER 2013

Organization in-place from Exchange 2007 and Exchange 2010 Servers are not in-place No Exchange 2003 or before Windows 2003 Active Directory still the minimum

Forest topology Single forest Resource forest Cross-org forest

Toolset Native tools Third-party tools How much data do you need to move? Cost and complexity vs. fidelity

THE UPGRADE MATRIX

QUESTIONS

FURTHER QUESTIONS?

Devin Ganger, MCM, Principal Consultant Devin.Ganger@cohesivelogic.com Twitter: @devinganger Jeremy Phillips, MCITP, Founder & CEO Jeremy.Phillips@cohesivelogic.com Twitter: @jerephil General Contact Info Website: www.cohesivelogic.com Phone: (425) 949-1337 Twitter: @CohesiveLogic Facebook: www.facebook.com/CohesiveLogic LinkedIn: Search for Cohesive Logic