Download presentation
Presentation is loading. Please wait.
Published byEsperanza Villalobos Vázquez Modified over 6 years ago
1
Exchange 2010 and Virtualization VirtG’s Deep Dive Day March 10, 2010
Lee Benjamin ExchangeGuy Consulting 1
2
About Lee Benjamin ExchangeGuy Consulting User Groups
Architecture, Migration/Upgrades, Project Guidance ISV Advisor, Strategy, Whitepapers, Testing, Reviews Industry Events, Speaker, Custom Training, Expert User Groups Chairman Vice President Global Secretary Advisor
3
Agenda Virtualizing Exchange 2010 Architectural Foundation
Common Questions, Releases Architectural Foundation Exchange Server Roles Foundation Technologies Virtualization and Exchange Generalities Hyper-V, Other (WSVVP) Exchange Online In Office 365
4
Common Questions What Exchange Roles can I virtualize?
Should I virtualize the Mailbox Role? Can I virtualize with VMware, or just Hyper-V? What about virtualization snapshots? Should I use Network Load Balancing? Can I virtualize the Unified Messaging Role? Can I virtualize Lync? Is Office 365 considered virtualization?
5
Exchange Server 2010 Releases
Released November 2009 Final RTM Rollup 5 Released December 2010 EX2010 RTM Is No Longer Supported (With or Without RU) Service Pack 1 EX2010 SP1 Released August 2010 Rollup 6 for SP1 Released October 2011 Service Pack 2 EX2010 SP2 Released December 2011 Hybrid Configuration Wizard, OWA Mini, Address Book Policies (GAL Segmentation) Rollup 1 for SP2 Released February 2012
6
MEC Is Back !! Microsoft Exchange Conference MEC Returns
Was The Conference About Exchange 1996 Austin (Exchange Deployment Conference) 1997 San Diego 1998 Boston 1999 Atlanta/Hamburg/Tokyo 2000 Dallas/Nice/Tokyo/Singapore 2001 Orlando/Nice Started Out Reasonable Size (Though 4000 Peak in Boston) Many Community Experts Disappeared For Ten Years.. ? MEC Returns September 24-26, 2012 In Orlando Focus is Exchange, On-Premises and Cloud
7
Exchange Server Roles Exchange 2003 Exchange 2010/2007
SMTP, POP3/IMAP4 HTTPS Outlook Web Access Exchange ActiveSync Hygiene (AV/AS) Optional 1. Front-End Server Mailbox Databases Routing MAPI/Outlook Includes Front-End 2. Back-End Server Client Connection Point, Required Including Outlook/MAPI In 2010 More Load, = More CPU + Memory 1. CAS – Client Access Server All Message Routing, Required Shadow/Resiliency In 2010 2. HUB – Hub Transport Role 64 Bit ESE Database Scalability And Performance 3. MBX – Mailbox Role Voic , Voice Access, Voic Preview 4. UM – Unified Messaging Routing and Hygiene Lives Alone, Optional 5. EDGE- Edge Transport Role
8
Exchange 2010 Architecture
Phone system (PBX or VOIP) Edge Transport Routing & AV/AS Hub Transport Routing & Policy External SMTP servers Mailbox Storage of mailbox items Unified Messaging Voice mail & voice access Mobile phone Web browser Client Access Client connectivity Web services Outlook Anywhere (remote user) Line of business application Outlook (local user)
9
Exchange 2010 Foundation 64bit Database And Storage Technologies (ESE)
Compliance And Discovery Functionality Integration With Mobility And Voice Anti-Virus, Anti-Spam, And Rights Management Designed For On-Premises and Online-Hosted Availability And Resilience- Virtualization Support
10
Exchange’s Database Extensible Storage Engine (ESE)
Well Known With 16 Years In Production 64bit Database Introduced In Exchange 2007 Removed Database Cache Memory Limitation (1.2GB) Log Files Are 1MB (was 5MB), STM Files Are No More For 2010, Database Reorganized For Large Mailboxes Tables vs. Mailboxes, SIS Casualty, Storage Groups Gone Database Page Repair From Replicated Copy (Lagged) 90% IO Reduction Over Exchange 2003 Really Fast, Latency Matters, No NAS
11
MAPI To The Middle (CAS) Finally
Exchange 2010 Exchange 2007 Middle Tier Exchange Biz Logic Mailbox MAPI RPC Store Exchange Components OWA Sync UM Transport Agents Mailbox Agents WS Entourage Outlook / MAPI DAV Middle Tier MAPI, RFR & NSPI RPC Exchange Core Biz Logic Exchange Biz Logic Mailbox MAPI RPC Store Exchange Components OWA Sync UM Transport Agents Mailbox Agents WS Outlook / MAPI Entourage CAS CAS Performance Implications Moving Heavy Workload
12
Database Availability Groups
SCC, CCR, and SCR Evolved No Clustering Knowledge Required Windows Server Clustering Underneath For Heartbeat From 2 To 16 Replicas, Multiple Active Nodes All Managed Inside Exchange Exchange Management Console or Shell Recommend 3-4 Node DAGs, Or Larger (2 with SP1) Allows Slower SAS Or Lower Cost SATA Disks
13
Must I Sill Backup? Yes. Storage Groups Removed 2010
Store:SG Became 1 : 1 in 2007 Stores Now Owned By The Organization Allows Database Mobility Recover To Another Exchange Server Recovery Database (was Recovery Storage Group) Streaming Backup Support No Longer Only VSS Snapshots From Microsoft And 3rd Parties Backup/Restore From/To Any DAG Member Why Restore When You’ve Got DAG Replication..??
14
Transition: Deployment Assistant
15
Remote Connectivity Analyzer
testexchangeconnectivity.com/ Test Exchange ActiveSync (EAS) Outlook Anywhere (RPC/HTTP) Autodiscover SMTP …More Will Come… Office 365 Use It Every Step Of Transition
16
Architectural Best Practices
Multi-Role Servers When At All Possible Combine Roles CAS+HUB Obvious Similar Functions (Protocols) CAS And HUB Not Supported In the DMZ Not MBX or UM Either, Only Edge Infrastructure Remains Critical 64bit Domain Controllers Load Balancers versus NLB Redundancy, Redundancy, Redundancy
17
EX2010 Virtualization Support
EX2010 Runs On Windows Server 2008 And R2, 64bit Not Supported On Server 8 Beta !! Microsoft Hyper-V Also Microsoft Hyper-V Server/R2 Third-Party Hypervisor Validated Under WSVVP Windows Server Virtualization Validation Program VMware, Other Any Exchange 2010 Role Unified Messaging (UM) Supported SP1 Only Virtualization SW On Host, and Management SW Dynamic Memory Not Useful
18
Virtual Concerns 9-12% Overhead For Hypervisor
Plan For 10% Less Users Same CPU and Memory Requirements As Physical Savings May Not Be There Scale Out Rather Than Scale Up Conscious Decision From Exchange Team Spread The Load And Risk More Servers And Replicated Copies (DAGs) Storage Must Use Fixed Size Virtual Storage Disks, or SCSI Pass-Through Physical Disks, or iSCSI SAN Disks No Differencing Disks, No Hypervisor Snapshots
19
Virtualization Scenarios
CAS/HUB, MBX, UM Branch Office Streamlined Provisioning To Smaller Offices Distributed DR Sites Around The World DR Sites With Lagged Copies Log Files Are Replicated Delayed Insert Into Database (Hours, Days) If Major Corruption, Remove Troubled Log Before Transition Helper CAS/HUB 2007 And CAS/HUB 2010
20
Living With The Cloud- Hybrid
Coexistence Sync AD On-Premises Cloud Services Seamless User Experience
21
Microsoft Office 365 BRINGING TOGETHER CLOUD VERSIONS OF MICROSOFT’S COMMUNICATIONS AND COLLABORATION PRODUCTS WITH THE LATEST VERSION OF OUR DESKTOP SUITE FOR BUSINESSES OF ALL SIZES. 26
22
What’s New in Office 365 Platform Capabilities New user interface
Flexible service offering with pay-as-you-go, per-user licensing The complete Office experience with services integration in Office 365 Always the latest version of the Office apps, including Office Web Apps Familiar Office user experience to access services Voic with unified messaging Integrated personal archiving Retention policies and legal hold Exchange Control Panel Free/busy coexistence Cross-premises management My Sites to manage and share documents Access documents offline Improved Team & Project Sites Document-level permissions to protect sensitive content Share documents securely with Extranet Sites Cross site collection search IM & Presence across firewalls GAL/Skill search in SharePoint Online meeting with desktop sharing Activity feeds Contact photos Click to communicate from Office contact cards Windows Live federation Platform Capabilities New user interface Role based access Identity federation (eliminate sign-in client) Multi-factor authentication support 27
23
Simple Exchange Coexistence
Exchange Online can coexist with Exchange Server on-premises All users share the same domain name and global address list Directory Sync keeps address lists and groups up to date Admin uses Web-based migration tool to move mailboxes in stages Exchange 2010 is not required for simple coexistence features Exchange 2003, 2007 or 2010
24
Rich Exchange Coexistence
Share free/busy data between cloud and on-premises users Manage cloud and on-premises users from one place Configure secure, high-fidelity cross-premises mail flow Migrate users to the cloud with native Exchange tools Easily move mailboxes back on-premises Organizations interested in the smoothest migration experience, or organizations that want to have permanent coexistence, with a mix of some users on-premises, and others in the cloud, would choose “rich Exchange coexistence.” In this scenario, an Exchange 2010 SP1 server is deployed on-premises, and acts as a gateway to the cloud. With the Exchange 2010 SP1 server in place, administrators can: Manage both their local Exchange forest, and their Exchange Online forest, from the Exchange Management Console Move users to the cloud using PowerShell or the Exchange Management Console Enable seamless calendaring, including free busy and full calendar sharing, between hosted and on-prem users Configure cross-premises mailflow so that all mail truly looks and feels like it is internal to the company. And, if desired, configure all inbound and outbound mail to flow through the local servers. Move mailboxes back on-premises if the need arises Although an Exchange 2010 SP1 server is deployed on-premises, there is no need to upgrade mailboxes to Exchange 2010 prior to moving them to the cloud. The Exchange 2010 SP1 server has the ability to act a proxy or bridge, between older Exchange 2003/2007 environments and Exchange Online, without the need to migrate on-premises Exchange mailboxes to Exchange 2010. Once an organization reaches 100% of mailboxes in the cloud, they would typically remove the Exchange 2010 server. The Directory Sync tool and ADFS server would remain in place so to connect on-premises AD infrastructure to the cloud to power SSO, easy provisioning, and a unified directory. Note: The Directory Sync tool, and ADFS (Geneva) federation for enterprise single sign-on would also be part of this coexistence story Let’s take a closer look at the capabilities that light up when a Exchange 2010 server is installed on-premises. Exchange 2010 SP1 “gateway” server enables rich coexistence with Exchange 2003/2007 Exchange 2010 SP1 server Exchange 2003/2007
25
Rich Coexistence Mailbox Moves
11/28/ :59 PM Rich Coexistence Mailbox Moves Exchange 2010 SP1 CAS Mailbox migration Uses same replication engine as on-premises mailbox moves Migration support is built into Exchange Management Console and Remote PowerShell No Outlook resync or profile change required after mailbox move Yes, you can go back When a user is moved to the cloud, it is important that all their mailbox items, from s to calendar appointments to personal contacts and tasks, migrate with them in a seamless way. With rich coexistence, the migration tool is not a web based tool. Instead, mailboxes can be moved to the cloud right from within the Exchange Management Console or Remote PowerShell. In EMC, the simply administrator highlights the mailboxes he wants to move, clicks “migrate mailbox,” and then walks though a wizard to identify specify options and parameters. It’s basically the same as moving a mailbox between two servers on-premises. Cloud migrations now use the same Exchange 2010 Mailbox Replication Service (MRS) that powers mailbox moves between two on-premises servers and also migrations from prior versions of Exchange. A single architecture for mailbox migration means that Exchange Online users benefit from the investments made in on-premises mailbox moves. In this new architecture, the mailbox migration process is asynchronous and fault-tolerant. In the old days of cloud mailbox moves, if a server machine or database went down, or if the administrator accidentally closed the Exchange Online mailbox migration tool, he had to start the move over again. The new replication service, in contrast, runs like a background process. The administrator enters the mailbox move request, and then this request is logged with Exchange Online and picked up by one or more E14 CAS servers on the network. If a server goes down, the request remains in effect, and another server from the pool of available machines and picks up where the previous one left off. You can close EMC or close Powershell window and it keeps working. Plus, the administrator manually suspend or resume the replication at will. When the administrator schedules the mailbox move, he can set the mailbox move to “autocomplete” or choose to have it wait for his confirmation on the last step of the process. And, there is intelligence built in to the migration process, so that the user won’t be switched over to the cloud until data redundancy is satisfied (log shipping to redundant databases and content indexing is complete). This ensures that the user will have responsive mailbox search capabilities, and protection of their data, as soon as they switch. The user’s source mailbox is accessible throughout the move, if the source mailbox is Exchange 2007 SP2 or Exchange When the source mailbox is on Exchange 2003, the move is an offline operation. There is no need for an OST resync after the move, which improves the user’s experience and eases network congestion. Remember that the Exchange 2010 CAS server is acting as a proxy in this scenario. Mailboxes do not need to be moved to Exchange mailbox server first. Exchange 2003 Exchange 2007 Exchange 2010 SP1
26
Office 365 Simple vs. Rich Coexistence
Feature Simple Rich* Mail routing between on-premises and cloud (recipients on either side) Mail routing with shared namespace (if on both sides) Unified global address list (GAL) Free/Busy information and calendar sharing across premises Out of Office notice understands that across-premises is internal to the organization MailTips, messaging tracking, and mailbox search work across premises Outlook Web App Redirection across premises (single URL for Outlook Web App both on premises and in the cloud) Preserve Auth header (that is, ensure internal is not marked as spam, resolve against GAL) Exchange Management Console on premises is used to manage cross-premises mailbox migrations Mailbox moves support both onboarding and offboarding No Outlook reconfiguration or OST resynchronization required after mailbox migration *Rich Coexistence feature set requires Exchange 2010 SP1 HT+CAS on premises and requires supplemental configuration steps (both on premises and in the cloud)
27
Common Questions What Exchange Roles can I virtualize?
Should I virtualize the Mailbox Role? Can I virtualize with VMware, or just Hyper-V? What about virtualization snapshots? Should I use Network Load Balancing? Can I virtualize the Unified Messaging Role? Can I virtualize Lync? Is Office 365 considered virtualization?
28
Virtualization Summary
Exchange 2010: Rise Of The Hypervisors Consolidation and Resilience Are Business Drivers Exchange Heavy Resource Application, Virtual Or Not When Not To Virtualize- UM Role (Perhaps Not Enough Resources), CPU/Memory, Hypervisor Not Validated Scenarios- Virtual Disaster Recovery, Branch Office, Redundancy, Green Computing, Transition Helper
29
Thanks! Lee Benjamin ExchangeGuy Consulting www.ExchangeGuy.com
ExchangeServerBoston.org, Chairman BostonUserGroups.org, Vice President Virtualization Group (VirtG), Advisory Board GITCA.org (formerly Culminis), Director, Global Board
Similar presentations
© 2025 SlidePlayer.com Inc.
All rights reserved.