Exchange High Availability Solution
Architecture Design Session
Name
Title
Microsoft
Architecture Design Session
Solution
Briefing
Summary
Vision scope
input from
solution
briefing
Solution
Overview
Technology
Overview
VPC-based
demo
Point out
technologies
for relevant
capabilities
Web –based
demo
View the
capabilities in
action
Show various
possibilities
Discuss
technologies
Architecture
Discussion
Discuss
Architecture
Decision Points
POC
Planning
Develop scope
and
specifications
for POC
Architecture Design Session
Solution
Briefing
Summary
Vision scope
input from
solution
briefing
Summary of Pains and Drivers
Challenges
•
•
•
Service downtime disrupts
business operations and reduce
productivity
Achieving high availability for all
types of communication is
expensive
Protection against Site-level
Disasters
Business Drivers
•
•
•
•
Meeting stringent SLAs
Accelerate productivity
Ensure business continuity
Reduce IT cost
Technical Requirements
•
•
•
Easy to Deploy and Manage
Deliver a high-value hosted continuity service
Provide IT control with failover, redundancy, and scalability across your
organization
Architecture Design Session
Solution
Briefing
Summary
Vision scope
input from
solution
briefing
Solution
Overview
VPC-based
demo
Web –based
demo
View the
capabilities in
action
Show various
possibilities
Communications Today
Instant
Messaging (IM)
Unified Inbox
& Presence
Voice Mail
Video
Conferencing
Telephony
and
Voice Mail
User
Experienc
e
Authentication
User
E-mail and
Calendaring
Web
Conferencing
Unified
Conferencing:
Audio, Video,
Web
User
User
User
Experienc
e
Authentication
Authentication
Administration
Administration
Storage
Authentication
Administration
Storage
Audio
Conferencing
User
Experience
Experienc
e
Authentication
E-mail and
Calendaring
Instant
Messaging
Experienc
e
Administration
Storage
Telephony
Storage
User
Experienc
e
Administration
Storage
Authentication
Authentication
Administration
Administration
Storage
Compliance
On-Premises or in the Cloud
Storage
Experienc
e
Authentication
Administration
Storage
Microsoft Unified Communications
Increased productivity through communications convergence
Across Devices
PC, Mobile, Web
Increase
Efficiency and
Flexibility
Streamline
Communications
Amplify Protection
and Control
Unified Identity,
Presence, and Inbox
Authentication
Administration
Storage
Compliance
Provide a Unified
and Extensible
Platform
Maximize IT
Resources
with S+S
On-Premises or in the Cloud
Scenarios
Microsoft UC Products and Services
E-Mail and Security and
Calendaring Compliance
VoIP
Conferencing
E-mail Security,
IM and
Compliance, and Presence
Continuity
Mobility
Delivery
Products
Unified
Messaging
On Premise
Hosted by Microsoft
Hosted by Microsoft or by Partners
Hosted by Partners
UC Journey Through Infrastructure
Optimization
identify
where
you want
to be
identify
where
you are
Basic
Standardized
Rationalized
Dynamic
Basic e-mail, file
shares, mostly
phone based
communication
Standard platform
for secure e-mail
and IM
Ad hoc teaming
around functions &
projects based on IT
standards
Increasing
unification of
communication
channels
Fully managed
collaboration
platform and
pervasive access
Seamless
collaboration across
the firewall
Federation of
communication
information and
policy
IT is an
Efficient cost center
IT is a
business enabler
IT is a
strategic asset
IT is a
cost center
Identifying Target Maturity Level
Voice
Conferencing
IM &
Presence
Messaging
Basic
Standardized
Rationalized
Basic email with no remote Rich mailbox & calendaring
access and with limited
Secure, remote, online &
security
offline access
Minimal or decentralized
Basic AV/AS/AP protection
IT support
and disaster recovery
User inboxes are fully
Solution supports encryption
managed by IT
Business continuity with
AS/AP and multi-layer AV
protection
Public IM/online
presence, ad-hoc use for
daily business
Secure IM/online presence
accessible from a variety of
devices and integrated into
enterprise productivity &
collaboration platform
Secure access from inside
& outside the firewall
Supports peer-to-peer voice
& video communications
Presence enabled email
client
Sporadic use of audio &
web conferencing
Limited video
conferencing capabilities
Secure web conferencing
accessible from remote
locations and devices
IT-managed video
conferencing with limited
remote access
Legacy TDM PBX,
traditional phones
Highly available hybrid
telephony infrastructure
Limited voice mail and
call routing
Online & offline access to
voice mail
Managed call routing
Support advanced policydriven message controls
Provisioning for user
inboxes
Dynamic
Seamless business continuity
with multiple AV/AS protection
Advanced policy control to
mobile devices & applications
Integration with LOB
applications
Federation of calendar
Supports federation and
integration with LOB
applications
Persistence group chat
Integrated & secure
conferencing platform
Supports high-quality audio
& video
Remotely accessible
collaboration features
Encrypted voice infrastructure
with unified inbox accessible
from PCs, phones, & web
browsers
Managed storage
Presence-based call routing
Contextual unified
conferencing solution tightly
integrated with collaboration
infrastructure and LOB
applications
Integrated voice platform for
IM/presence; conferencing
with LOB applications
Auto-remediation, proactive
monitoring of call quality
Federated identity and
presence-based call routing
High Availability
Unified Communication
High Availability Overview
Exchange High Availability technologies
1.
2.
3.
Primarily designed to protect Exchange mailbox data
(Mailbox server role)
Add redundancy to provide HA for service roles (UM,
CAS, HT, Edge)
Remember that:
1.
2.
High Availability is automatic failovers
Site Resilience is manual failovers!
Exchange Server 2010 High Availability
Goals
Reduce complexity
Reduce cost
Native solution - no single point of failure
Improve recovery times
Support larger mailboxes
Support large scale deployments
Exchange Server Improvements
Improved mailbox uptime
•
•
•
•
•
•
Improved failover granularity
Simplified administration
Incremental deployment
Unification of CCR + SCR
Easy stretching across sites
Up to 16 replicated copies
More storage flexibility
• Further Input/Output (I/O) reductions
• RAID-less/JBOD support
Better end-to-end availability
• Online mailbox moves
• Improved transport resiliency
Key Benefits
 Easier and cheaper to deploy
 Easier and cheaper to manage
 Better Service Level
