MS Exchange 2010 Prechod Ing. Peter Záhradník

Size: px

Start display at page:

Download "MS Exchange 2010 Prechod Ing. Peter Záhradník"

Emily Tucker
5 years ago
Views:

1 MS Exchange 2010 Prechod Ing. Peter Záhradník Gratex Support Center

2 Exchange 2010 o com to bude? Tato prezentacia bude pre ludi co uvazuju nad prechodom na novy Exchange

3 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?

4 Exchange Architektura

5 Exchange nove vlastnosti erview.aspx Najzaujimavejsie HA RBAC User Self Service Storage Unified User Experience A dalsie.

Replicate databases to remote datacenter SCC, LCR, CCR, SCR -> zrusene Je mozne postavit HA vsetkych

6 Vysoka dostupnost (HA) - DAG BA (HQ) MA (DR) Mailbox Server Mailbox Server Mailbox Server Recover quickly disk and database failures DB1 DB2 DB3 DB4 DB5 DB1 DB2 DB3 DB4 DB5 DB1 DB2 DB3 DB4 DB5 Replicate databases to remote datacenter 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

Vysoka dostupnost (2) Online Mailbox Move E-mail Client Uzivatelia

-> EX2010 offline EX2007 SP1 -> EX2010 - offline Mailbox Server 1

7 Vysoka dostupnost (2) Online Mailbox Move Client Uzivatelia ostavaju online pocas presunu mailboxov Client Access Server EX2003 -> EX2010 offline EX2007 SP1 -> EX offline Mailbox Server 1 Mailbox Server 2 EX2007 SP2 -> EX2010 online EX2010 -> EX online

8 RBAC Role Based Access Control Daju sa vytvarat jednoduchsie opravnenia na delegovanie prav inym osobam HR ludom na modifikaciu atributov kontaktov Helpdesk ludom na spravovanie napr diskovych kvot Branch office admin na spravovanie len svojich uctov Atd

9 User Self Service Track the Status of Sent Messages Create and Manage Distribution Groups

10 Storage Storage Area Network (SAN) Direct Attached SAS / SATA Disks JBOD SATA (RAID-less) 70% reduction in disk I/O over EX K 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

11 Unified User Experience (1) Conversation View Instant Messaging Ignore Conversation

12 Unified User Experience (2)

13 SMS SYNC

14 MailTips MailTips in Outlook 2010 MailTips in Outlook Web App

15 Calendar - Free/Busy Federation

16 Archive (1)

17 Archive (2) Apply Move and Delete Policies to Individual Messages Policies Applied to All E- mail Within a Folder Retention Policy and Expiry Details

and searching of protected e-mail Do Not Forward policies

18 RMS Transport Rule action to apply Rights Management template to or voice mail messages Support for scanning of attachments and searching of protected Do Not Forward policies available by default Information protection across PC, Web, and mobile device

19 CMDLETS

20 Instalacia / Upgrade Exchange

21 Upgrade Inplace Upgrade -> nie je mozny Migracia -> v ramci Exchange Organizacie (ANO) - nesmie tam byt Exchange 2000 alebo Exchange z Exchange > migracia do novej Exchange Organizacie (ANO) - z Exchange > z ineho systemu (ANO) - napr. LOTUS

22 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

23 Deployment Single Server vsetky role na jeden server - okrem EDGE Multiple Server - Poradie CHUME - CAS - HUB - UM (optional) - MBX - EDG UNINSTALL - > EMUHC

24 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,

25 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)

26 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

27 Upgrade v Kocke z vtacej perspektivy

28 VIRTUALIZACIA

29 Virtualizacia Supported Root: Hyper-V or SVVP Guest: 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

30 Virtualizacia (2) - HA Capability Hyper-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

31 SIZING EXCHANGE 2010

32 SIZING (1) - MAXIMUMS Role Recommended Max Processor Configuration Recommended Processor Configuration Recommended Max Memory Configuration Hub Transport 12 cores 4 cores 16 gigabytes (GB) Client Access Server 12 cores 8 cores 16 GB Mailbox 12 cores 8 cores 64 GB Unified Messaging 12 cores 8 cores 16 GB Recommended Memory Configuration 1 GB per core or 8 GB (minimum) 2 GB per core or 8 GB (minimum) 4 GB plus 2-10 megabytes (MB) per mailbox 2 GB per core or 4 GB (minimum) Multiple Role Server 24 cores 8 cores 64 GB 8 GB plus 2-10 MB per mailbox

33 SIZING (2) STORAGE Treba ponechat na skusenych/znalych Ak by vas zaujimalo ako a preco, tak si SIZING CALCULATOR vyskusajte aspx

34 SIZING (3) Storage Real World - File System Antivirus - Exchange Antivirus - BlackBerry - Monitoring - Backup - Archiving - Faxing - etc = 200 az 500 % narast oproti povodnym IOPS

