Exchange - Home - Virtualization Group
Download
Report
Transcript Exchange - Home - Virtualization Group
Lee Benjamin
ExchangeGuy Consulting
www.ExchangeGuy.com
March 2011
About Lee Benjamin
ExchangeGuy Consulting
Architecture, Migration/Upgrades, Project Guidance
ISV Advisor, Strategy, Whitepapers, Testing, Reviews
Industry Events, Speaker, Custom Training, Expert
www.ExchangeGuy.com
User Groups
www.ExchangeServerBoston.org
www.BostonUserGroups.org
www.GITCA.org
www.VirtG.com
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
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?
Exchange Server 2010 Releases
Exchange Server 2010
RTM’d October 8, 2009, GA since November 9, 2009
Hosting nearly 40 million mailboxes in the cloud!
Service Pack 1
RTM = August 21st, RTW August 23rd
At release running on…
134,000 Mailboxes in MSIT, 477,836 Mailboxes in TAP
Rollup 3 for SP1 Released March 2011
Exchange Server Roles
Exchange 2003/2000
1. Front-End
Server
2. Back-End
Server
• SMTP, POP3/IMAP4
• HTTPS
• Outlook Web Access
• Exchange ActiveSync
• Hygiene (AV/AS)
• Optional
•
•
•
•
Mailbox Databases
Routing
MAPI/Outlook
Includes Front-End
Exchange 2010/2007
1. CAS – Client
Access Server
• Client Connection Point, Required
• Including Outlook/MAPI In 2010
• More Load, = More CPU + Memory
2. HUB – Hub
Transport Role
• All Message Routing, Required
• Shadow/Resiliency In 2010
3. MBX –
Mailbox Role
• 64 Bit ESE Database
• Scalability And Performance
4. UM – Unified • Voicemail, Voice Access,
Voicemail Preview
Messaging
5. EDGE- Edge
Transport Role
• Routing and Hygiene
• Lives Alone, Optional
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)
Exchange 2010 Foundation
64bit Database
And Storage
Technologies
Virtualization
Availability and
Resilience
Designed For
On-Premises
and OnlineHosted
Compliancy and
Discovery
Functionality
Integration
With Mobility,
Voice, And
Social
Networking
Platforms
Information
Rights
Management
Exchange’s
Database
Extensible Storage Engine (ESE)
Well Known With 14 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
70% IO Reduction Over Exchange 2007
MAPI To The Middle (CAS, Finally)
Mailbox
CAS
Middle
Tier
Mailbox
Agents
OWA
Sync
Entourage
UM
Exchange
Biz Logic
Store
WS
Outlook
/ MAPI
CAS
MAPI RPC
Exchange Components
Mailbox
Agents
OWA
Sync
MAPI,
Exchange
RFR &
Biz Logic
NSPI RPC
Exchange Core Biz Logic
DAV
Mailbox
WS
Transport
Agents
Entourage
Middle
Tier
Exchange Components
Outlook
/ MAPI
MAPI RPC
Store
Performance Implications Moving Heavy Workload
Transport
Agents
UM
Management Tools
Exchange Management Console And Shell (2007)
Simplified Hierarchy
Sophisticated PowerShell Environment
All Recipient Management In EMC and EMS
Manage Users In ADUC, Messaging In Exchange
Exchange Control Panel (2010)
Delegate Tasks Through Web Interface
Distribution Groups, Tracking, Personal Info, More…
Through Outlook Web App
Roles Based Access Control
Exchange Control Panel
UI Scope
Control
Secondary
Navigation
Slab
Primary
Navigation
Backup Changes
Storage Groups Removed 2010
Store : SG Became 1:1 in 2007
Stores Owned By The Organization
Allows Database Mobility
Recover To Another Exchange Server
Recovery Database (was Recovery Storage Group)
No Streaming Backup Support
Only VSS Snapshots
From Microsoft And 3rd Parties
Backup/Restore From/To Any DAG Member
Why Restore When You’ve Got DAG Replication
Companion Archiving / Policies
Compliance and Discovery Concerns, Regulations…
Introducing Secondary Companion Mailbox
Integrated Into Outlook 2010 and OWA 2010 (Also Outlook 2007 in RU)
SP1- Same Or Different Database
Users Can Drag And Drop PST’s
Auto-Archive Policy, Transport Rules,
Message Retention
Separate Retention Policy For Archives
Legal Hold Capability
Any Kind Of Delete Will Fail
Administrator or Compliance Role To View
Third Parties Extend To Business Level Archives
Database Availability Groups
SCC, CCR, and SCR Evolution
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 Lower Cost SAS and SATA Disks in DAS
Exchange 2010 DAG Example
Three Exchange Servers
Running MBX Role
• Two In Data Center
• One At Secondary DR Location
DAG Created and 3 Mailbox
Servers Added to DAG
• Mailboxes Split Between 2 Mailbox Servers
In Primary Datacenter
3rd DAG Node In DR Site For
Site Resiliency
• Replicated DAG Will Failover or Crossover As Needed
• DR Copy Is Candidate For Virtualization
4th DAG Node In DR Site
Could Be Lagged Copy
Can Virtualize CAS and HUB
For Redundancy
• 4 Copies Allows Intra- and Cross Site Protection
• And Protection Against Potential Corruption
• 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
Message Routing
All Traffic Routes Through HUB Transports
Routing Topology Is Active Directory Sites
No Longer Exchange Routing Groups
Larger AD Topologies May Require Work
EDGE Designed for Perimeter (Optional)
Hardened SMTP, Protects AD with EdgeSync
Anti-Virus and Anti-Spam on Periphery
However, HUB Can Be Configured Direct To Internet
CPU and Memory Are Key, Minimal Disk
Add Redundancy With Additional Servers
Shadow Transport
Message Traffic In Motion Should Be Resilient
Exchange 2007
Introduced
HUB Transport
Role
And The Transport
Dumpster
Messages Recently Delivered To Clustered Mailbox Server
Exchange 2010
Introduces
Shadow
Redundancy
Maintains Copies Of Messages
Mail Not Lost During Failover
From Edge (If Used) Through HUB(s) to MBX
Until Next Hop Confirms Delivery To Next Hop
No More Emptying Queues To Take Server Offline
Redundancy
Moved To Server
Level
Of Course You Must Implement Multiple Servers
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
Coexistence
Sync AD
Microsoft Office 365
What’s New in Office 365
• 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
• 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
New user interface
Role based access
Identity federation (eliminate sign-in client)
Multi-factor authentication support
• 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
Virtualization Support
Windows Server 2008 And R2 With Hyper-V
Also Microsoft Hyper-V Server And R2
Any Third-Party Hypervisor Validated Under The
Windows Server Virtualization Validation Program
VMware, 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 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)
Single Exchange 2010 Server
Exchange Server Running CAS, HUB, and MBX Roles
Deploy This Critical Server On Physical Hardware
Resource Intensive On Its Own
Direct Attached Storage, Redundancy Through Raid
Lower Cost SAS And SATA Drives Acceptable
Though Use Storage Calculator
Consider Virtualization For Low Availability
2nd Copy of Mailbox Role In DAG
Not Actively Supporting Users
Virtualize CAS and HUB For Redundancy
Regardless Of Mailbox Role In DAG
Size Accordingly
Exchange 2010 3-Node DAG
3 Exchange Servers Running MBX Role
Two In Data Center, One At Secondary DR Location
Could Also Be Running CAS And Hub Roles*
DAG Created and 3 Mailbox Servers Added to DAG
Mailboxes Split Between 2 Mailbox Servers
DR Copy Is Candidate For Virtualization
Set Lagged Copies on 3rd DAG Node In DR Site
Replicated DAG Will Failover or Crossover As Needed
3 Copies Allows Both Intra- and Cross Site Protection
Virtualize CAS and HUB For Redundancy
Size Accordingly
Other Exchange 2010
Virtualization Scenarios
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
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?
Virtualization Summary
Exchange 2010: Rise Of The Hypervisors
Consolidation and Resilience Are Drivers
Exchange Heavy Resource Application, Virtual Or Not
When Not To Virtualize- UM Role, Not Enough Resouces
CPU/Memory, Hypervisor Not Validated
Scenarios- Virtual Disaster Recovery, Branch Office,
Redundancy, Green Computing, Transition Helper
Lee Benjamin
ExchangeGuy Consulting
www.ExchangeGuy.com
[email protected]
ExchangeServerBoston.org, Chairman
BostonUserGroups.org, Vice President
Virtualization Group (VirtG), Advisory Board
GITCA.org (formerly Culminis), Director, Global Board