Agreements (SLAs)
 Reduced storage costs
 Larger mailboxes
 Easier and cheaper to manage
 Better SLAs
Lync Server 2010 High Availability
and Resiliency Goals
Reduce complexity
Reduce cost
Native solution - no single point of failure
Resilient Voice Service
Support large scale deployments
High Availability
Resiliency architecture
Branch office resiliency
Data Center resiliency
Architecture Design Session
Solution
Briefing
Summary
Vision scope
input from
solution
briefing
Solution
Overview
Technology
Overview
VPC-based
demo
Point out
technologies
for relevant
capabilities
Web –based
demo
View the
capabilities in
action
Show various
possibilities
Discuss
technologies
Exchange Server 2010 Deployment Model
Role based Deployment
Enterprise Network
Edge Transport
Routing and
AV/AS
Phone system
(PBX or VOIP)
Hub Transport
Routing and policy
External
SMTP
servers
Mobile phone
Web browser
Mailbox
Storage of
mailbox items
Unified Messaging
Voice mail and
voice access
Client Access
Client connectivity
Web services
Outlook (remote
user)
Line of business
application
Outlook (local user)
Exchange High Availability Technologies
Continuous Replication technology
Mailbox
Server 1
Mailbox
Server 2
Mailbox
Server 3
Mailbox
Server 4
Mailbox
Server 16
Leverages on-site data replication (CCR) and off-site data
replication (SCR) and combines into a single framework
called a “Database Availability Group.”
Removes the need of managing Failover Clustering
separately
Reduces the need for multiple servers to achieve high
redundancy in small deployments – Two Servers can provide
full redundancy
Simplified recovery from a variety of failures (disk-level,
server-level, and datacentre-level)
Can be deployed with cheaper storage types
Exchange High Availability Technologies
Mailbox Resiliency
San Jose
Recover quickly
from disk and
database failures
DB1
DB2
DB3
DB4
DB5
DB1
DB2
DB3
DB4
DB5
New York
DB1
DB2
DB3
DB4
DB5
Replicate databases
to remote datacenter
Evolution of Continuous Replication technology
Provides full redundancy of Exchange roles on as few as two servers
Reduce backup frequency through up to 16 replicas of each database
Single solution for High Availability, Disaster Recovery, and Backup
Simplified administration reduces complexity
Built-in features for mailbox recovery
Improved availability
Can be deployed on a range of storage options
Exchange High Availability Technologies
Mailbox Resiliency Overview
AD site: Dallas
Clients connect
via CAS servers
DB1
DB3
DB5
AD site:
San Jose
Easy to stretch
across sites
Failover
managed within
Exchange
DB1
DB4
DB2
DB5
DB3
DB2
DB5
DB3
DB1
DB4
DB3
DB1
DB4
DB2
DB5
Database centric failover
Exchange High Availability Technologies
Mailbox Resiliency Components
Database Availability Group (DAG)
Mailbox Servers
RPC Client
Access
Service
Mailbox Database Copies
AM
Client
Active Manager
RPC Client Access Service
Database Availability Group
Active Manager Client
Active
Manager
Active
Manager
Active
Manager
DB1
DB1
DB1
DB2
DB2
DB2
DB3
DB3
DB3
Exchange High Availability Technologies
DAG (Database Availability Group) & Mailbox Servers
Database Availability Group
A group of up to 16 mailbox
servers that host a set of
replicated databases
Wraps a Windows® Failover
Cluster
Defines the boundary of
replication and failover/
switchover (*over)
Database Availability Group
DB1
DB1
DB1
DB2
DB2
DB2
DB3
DB3
DB3
Mailbox Servers
Host the active and passive copies of multiple mailbox
databases
Support up to 100 databases per server
Exchange High Availability Technologies
Mailbox Database Copies
Database names are
unique across an forest
Up to 16 copies of each
database
Each database has one
Active copy in a DAG
Each server hosts only
one copy of a database
Replication using Log Shipping
System tracks health of each copy
Exchange High Availability Technologies
Continuous Replication
Replication Log Buffer
ESE Log Buffer
Database
Database
available
behind
on logs
for log
(e.g Server
replication
Reboot)
Log
File 6
Log
File 3
Log
Log
File
File 44
Log
File 1
Log
File 2
Log
File 6
Log
File 7
Log
File 1
Log
File 2
Log
File 5
Continuous Replication – Block
File Mode
Mode
Exchange High Availability Technologies
Active Manager
Selects the “best” copy to activate when the active mailbox
database fails
30-second database failover
Process which runs on every server in DAG
Provides definitive information on where a database is
active and mounted
Active Directory® is primary source for configuration
information
Active Manager is primary source for changeable state
information such as active and mounted
Active Manager Client runs on CAS and HUB Servers
Exchange High Availability Technologies
Achieving double resiliency
•
•
•
Single Site
4 Nodes in a DAG
3 Database Copies
•
•
•
•
Upgrade server 1
Server 2 fails
Server 1 upgrade is done
2 active copies die
CAS NLB Farm
Mailbox
Server 1
Mailbox
Server 2
Mailbox
Server 3
Mailbox
Server 4
DB1
DB2
DB3
DB7 DB8 DB1
DB5 DB6 DB7
DB3 DB4 DB5
DB4
DB5 DB6
DB2 DB3 DB4
DB8 DB1 DB2
DB6 DB7 DB8
Database Availability Group (DAG)
Exchange High Availability Technologies
Resiliency across datacenters - Built-in site resiliency
Same deployment and
management tools as High
Availability in a single
datacenter
No stretched subnet
networking requirements
Improved process to
prevent “Split Brain”
Database Availability
Group
Simplified standby
datacenter validation
Faster datacenter
switchover process
Fewer resources required
for datacenter resiliency
No Client re-configuration
required to access
databases in standby
datacenter
Support for 2 node
datacenter resilient
topologies
Two node DAGs can use
Datacenter Activation
Coordination (DAC) mode
DAC mode available to
single site configurations
Exchange High Availability Technologies
Incremental Deployment - Reduces cost & complexity
Datacenter 1
Mailbox servers in
a DAG can host
other Exchange
2010 roles
Datacenter 2
Database Availability Group
DB1
DB1
DB1
DB2
DB2
DB2
DB3
DB3
DB3
Easy to add high availability to existing deployment
High availability configuration is post-setup
Exchange High Availability Technologies
RPC Client Access Server
MAPI clients e.g. Microsoft Office
Outlook connecting from inside the
Organization Firewall no longer
connects to Mailbox Server
MAPI clients connects to Client
Access Server for mailbox and
directory access
Client Access Server Array to be
deployed to provide high availability
and redundancy
Provides a better client experience
when failover occurs
Allows a higher number of concurrent
connections and a higher number of
mailboxes per server
Outlook Clients
Exchange CAS Array
MBX
GC
High Availability During Failures
Keeping users connected
Client
Client Access
Server failure…..
Client reconnects
through another
Client Access
Server
Mailbox Database or
Server failure…..
Load Balanced Client Access Servers
DB1
Client disconnected
for <30 seconds
DB1
DB2
DB3
Mailbox Servers
Database Availability Group
DB2
DB3
High Availability During Moves
Keeping users connected
Email Client
Client Access Server
Users remain online while
their mailboxes are moved
between servers
Sending messages
Receiving messages
Accessing entire mailbox
Administrators can
perform migration and
maintenance during
regular hours
Mailbox Server 1
Mailbox Server 2
Exchange High Availability Technologies
Transport Resiliency
Provides resilience and simplifies recovery from a transport server
failure
Provide redundancy for messages for the entire time they're in transit
Message in Transport Database gets deleted only after it verifies that
all of the next hops for that message have completed delivery
Easy maintenance of Hub Transport or Edge Transport server
Eliminates the need for storage hardware redundancy for transport
servers
Message flow with shadow redundancy
High Availability - Email in transit
Automatic protection against loss of queued email due to hardware
failure
Servers keep “shadow copies” of items
until they are delivered to the next hop
Simplifies Hub and Edge Transport Server upgrades and
maintenance
Exchange High Availability Technologies
Backup Using Exchange 2010
Reason for
Backup
Recovery
Feature
Exchange 2010
Feature Benefit
Fast
Recovery
•
•
Fast recovery
Data redundancy
Data
Retention
•
Guaranteed item
retention
•
Past point-in-time
database recovery
•
Secondary mailbox for
older data
Exchange High Availability Technologies
Exchange Hosted Services Continuity
Offsite, Microsoft-maintained business continuance
30-day rolling archive of online email stored offsite
Full Web and Outlook access
Message archive is encrypted and only accessible to
authorized users
Automated failover when your site goes down
Multiple vendors used for message hygiene
Exchange High Availability
Simplified Administration - Reduces cost & complexity
High Availability administration
all within Exchange 2010
Exchange Management Console
for common tasks
Exchange Management Shell
(PowerShell)
Mailbox Databases managed at
Organizational Level
Same automated database
failover process used for a
range for failures—disk, server,
network
Simplified activation of
Exchange 2010 services in a
standby datacenter
Additional Tools
provided to simplify
management
Active mailbox database
redistribution
DAG Maintenance Mode
Single Copy Alert
Failover Metrics
Reporting (Improved)
DAG property page
supports static
IP address specification
Exchange High Availability
Simplified Administration – Managing Availability
1
Select a database
2
View locations and status of
replicated copies
3
Take action (add copies,
change master, etc.)
Architecture Design Session
Solution
Briefing
Summary
Vision scope
input from
solution
briefing
Solution
Overview
Technology
Overview
VPC-based
demo
Point out
technologies
for relevant
capabilities
Web –based
demo
View the
capabilities in
action
Show various
possibilities
Discuss
technologies
Architecture
Discussion
Discuss
Architecture
Decision Points
High Availability Scenarios
Small Deployment
IT assets are located at a single
site. Customers has requirement
of higher uptime with lower cost.
Additionally the customer has the
following concerns:
Protection against Server/Disk
failure
Protection against Database
failure
Connection failure – Consider
where messages go if you are
offline
Data loss – Consider the
impact of lost messages,
Archiving and regulatory
impact of retention
Site loss – Plan for site failure,
what do you need to recover?
High Availability Scenarios
Medium Deployment
IT assets are located at a number of
different sites. The customers has
high uptime requirements.
Additionally the customer has the
following concerns:
Protection against Server/Disk
failure
Protection against Database
failure
Connection failure – Evaluate
redundant links, and routing
impacts
Data loss – Consider site
replication, Archiving and offsite
backup requirements
Site loss – Consider a hosted
standby, or site replication
High Availability Scenarios
Large Deployment
IT assets are located at a
number of different sites often
times in data centre-grade
facilities. The customer has high
uptime requirements.
Additionally the customer has the
following concerns:
Server failure – Implement
DAG with extended nodes in
other sites
Connection failure – Have
redundant links to the internet
and between sites
Data loss – Consider site
replication, Archiving and
offsite backup requirements
Site loss – Create site failover
plans
Architecture Decision Points
Current
Infrastructure
• Current High Availability
technologies
Future
Infrastructure
• Future High Availability needs
and goals
Deployment
• Basic deployment planning
Architecture Decision Points
Current Infrastructure
What are the currently implemented high
availability technologies?
What is the current network and office topology?
What are the company drivers and requirements
for high availability?
What are the current site resiliency goals?
Architecture Decision Points
Future Infrastructure
What are the future plans for the network and office
topology?
What are the expansion expectations for the next six
months, a year, two years, and five years?
What level of high availability is needed?
Does everyone need the same level of service?
How will you address business continuance/site loss? Do
you want to do it all in-house or outsource some of or all
of it?
Architecture Decision Points
Deployment
How can you prepare now to meet your future high
availability needs?
Will you upgrade existing systems or implement all new
systems?
Exchange rely on Active Directory so it needs to be made
highly available as well
Exchange Hosted Services provides a quick, easily
implemented HA solution for site loss and business
continuance
DAG spanned to multiple nodes and multiple hub and
CAS servers for Microsoft Exchange
Architecture Design Session
Solution
Briefing
Summary
Vision scope
input from
solution
briefing
Solution
Overview
Technology
Overview
VPC-based
demo
Point out
technologies
for relevant
capabilities
Web –based
demo
View the
capabilities in
action
Show various
possibilities
Discuss
technologies
Architecture
Discussion
Discuss
Architecture
Decision Points
POC
Planning
Develop scope
and
specifications
for POC
POC Planning
Sponsor Name
Project Timing
Goals and Objectives
Scope
Milestones
Risks & Dependencies
Next Steps
  