35 STORAGE - JBOD JBOD Advantages Eliminates unnecessary DB copies: server and storage redundancy can be symmetrical Reduces disk I/O: eliminates RAID write penalty Enables simple storage design: 1 disk = 1 database with logs Enables simple storage failure recovery JBOD Challenges Disk striping performance (e.g. RAID10) cannot be leveraged Disk failure = database failover (~30 second outage) Re-enabling resiliency = spare disk assignment/partitioning/format/db re-seed (scriptable) Soft disk errors (bad blocks) must be detected and repaired

36 DESIGNS

37 High Availability Design Example Branch Office or Smaller Deployment 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 37

Copies DAGs with more servers sustain more failures JBOD -> greater 3 physical resiliency

38 High Availability Design Example Double Resilience Maintenance + DB Failure 2 servers out -> manual activation Single of Site server 3 Nodes In 3 server DAG, quorum is lost HA Copies DAGs with more servers sustain more failures JBOD -> greater 3 physical resiliency Copies Mailbox Server 1 Mailbox Server 2 Mailbox Server 3 X Database Availability Group (DAG) 38

Recovering Failure Scenario: Primary Database Server Center Failure Center Failure 1.

Add Automatic Adjust primary DNS failover records data center to for MBX-A-2 SMTP servers and back HTTPS to DAG: access

Reconfigure MBX-A-1 Run Stop-DatabaseAvailabilityGroup DB1 is fixed DAG is fixed use and File becomes Share Witness DAG1 in

$centers) c:\fsw\dag1 WitnessServer a Stop copy the cluster HT-A service on the nodes: Stop-Service ClusSvc 4. 5.$ $data AlternateWitnessDirectory center c:\fsw\dag1 5.$ Change Databases MX mount records (no and activation HTTP access block back scenario) to primary data center Legend Active Database 7.

Change Databases MX mount records (no and activation HTTP access block back scenario) to primary data center Legend Active Database 7.

Mount databases in primary data center Unhealthy? Database Edge-A Proxy-A 2.1.x.x Perimeter Network Contoso.

39 Recovering Failure Scenario: Primary Database Server Center Failure Center Failure 1. Verify MBX-A-1 Primary primary data DB1 failscenter data center fails is capable of hosting service 2. Add Automatic Adjust primary DNS failover records data center to for MBX-A-2 SMTP servers and back HTTPS to DAG: access Start-DatabaseAvailabilityGroup and adjust CAS configuration (if DAG1 necessary) ActiveDirectorySite Redmond Reconfigure MBX-A-1 Run Stop-DatabaseAvailabilityGroup DB1 is fixed DAG is fixed use and File becomes Share Witness DAG1 in ActiveDirectorySite primary data center: Redmond Set-DatabaseAvailabilityGroup ConfigurationOnly (in both DAG1 data WitnessDirectory centers) c:\fsw\dag1 WitnessServer a Stop copy the cluster HT-A service on the nodes: Stop-Service ClusSvc Reseed Restore-DatabaseAvailabilityGroup data allow replication occur DAG1 and ActiveDirectorySite update copies in primary Bel Air data AlternateWitnessDirectory center c:\fsw\dag1 5. Schedule AlternateWitnessServer downtime for the HT-B mailbox databases and dismount them 6. Change Databases MX mount records (no and activation HTTP access block back scenario) to primary data center Legend Active Database 7. Move databases back to primary data center: Move-Activ boxDatabase DB1 ActivateOnServer MBX-A-1 Database Copy 8. Mount databases in primary data center Unhealthy? Database Edge-A Proxy-A 2.1.x.x Perimeter Network Contoso.com (MX Record) Autodiscover.contoso.com Mail.contoso.com Load Balance Array Records Proxy-B Edge-B 2.2.x.x Perimeter Network DC-A HT-A CAS-A CAS-B HT-B DC-B x.x MAPI Network DAG x.x MAPI Network DAG1 DB1 MBX-A-1 DB2 DB1 MBX-A-2 DB2 MBX-B-3 DB1 DB2 MBX-B-4 DB1 DB2 DB3 DB4 DB3 DB4 DB3 DB4 DB3 DB x.x Replication Network AD Site Redmond Outlook 2007/14 (MBX on DB1) x.x Replication Network AD Site Bel Air

Exchange Server Continuous Replication. Cluster. Local. Standby. 2. Inspect logs. 1. Copy logs. 3. Replay logs. Log. Log

Exchange Server Continuous Replication. Cluster. Local. Standby. 2. Inspect logs. 1. Copy logs. 3. Replay logs. Log. Log Exchange Server 2007 Continuous Replication 2. Inspect logs Database Log E00.log E0000000012.log E0000000011.log 1. Copy logs Log Database 3. Replay logs Local Cluster File Share Standby Log shipping to