©2011 ExchangeGuy Consulting
Exchange 2010 and Virtualization
VirtG’s Deep Dive DayLee Benjamin
ExchangeGuy Consultingwww.ExchangeGuy.com
March 2011
©2011 ExchangeGuy Consulting
About Lee BenjaminExchangeGuy Consulting
Architecture, Migration/Upgrades, Project GuidanceISV Advisor, Strategy, Whitepapers, Testing, ReviewsIndustry Events, Speaker, Custom Training, Expertwww.ExchangeGuy.com
User Groupswww.ExchangeServerBoston.org www.BostonUserGroups.org www.GITCA.org www.VirtG.com
©2011 ExchangeGuy Consulting
Agenda
• Architectural Foundation of Exchange 2010• Exchange Server Roles• Foundation Technologies
• Virtualization and Exchange• Generalities, Hyper-V• Common Questions
• ExchangeGuy’s Virtual Environment• Remote Demo
©2011 ExchangeGuy Consulting
Common QuestionsWhat 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?
©2011 ExchangeGuy Consulting
Exchange Server 2010 ReleasesExchange Server 2010
RTM’d October 8, 2009, GA since November 9, 2009
Hosting nearly 40 million mailboxes in the cloud!
Service Pack 1RTM = August 21st, RTW August 23rd At release running on…
134,000 Mailboxes in MSIT, 477,836 Mailboxes in TAPRollup 3 for SP1 Released March 2011
©2011 ExchangeGuy Consulting
Exchange Server RolesExchange 2003/2000
• 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
Exchange 2010/2007• 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
• Voicemail, Voice Access, Voicemail Preview
4. UM – Unified Messaging
• Routing and Hygiene• Lives Alone, Optional
5. EDGE- Edge Transport Role
Exchange 2010 Architecture
ExternalSMTP
serversMailbox
Storage of mailbox items
Edge TransportRouting &
AV/AS
Unified MessagingVoice mail & voice access
Phone system (PBX or VOIP)
Client AccessClient
connectivityWeb services
Hub TransportRouting & Policy
Web browserOutlook
Anywhere(remote
user)
Mobile phone
Outlook (local user)
Line of business application
©2011 ExchangeGuy Consulting
Exchange 2010 Foundation64bit
Database And Storage
TechnologiesCompliancy
and Discovery
FunctionalityIntegration
With Mobility,
Voice, And Social
Networking Platforms
Information Rights
Management
Designed For On-Premises and Online-
Hosted
Availability and
Resilience
Virtualization
©2011 ExchangeGuy Consulting
Exchange’s DatabaseExtensible Storage Engine (ESE)
Well Known With 14 Years In Production64bit 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 MailboxesTables vs. Mailboxes, SIS Casualty, Storage Groups
GoneDatabase Page Repair From Replicated Copy (Lagged)
90% IO Reduction Over Exchange 200370% IO Reduction Over Exchange 2007
MAPI To The Middle (CAS, Finally)M
iddl
eTi
er
Exchange Biz Logic
Mai
lbo
x
MAPI RPC
Store
Exchange Components
OWA
SyncUM
Transport Agents
Mailbox Agents
WS Entourage
Outlook / MAPI
DAV
Mid
dle
Tier
MAPI, RFR &
NSPI RPC
Exchange Core Biz Logic
Exchange Biz Logic
Mai
lbox MAPI RPC
Store
Exchange Components
OWA
SyncUM
Transport Agents
Mailbox Agents
WSOutlook / MAPI
Entourage
Exchange 2007 Exchange 2010
Performance Implications Moving Heavy Workload
CAS CAS
©2011 ExchangeGuy Consulting
Management ToolsExchange Management Console And Shell
(2007)Simplified HierarchySophisticated PowerShell EnvironmentAll Recipient Management In EMC and EMSManage Users In ADUC, Messaging In
Exchange
Exchange Control Panel (2010)Delegate Tasks Through Web InterfaceDistribution Groups, Tracking, Personal Info,
More…Through Outlook Web AppRoles Based Access Control
Exchange Control Panel
Primary Navigati
on
UI Scope Control
Secondary
Navigation
Slab
Backup ChangesStorage Groups Removed 2010
Store : SG Became 1 : 1 in 2007Stores Owned By The OrganizationAllows Database Mobility
Recover To Another Exchange Server Recovery Database (was Recovery Storage Group)
No Streaming Backup SupportOnly VSS SnapshotsFrom Microsoft And 3rd Parties
Backup/Restore From/To Any DAG MemberWhy Restore When You’ve Got DAG Replication
©2011 ExchangeGuy Consulting
Companion Archiving / PoliciesCompliance and Discovery Concerns, Regulations…Introducing Secondary Companion Mailbox
Integrated Into Outlook 2010 and OWA 2010 (Also Outlook 2007 in RU)
SP1- Same Or Different DatabaseUsers Can Drag And Drop PST’s
Auto-Archive Policy, Transport Rules,Message RetentionSeparate Retention Policy For Archives
Legal Hold CapabilityAny Kind Of Delete Will Fail
Administrator or Compliance Role To ViewThird Parties Extend To Business Level Archives
©2011 ExchangeGuy Consulting
Database Availability GroupsSCC, CCR, and SCR EvolutionNo Clustering Knowledge Required
Windows Server Clustering Underneath For Heartbeat
From 2 To 16 Replicas, Multiple Active NodesAll Managed Inside Exchange
Exchange Management Console or ShellRecommend 3-4 Node DAGs, Or Larger (2
with SP1)Allows Lower Cost SAS and SATA Disks in
DAS
©2011 ExchangeGuy Consulting
Exchange 2010 DAG Example• Two In Data Center• One At Secondary DR Location
Three Exchange Servers Running MBX Role
• Mailboxes Split Between 2 Mailbox ServersIn Primary Datacenter
DAG Created and 3 Mailbox Servers Added to
DAG
• Replicated DAG Will Failover or Crossover As Needed
• DR Copy Is Candidate For Virtualization3rd DAG Node In DR
Site For Site Resiliency
• 4 Copies Allows Intra- and Cross Site Protection• And Protection Against Potential Corruption
4th DAG Node In DR Site Could Be Lagged Copy
• If CAS/HUB on MBX Server, Need External Load Balancer, Not Microsoft’s Software NLB (Thinks Its A Cluster)
• Size Accordingly- Plan For Fail/Crossover Load On Servers
Can Virtualize CAS and HUB For Redundancy
©2011 ExchangeGuy Consulting
Message RoutingAll Traffic Routes Through HUB TransportsRouting Topology Is Active Directory Sites
No Longer Exchange Routing GroupsLarger AD Topologies May Require Work
EDGE Designed for Perimeter (Optional)Hardened SMTP, Protects AD with EdgeSyncAnti-Virus and Anti-Spam on PeripheryHowever, HUB Can Be Configured Direct To
InternetCPU and Memory Are Key, Minimal DiskAdd Redundancy With Additional Servers
©2011 ExchangeGuy Consulting
Shadow Transport
Message Traffic In Motion Should Be Resilient
Exchange 2007 IntroducedHUB Transport RoleAnd The Transport Dumpster
Messages Recently Delivered To Clustered Mailbox Server
Mail Not Lost During Failover
Exchange 2010 Introduces Shadow Redundancy
Maintains Copies Of MessagesFrom Edge (If Used) Through HUB(s) to MBXUntil Next Hop Confirms Delivery To Next HopNo More Emptying Queues To Take Server Offline
Redundancy Moved To Server Level Of Course You Must Implement Multiple Servers
©2011 ExchangeGuy Consulting
Transition: Deployment Assistant
http://technet.microsoft.com/exdeploy2010
Remote Connectivity Analyzer https://www.
testexchangeconnectivity.com/ Test
Exchange ActiveSync (EAS) Outlook Anywhere
(RPC/HTTP) Autodiscover SMTP …More Will Come…
Use It Every Step Of Transition
Living With The Cloud- HybridCoexistence
Sync AD
On-Premises
Seamless User Experience
Cloud Services
Microsoft Office 365BRINGING TOGETHER CLOUD VERSIONS OF MICROSOFT’S COMMUNICATIONS
AND COLLABORATION PRODUCTS WITH THE LATEST VERSION OF OUR DESKTOP SUITE FOR BUSINESSES OF ALL SIZES.
22
What’s New in Office 365
• New user interface• Role based access• Identity federation (eliminate sign-in client)• Multi-factor authentication support
PlatformCapabiliti
es
• 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
• 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
• Voicemail with unified messaging
• Integrated personal archiving
• Retention policies and legal hold
• Exchange Control Panel
• Free/busy coexistence
• Cross-premises management
• 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
23
Virtualization SupportWindows Server 2008 And R2 With Hyper-VAlso Microsoft Hyper-V Server And R2Any Third-Party Hypervisor Validated Under
The Windows Server Virtualization Validation ProgramVMware, Other
Any Exchange 2010 Role Except Unified Messaging (UM)
Must Use Fixed Size Virtual Storage Disks, or SCSI Pass-Through Physical Disks, or iSCSI SAN Disks
No Differencing Disks, No Hypervisor Snapshots
Only Virtualization And Management SW On Host
Virtual Concerns9-12% Overhead For Hypervisor
Plan For 10% Less UsersSame CPU and Memory Requirements As
PhysicalSavings May Not Be There
Scale Out Rather Than Scale UpConscious Decision From Exchange TeamSpread The Load And RiskMore Servers And Replicated Copies (DAGs)
Exchange Server Running CAS, HUB, and MBX RolesDeploy This Critical Server On Physical Hardware
Resource Intensive On Its OwnDirect Attached Storage, Redundancy Through Raid
Lower Cost SAS And SATA Drives AcceptableThough Use Storage Calculator
Consider Virtualization For Low Availability2nd Copy of Mailbox Role In DAG
Not Actively Supporting UsersVirtualize CAS and HUB For Redundancy
Regardless Of Mailbox Role In DAGSize Accordingly
Single Exchange 2010 Server
Exchange 2010 3-Node DAG3 Exchange Servers Running MBX Role
Two In Data Center, One At Secondary DR LocationCould Also Be Running CAS And Hub Roles*
DAG Created and 3 Mailbox Servers Added to DAGMailboxes Split Between 2 Mailbox Servers
DR Copy Is Candidate For VirtualizationSet Lagged Copies on 3rd DAG Node In DR SiteReplicated DAG Will Failover or Crossover As Needed3 Copies Allows Both Intra- and Cross Site Protection
Virtualize CAS and HUB For Redundancy Size Accordingly
Other Exchange 2010 Virtualization ScenariosBranch Office
Streamlined Provisioning To Smaller OfficesDistributed DR Sites
Around The WorldDR Sites With Lagged Copies
Log Files Are ReplicatedDelayed Insert Into Database (Hours, Days)If Major Corruption, Remove Troubled Log Before
Transition HelperCAS/HUB 2007 And CAS/HUB 2010
Common QuestionsWhat 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?
Virtualization SummaryExchange 2010: Rise Of The Hypervisors
Consolidation and Resilience Are Drivers
Exchange Heavy Resource Application,
Virtual Or NotWhen Not To Virtualize- UM Role,
Not Enough Resouces CPU/Memory,
Hypervisor Not Validated
Scenarios- Virtual Disaster Recovery,
Branch Office, Redundancy, Green
Computing, Transition Helper
©2011 ExchangeGuy Consulting
THANKS!Lee Benjamin
ExchangeGuy Consultingwww.ExchangeGuy.com
ExchangeServerBoston.org, ChairmanBostonUserGroups.org, Vice President
Virtualization Group (VirtG), Advisory BoardGITCA.org (formerly Culminis), Director, Global Board