Solution
Development
Solution
Briefing
Architecture
Design
Session
Proof of
Concept
Proof of Concept
•Assemble resources from the business
side and from the IT group
•Understand business processes that are
being addressed
•Gain knowledge about technology
infrastructure
•Verify the technology roadmap
•Review the POC scope and assumptions
© 2007 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.
Appendix Slides…
Exchange High Availability Technologies
Creating Redundant Environment
Multiple Unified Messaging Servers can be deployed in a dial plan to
achieve the resiliency and high availability
IP Gateways can be set up to route calls in a round-robin manner to
balance the load between multiple UM servers in a dial plan and
detect UM server failure
Multiple Edge Transport Servers can be deployed to provide
redundancy and failover capabilities
Multiple HUB Transport Servers can be deployed to provide
redundancy and load distribution
Multiple Client Access Servers can be deployed in Client Access
Array to provide redundancy and prevents single Points of failures
Create Database Availability Group (DAG) with multiple copies of
database
Create Database Availability Group (DAG) that span multiple Mailbox
servers
Lync Server High Availability Technologies
Creating Redundant Environment
Instant Messaging
Enterprise Edition: Multiple Front-End Server, Array of Edge Servers
Web Conferencing
Enterprise Edition: Multiple Front-End Servers, Array of Edge Servers
Voice
Multiple Mediation Servers and Gateways
Multiple voice routes
Web Based IM/PA
Load balance multiple Exchange 2010 CAS Servers
Monitoring Server
Clustered SQL database
Archiving Server
Clustered SQL database
Persistent Group Chat
Multiple Group Chat Servers in a pool
Site Resilience
Namespace, Network and Certificate Planning
Planning for site resilience
Namespaces
Each datacenter is considered active and needs their
own namespaces
Each datacenter needs the following namespaces
OWA/OA/EWS/EAS namespace
POP/IMAP namespace
RPC Client Access namespace
SMTP namespace
In addition, one of the datacenters will maintain the
Autodiscover namespace
Planning for site resilience
Namespaces
Best Practice: Use Split DNS for Exchange hostnames
used by clients
Goal: minimize number of hostnames
mail.contoso.com for Exchange connectivity on
intranet and Internet
mail.contoso.com has different IP addresses in
intranet/Internet DNS
Important – before moving down this path, be sure to map
out all host names (outside of Exchange) that you want to
create in the internal zone
Planning for site resilience
Namespaces
External
DNS
External
DNS
Mail.contoso.com
Pop.contoso.com
Imap.contoso.com
Autodiscover.contoso.co
m
Smtp.contoso.com
Mail.region.contoso.com
Pop.region.contoso.com
Imap.region.contoso.com
Smtp.region.contoso.com
Exchange
Config
Exchange
Config
ExternalURL =
mail.contoso.com
CAS Array =
outlook.contoso.com
OA endpoint =
mail.contoso.com
Internal DNS
Mail.contoso.com
Pop.contoso.com
Imap.contoso.com
Autodiscover.contoso.co
m
Smtp.contoso.com
Outlook.contoso.com
Datacenter 1
CAS
AD
HT
MBX
Datacenter 2
HT
MBX
CAS
AD
ExternalURL =
mail.region.contoso.com
CAS Array =
outlook.region.contoso.co
m
OA endpoint =
mail.region.contoso.com
Internal DNS
Mail.region.contoso.com
Pop.region.contoso.com
Imap.region.contoso.com
Smtp.region.contoso.com
Outlook.region.contoso.co
m
Planning for site resilience
Network
Design High Availability for Dependencies
Active Directory
Network services (DNS, TCP/IP, etc.)
Telephony services (Unified Messaging)
Backup services
Network services
Infrastructure (power, cooling, etc.)
Planning for site resilience
Network
Latency
Must have less than 250 ms round trip
Network cross-talk must be blocked
Router ACLs should be used to block traffic between
MAPI and replication networks
If DHCP is used for the replication network, DHCP can
be used to deploy static routes
Lower TTL for all Exchange records to 5 minutes
OWA/EAS/EWS/OA, IMAP/POP, SMTP, RPCCAS
Both internal and external DNS zone
Planning for site resilience
Certificates
Certificate Type
Pros
Cons
Wildcard Certs
•One cert for both sides
•Flexible if names change
•Wildcard certs can be expensive, or
impossible to obtain
•WM 5 clients don’t work with wildcard
certs
•Setting of Cert Principal Name to
*.company.com is global to all CAS in
forest
Intelligent Firewall
•Traffic is forwarded to the
‘correct’ CAS
•Requires ISA or other firewall which can
forward based on properties
•Additional hardware required
•AD replication delays affect publishing
rules
Load Balancer
•Load Balancer can listen for both
external names and forward to the
‘correct’ CAS
•Requires multiple certificates
•Requires multiple IP’s
•Requires load balancer
Same Config in Both
Sites
•Just an A record change required
after site failover
•No way to run DR site as Active during
normal operation
Manipulate Cert
Principal Name
•Minimal configuration changes
required after failover
•Works with all clients
•Setting of Cert Principal Name to
mail.company.com is global to all CAS in
forest
Planning for site resilience
Certificates
Best practice: minimize the number of certificates
1 certificate for all CAS servers + reverse proxy + Edge/Hub
Use Subject Alternative Name (SAN) certificate which can cover
multiple hostnames
If leveraging a certificate per datacenter, ensure
the Certificate Principal Name is the same on all
certificates
Outlook Anywhere won’t connect if the Principal Name
on the certificate does not match the value configured in
msstd: (default matches OA RPC End Point)
Set-OutlookProvider EXPR -CertPrincipalName
msstd:mail.contoso.com