Transcript Upgrading to Exchange 2013

Eesti. Baltimaad. Põhja Euroopa.
Priit Timpson
Atea teenuste osakond
Office/Lync/Exchange/SharePoint
2013
Priit Timpson
Atea teenuste osakond
Office 2013
• Modern Interface
• Touch Mode
• Reading mode
• Editing PDFs
• Excel on multiple monitors
• SkyDrive - Connect to the Cloud, Connect to
Your Content
• Outlook cache sizes, speed, .ost compression
• Etc.
Lync 2013
• Full IPv6 support
• VDI plugin, allowing full A/V support in virtual
desktop environments
• H.264 SVC codec support
• Skype federation support (coming)
• Hybrid deployments of on-premises and Lync
Online cloud servers now supported (this
capability is called "hybrid voice")
Lync 2013
• New role Office Web Apps server
• Consolidation of roles
• Director role optional not “recomended“
• A\V Conferencing always on Front-End
• Archiving and Monitoring on Front-End
(optional)
• Lync 2013 Std. also Persistent Chat on FrontEnd
Lync 2013
• Persistent Chat – alternative for distribution
lists
• With this comes also new RBAC rolePersistent
Chat Manager
Lync 2013
• Enterprise voice features – inter-trunk routing to
connect an IP-PBX and a PSTN gateway
Manager/delegate simultaneous ringing (multiple
designated phones ring at the same time)
• Lync 2013 now supports M-N trunk routing.
This allows you to have multiple trunks to different
gateways, and a gateway to have multiple trunks
to different Mediation Servers
• Hybrid voice with Lync Online
Lync 2013
• Disaster recovery and high-availability
improvements
• Reduntant roles for common pool (same as in
Lync 2010)
• No more Metropolitan Site Resilency
• New - Lync Pool pairing (Ent. with Ent.; Std.
with Std.) both sites are active.
Manual failover, failback
Lync 2013
• Lync Web App changes – Audio/Video over
browser, no more Attendee
• New Mobility client – not jet relased and no
dates. Will be supporting audio and video calls
over mobile data, wi-fi
Lync 2013
• Coexistence and Migration
• Supported are Microsoft Lync Server 2010
Microsoft Office Communications Server 2007
R2
• Migration to diffrent Forest not supported
• Public SSL, IP-s etc.
Exchange 2013
• New Architecture!
From Exchange 2010 5 server roles to 2 roles in
Exchange 2013.
Client Access Server role and Mailbox Server
role
Exchange 2013 CAS
• Domain-joined machine in the internal Active
Directory forest
– Thin, stateless (protocol session) server
• Comprised of three components:
– Client access protocols (HTTP, IMAP, POP)
– SMTP
– UM Call Router
• Exchange-aware proxy server
– Understands requests from different protocols (OWA, EWS, etc.)
– Supports proxy and redirection logic for client protocols
– Capable of supporting legacy servers with redirect or proxy logic
– Contains logic to route specific protocol requests to their destination
end-point
Client Protocol Architecture in Exchange 2013
Outlook Web App
Outlook
EAS
EAC
PowerShell
POP/IMAP
SMTP
SI
P
Load Balancer
Redirect
IIS
Client
Access
POP,
IMAP
HTTP Proxy
SMTP
SMTP
POP, IMAP
HTTP
UM
IIS
RpcProxy
RPS
RPC CA
OWA, EAS, EWS,
ECP, OAB
Mailbox
MDB
POP
IMAP
Transpor
t
MailQ
UM
SIP + RTP
Outlook Connectivity in Exchange 2013
• Exchange 2013 supports RPC/HTTP only; No RPC/TCP
– Simplifies the protocol stack
– Provides an extremely reliable and stable connectivity model
because RPC session is always on Mailbox server hosting
active copy
– Eliminates need for RPC CAS Array namespace(s)
– Eliminates end user interruptions like “The Exchange
administrator has made a change that requires you to quit
and restart Outlook” during mailbox moves
A Single Common Namespace Example
Geographical DNS Solution
Sue
Sue
(somewhere in NA)
mail.contoso.com
DNS Resolution
Round-Robin between # of VIPs
VIP #1
DAG
DNS Resolution via Geo-DNS
Round-Robin between # of VIPs
VIP #2
VIP #3
DAG
(traveling
in APAC)
VIP #4
SMTP Inbound/Outbound Mail Flow
Inbound Mail Flow
Outbound Mail Flow
1. FET accepts initial SMTP
conversation if source passes
connection filtering
1. MBX 2013 determines if mail
recipient is a remote destination
and selects a FET within local site
when the FrontEndProxyEnabled
parameter on Send Connector is
set to $true
2. Applies protocol, sender, and
recipient filtering based on
message envelope up to the
SMTP data command
3. Proxies the message to the
appropriate destination
16
2. MBX 2013 connects to FET and
initiates SMTP conversation
3. FET proxies outbound connection
to appropriate destination
Mailbox Server Role
• Server that hosts the components that process, render and
store Exchange data
– Includes components previously found in separate roles
• Only Client Access servers connect directly to the Mailbox
server
– Clients connect to Client Access servers
• Note – one exception is UM with RTP
– Connectivity to a mailbox is always provided by the protocol
instance local to the active database copy
Managed Store
• Store service process (Microsoft.Exchange.Store.Service.exe)
– Manages worker process lifetime based on mount/dismount
– Logs failure item when store worker process problems detected
– Terminates store worker process in response to “dirty” dismount during
failover
• Store worker process (Microsoft.Exchange.Store.Worker.exe)
– One process per database, RPC endpoint instance is database GUID
– Responsible for block-mode replication for passive databases
– Fast transition to active when mounted
– Transition from passive  active increases ESE cache size 5X
E2010 vs. E2013 Performance Comparison
* Results based on daily Outlook cached mode Load Generator simulations (10 databases, 1000 users) to
measure key metrics used to identify performance improvements/regressions (Beta2 build 466, subject to
change)
4
0.70
3.99
3.75
3.5
3.16
3.09
0.60
48-76% IOPS reduction
(disk IOPS capacity not
expected to change)
3
0.50
0.40
2.5
18-41% Average RPC
Latency reduction
2.35
2
0.65
1.5
0.30
0.74
1
0.5
0.20
0
0.16
0.10
RPC
AVERAGE
LATENCY
0.00
DB IOPS/MAILBOX
19
E14SP1
E15 Build 466
E14SP1
MCYCLES
PER RPC
PACKET
STORE
MEMORY
PER
MAILBOX
(MB)
E15 Build 466
17-34% increase in CPU
per RPC processed
(offset by additional CPU
cores)
~4X increase in store
memory overhead
(~4GB vs. ~1GB not
including ESE cache)
IOPS Reductions
DB IOPS/Mailbox
~99.5%
Reduction!
1
0.8
Exchange 2003
0.6
Exchange 2007
0.4
Exchange 2010
0.2
Exchange 2013
0
Exchange
2003
Exchange
2007
Exchange
2010
Exchange
2013
Support for Larger Mailboxes
• Large Mailbox Size is 100 GB+
– Aggregate Mailbox =
Primary Mailbox + Archive Mailbox +
Recoverable Items
– 1-2 years of mail (minimum)
• Increase IW productivity
• Eliminate or reduce PST files
• Eliminate or reduce third-party
archive solutions
• OST size control with Outlook
2013
1 Day
150
11 MB
1 Month
3300
242 MB
1 Year
39000
2.8 GB
2 Years
78000
5.6 GB
4 Years
156000
11.2 GB
Modern Public Folders
• Public folders based on the mailbox
architecture
• Single-master model
– Hierarchy is stored in a PF mailbox (one writeable)
– Content can be broken up and placed in multiple
mailboxes
– The hierarchy folder points to the target content
mailbox
• Because it’s a mailbox, it’s in a mailbox
database…thus,
– High availability achieved through continuous
replication
– No separate replication mechanism
• Similar administrative features to
current PFs
– No end-user changes
Public
Private
logon
logon
Public
logon
CAS2013
Hierarchy
Mailbox
MBX
2013
Content
Mailbox
MBX
2013
MBX
2013
Modern Public Folders
• 1 - User connects to their home
Public Folder mailbox first, which
should be located near their primary
mailbox.
• 2- Folder contents live in one specific
mailbox for that folder. All content
operations are redirected to the
mailbox for that folder
• 3 – Folder hierarchy changes are
intercepted and written to writeable
copy of Public Folder hierarchy
• 4 – All Public Folder mailboxes listen
for hierarchy changes and update
similar to Outlook clients
• 5 - When a Public Folder mailbox
gets full, move some folders to a new
mailbox
New Search Foundation Primer
Incoming Documents
Incoming Queries
CTS
Filter
Word
Brea
k
“CTS Flow”
IMS
Conte
nt
XForm
MAR
S
Write
r
Content
XForm
Parse
“IMS Flow”
Core
Uses Search Foundation
Significantly improved indexing
performance
Quer
y
Catalog
Significantly improved query performance
Service Availability Improvements
All core Exchange functionality for a given mailbox is served
by the MBX 2013 server where that mailbox’s database is
currently activated
Mailbox access fails over when a database fails over
Protocols shift to the server hosting the active database copy
Managed Availability: Internal monitoring and high
availability are tied together and can be used to detect and
recover from problems as they occur and are discovered
Best copy selection now includes health of services when
selecting best copy (best copy and server selection)
Failover time reductions
25
Exchange 2013 HA
• DAG
• Multiple databases per volume
• Lagged copy automatic log play down w. Safty Net
• DAG Network autoconfig
• CAS and MBX recovery independent
• Transport HA - Every message is redundantly persisted
before its receipt is acknowledged to the sender
• Etc.
26
Exchange 2013 Prerequisites
• Supported coexistence scenarios
– Exchange Server 2010 SP3*
– Exchange Server 2007 SP3 (+ coexistence RU*)
• Supported client access methods
– Outlook 2013, Outlook 2010, Outlook 2007
– RPC over HTTP is only method of connectivity for Outlook
clients
– Entourage 2008 for Mac, Web Services Edition
– Outlook for Mac 2011
Upgrading to Exchange 2013
From an existing Exchange 2007 environment
1. Prepare
Clients
Install Exchange 2007 SP3 + RU across the ORG
autodiscover.contoso.com
mail.contoso.com
3
legacy.contoso.com
2
1
E2007
SP3
CAS
E2007
SP3
HUB
4
Prepare AD with Exchange 2013 schema and validate
2. Deploy Exchange 2013 servers
5
E2013
CAS
Exchange 2007
Servers
RU
RU
RU
RU
Intranet site
Install both Exchange 2013 MBX and CAS servers
3. Create legacy namespace
Create DNS record to point to legacy Exchange 2007 CAS
4. Obtain and Deploy Certificates
Obtain and deploy certificates on Exchange 2013 CAS
servers configured with legacy namespace, Exchange
2013 namespace, and autodiscover namespace
Deploy certificates on Exchange 2007 CAS
5. Switch primary namespace to Exchange 2013 CAS
Validate using Remote Connectivity Analyzer
7
6
E2007
SP3
MBX
E2013
MBX
Internet-facing site – upgrade first
28
6. Move mailboxes
Build out DAG
Move Exchange 2007 users to Exchange 2013 MBX
7. Repeat for additional sites
Upgrading to Exchange 2013 (Cont’d)
1. Prepare
Install Exchange SP and/or updates across the org
Prepare AD with Exchange 2013 schema and
validate
Clients
autodiscover.contoso.com
mail.contoso.com
2. Deploy Exchange 2013 servers
1
3. Create legacy namespace
E2010
or 2007
HUB
E2010
or 2007
CAS
Exchange 2010
or 2007 Servers
SP/RU
SP/RU
E2010
or 2007
MBX
Internet facing site – Upgrade first
29
Intranet site
4. Obtain and deploy certificates
5. Switch primary namespace to Exchange 2013 CAS
6. Move mailboxes
7. Repeat for additional sites
Public Folder Migration Process
• Analyze existing Public Folders
– Tool available to analyze existing Public Folder hierarchy to determine
how many Exchange 2013 Public Folder mailboxes are recommended
• Copy Public Folder data
– Users continue to access existing Public Folder deployment while data is
copied
– Data migration happens in the background
• Switch clients to Exchange 2013 Public Folders
– There will be a short downtime while the migration is finalized
Once migration completes, everyone switches at the same time
– Can switch back, but any post migration Public Folder changes are lost
Exchange 2013
• Archiving
• eDiscovery
• Integration with ohter MS 2013 products
• Hybrid
• Data Loss Prevention (DLP – identify, monitor,
protect)
• OWA – Touch Mode, Offline
• Etc.
Questions/Küsimused?
Tänan!
Priit Timpson
Atea Eesti
Systems Engineer