Embed Size (px)
Citation preview
Exchange 2010 – o com to bude ?
Tato prezentacia bude pre ludi co uvazuju nadprechodom na novy Exchange…
zopar otazok
1. Uvazujete nad prechodom na Exchange 2010 ?
2. Je tu niekto kto nema v sucasnosti Exchange ?
3. Mate implementovany predchadzajuci Exchange HA ? Uvazujete nad vysokou dostupnostou EXCH2010 ?
4. Ma niekto z Vas uz nasadeny Exchange 2010 ?
Exchange 2010 - Architektura
Exchange 2010 - nove vlastnosti
http://www.microsoft.com/exchange/2010/en/us/overview.aspx
Najzaujimavejsie
• HA
• RBAC
• User Self Service
• Storage
• Unified User Experience
A dalsie ….
Vysoka dostupnost (HA) - DAG
• SCC, LCR, CCR, SCR -> zrusene
• Je mozne postavit HA vsetkych “Exchange roles” na najmenej 2 serveroch
• Az 16 replik kazdej DB
• Ako storage sa da pouzit DAS, SAN, NAS – FC, SAS aj SATA
Mailbox Server
DB1
DB3
DB2
DB4
DB5
Recover quickly
disk and
database failures
Mailbox Server
DB1
DB2
DB4
DB5
DB3
Mailbox Server
DB1
DB2
DB4
DB5
DB3
Replicate databases
to remote datacenter
BA (HQ) MA (DR)
Vysoka dostupnost (2)
Online Mailbox Move
Uzivatelia ostavaju online pocas presunu mailboxov
EX2003 -> EX2010 – offline
EX2007 SP1 -> EX2010 - offline
EX2007 SP2 -> EX2010 – online
EX2010 -> EX2010 - online
E-mail Client
Mailbox Server 1 Mailbox Server 2
Client Access Server
RBAC – Role Based Access Control
Daju sa vytvarat jednoduchsie opravnenia na delegovanieprav inym osobam
• HR ludom – na modifikaciu atributov kontaktov
• Helpdesk ludom – na spravovanie napr diskovych kvot
• Branch office admin – na spravovanie len svojich uctov
Atd…
User Self Service
Track the Status of Sent Messages
Create and Manage Distribution Groups
Storage
Storage Area Network (SAN)
JBOD SATA(RAID-less)
Direct Attached SAS / SATA Disks
70% reduction in disk I/O over EX2007
32K pages
Disk I/O patterns optimized for better hardware utilization
Resilience against corruption through automated page-level repairs
Delayed B-Trees calculation
Optimized for Large Mailboxes (10GB+)
Optimized for 100K items per Folder
…
Unified User Experience (1)
Conversation View
Ignore Conversation
Instant Messaging
Unified User Experience (2)
SMS SYNC
MailTips
MailTips in Outlook 2010
MailTips in Outlook Web App
Calendar - Free/Busy Federation
E-mail Archive (1)
Email Archive (2) Apply Move and Delete Policies to Individual Messages
Retention Policy and Expiry Details
Policies Applied to All E-mail Within a Folder
RMS
• Transport Rule action to apply Rights Management template to e-mail or voice mail messages
• Support for scanning of attachments and searching of protected e-mail
• “Do Not Forward” policies available by default
• Information protection across PC, Web, and mobile device
CMDLETS
Instalacia / Upgrade Exchange
Upgrade
Inplace Upgrade
-> nie je mozny
Migracia
-> v ramci Exchange Organizacie (ANO)
- nesmie tam byt Exchange 2000 alebo Exchange 5.5
- z Exchange 2007
-> migracia do novej Exchange Organizacie (ANO)
- z Exchange 2003
-> z ineho systemu (ANO)
- napr. LOTUS
EX 2010 – dropnute vlastnosti
• Local continuous replication (LCR), cluster continuous replication (CCR), single copy cluster (SCC) and Server Message Block (SMB) based replication
• Inbound Fax
• Clustered mailbox servers
• Storage groups
• Two copy replication limitations
• Streaming backups
• WebDAV
• 32-bit Client Administration Tools
• API - ExOLEDB, WebDAV, CDOEx, and ExCDO
Deployment
Single Server
– vsetky role na jeden server
- okrem EDGE
Multiple Server
- Poradie – CHUME
- CAS
- HUB
- UM (optional)
- MBX
- EDG
UNINSTALL - > EMUHC
Prerequisities - AD
AD DS 2003 SP2 GC na kazdom Exchange AD DS Site
Windows 2003 Forest Functional Level
AD PREPARATION
/PrepareSchema – musi byt urobene z x64
/PrepareAD
/PrepareDomain
Potrebne prava Enterprise Administrators, Schema Administrators, Exchange Organization Administrators, …
Prerequisities (2) - Installation
Windows Server 2008 SP2 or Release 2 (R2) 64-bit editions
Standard, Enterprise
Windows Management Framework
Windows PowerShell v2.0
Windows Remote Management v2.0
.NET Framework 3.5 SP1
Internet Information Services (IIS)
http://technet.microsoft.com/en-us/library/bb691354.aspx
Prerequisities (3)
V systeme musia byt nainstalovane sucasti IIS
Priklad : (Windows 2008 R2, vsetky role na jednom serveri)Import-Module ServerManager
Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,Web-ISAPI-Ext,Web-Digest-Auth,Web-Dyn-Compression,NET-HTTP-Activation,RPC-Over-HTTP-Proxy -Restart
Set-Service NetTcpPortSharing -StartupType Automatic
http://technet.microsoft.com/en-us/library/bb691354.aspx
Upgrade v Kocke – z vtacej perspektivy
VIRTUALIZACIA
VirtualizaciaSupported
Root: Hyper-V or SVVPGuest:
– Exchange Server 2010– Windows 2008 SP2 or Windows 2008 R2– Mailbox, Client Access, Hub Transport, Edge roles– Meets basic Exchange system requirements– Storage is fixed Virtual Hard Disk (VHD), SCSI pass through, or iSCSI
Not Supported- Combination of Exchange Mailbox HA and hypervisor-based clustering or migration technologies- Snapshots, differencing/delta disks- Volume Shadow Copy Service (VSS) backup of root for pass-through disks or iSCSI disks connected to initiator in guest- Unified Messaging role- Virtual/logical proc ratio greater than 2:1- Applications running in root partition
http://technet.microsoft.com/en-us/library/aa996719.aspx
Virtualizacia (2) - HA
CapabilityHyper-V Quick Migration DR
Exchange Mailbox HA
OS Heartbeat Yes Yes
Exchange Heartbeat No Yes
Copies of Exchange Data 1 At least 2
Shared Storage Requirement Yes No
Machine/Role Fail Over Granularity No
Yes(+ database fail granularity in Exchange Server
2010)
Support Hardware VSS No Yes
Support Backup from Passive N/A Yes
SIZING EXCHANGE 2010
SIZING (1) - MAXIMUMS
RoleRecommendedMax Processor Configuration
RecommendedProcessor
Configuration
RecommendedMax Memory Configuration
Recommended Memory Configuration
Hub Transport 12 cores 4 cores 16 gigabytes (GB)1 GB per core or 8
GB (minimum)
Client Access Server 12 cores 8 cores 16 GB2 GB per core or 8
GB (minimum)
Mailbox 12 cores 8 cores 64 GB4 GB plus 2-10
megabytes (MB) per mailbox
Unified Messaging 12 cores 8 cores 16 GB2 GB per core or 4
GB (minimum)
Multiple Role Server
24 cores 8 cores 64 GB8 GB plus 2-10 MB
per mailbox
SIZING (2) – STORAGE
Treba ponechat na skusenych/znalych
Ak by vas zaujimalo ako a preco, tak si
SIZING CALCULATOR vyskusajte
http://msexchangeteam.com/files/12/attachments/entry453145.aspx
SIZING (3) – Storage – Real World
- File System Antivirus
- Exchange Antivirus
- BlackBerry
- Monitoring
- Backup
- Archiving
- Faxing
- etc…
= 200 az 500 % narast oproti povodnym IOPS
STORAGE - JBOD
JBOD Advantages JBOD Challenges
Eliminates unnecessary DB copies: server and storage redundancy can be symmetrical
Disk striping performance (e.g. RAID10) cannot be leveraged
Reduces disk I/O: eliminates RAID write penalty Disk failure = database failover (~30 second outage)
Enables simple storage design: 1 disk = 1 database with logs
Re-enabling resiliency = spare disk assignment/partitioning/format/DB re-seed (scriptable)
Enables simple storage failure recovery Soft disk errors (bad blocks) must be detected and repaired
DESIGNS
CAS/HUB/
MAILBOX 1
CAS/HUB/
MAILBOX 2
Member servers of DAG can host other server roles
DB2
2 server DAGs, with server roles combined or not, should use RAID
High Availability Design ExampleBranch Office or Smaller Deployment
37
Single Site
3 HA Copies
Database Availability Group (DAG)
MailboxServer 1
MailboxServer 2
MailboxServer 3
3 Nodes
X
JBOD -> 3 physical Copies
2 servers out -> manual activation of server 3
In 3 server DAG, quorum is lost
DAGs with more servers sustain more failures – greater resiliency
High Availability Design ExampleDouble Resilience – Maintenance + DB Failure
38
DAG1DAG1
DB1 DB2
DB3 DB4
DB1 DB2
DB3 DB4
DB1 DB2
DB3 DB4
DB1 DB2
DB3 DB4
DB1 DB2
DB3 DB4
Failure Scenario: Database Failure1. MBX-A-1 DB1 fails2. Automatic failover to MBX-A-23. MBX-A-1 DB1 is fixed and becomes
a copy
DB1 DB2
DB3 DB4
DB1 DB2
DB3 DB4
Failure Scenario: Server Failure1. MBX-A-1 fails2. Automatic failover to MBX-A-23. MBX-A-1 is fixed
DB1 DB2
DB3 DB4
DB1 DB2
DB3 DB4
DB1 DB2
DB3 DB4
Failure Scenario: Data Center Failure1. Primary data center fails2. Adjust DNS records for SMTP and HTTPS access and adjust CAS configuration (if necessary)3. Run Stop-DatabaseAvailabilityGroup DAG1 –ActiveDirectorySite Redmond –ConfigurationOnly (in both data centers)4. Stop the cluster service on the nodes: Stop-Service ClusSvc5. Restore-DatabaseAvailabilityGroup DAG1 –ActiveDirectorySite “Bel Air” –AlternateWitnessDirectory c:\fsw\DAG1 –
AlternateWitnessServer HT-B6. Databases mount (no activation block scenario)
DB1 DB2
DB3 DB4
DB1 DB2
DB3 DB4
DB1 DB2
DB3 DB4
Legend Active Database
Database Copy
Unhealthy? Database
Outlook 2007/14 (MBX on DB1)
Recovering Primary Data Center1. Verify primary data center is capable of hosting service2. Add primary data center servers back to DAG: Start-DatabaseAvailabilityGroup DAG1 –ActiveDirectorySite Redmond3. Reconfigure DAG to use File Share Witness in primary data center: Set-DatabaseAvailabilityGroup DAG1 –WitnessDirectory c:\fsw\dag1 –
WitnessServer HT-A4. Reseed data or allow replication to occur and update copies in primary data center 5. Schedule downtime for the mailbox databases and dismount them6. Change MX records and HTTP access back to primary data center7. Move databases back to primary data center: Move-ActiveMailboxDatabase DB1 –ActivateOnServer MBX-A-18. Mount databases in primary data center
DB1 DB2
DB3 DB4
172.17.x.x “Replication” Network
172.16.x.x “MAPI” Network
172.19.x.x “Replication” Network
172.18.x.x “MAPI” Network
2.2.x.x Perimeter Network
AD Site Redmond AD Site Bel Air
Edge-BProxy-B
2.1.x.x Perimeter Network
Edge-A Proxy-A
MBX-B-3 MBX-B-4MBX-A-1 MBX-A-2
DC-A HT-A CAS-A CAS-B HT-B DC-B
Contoso.com (MX Record)Autodiscover.contoso.comMail.contoso.comLoad Balance Array Records
39
