Exchange 2010 ITPro. Milan Marenčík Microsoft Services

Transcription

1 Exchange 2010 ITPro Milan Marenčík Microsoft Services

2 Exchange bit AD required 5 serverovych roli Anywhere, anytime, any device Secure by design

3 5 roli Mailbox Client Access Hub Transport Unified Messaging Edge Transport

4 New Features Moderated transport Disk IOPS requirements % % Exchange Control Panel DAG MailTip Archiv Kolokacia roli na jednom serveri

5 High Availability Data Availability Service Availability Automatic Failover

6 Exchange 2010 High Availability

7 Availability Scenarios Service Availability Standalone Failover Clustering Network Load Balancing Application Availability Data Availability Third-Party Replication Built-in replication

8 Mailbox

9 Windows 2008 Failover Clustering

10 Exchange 2010 and Cluster No longer implements a clustered resource model Cluster services leveraged for: Node Management Cluster registry / registry replication Cluster Network / Heartbeating Supports up to the maximum cluster limit of 16 nodes

11 Database Availability Groups All DAG members must reside in the same Active Directory domain DAG members do not have to reside in the same Active Directory site It is no longer required or recommended to use stretched Active Directory sites DAG members can reside in different network subnets It is no longer required to stretch subnets DAG members must have round trip network latency < 250 ms

12 DAG Networks Single network DAG members fully supported Recommendation to have minimum of two networks on each node Both an Exchange and Platforms recommendation A network is a collection of one or more subnets used for either replication or MAPI traffic

13 DAG Networks There is no preference order to replication networks chosen at random by replication service MAPI network may be replication disabled Network will be utilized for replication if no other valid replication path exists iscsi networks should be both replication disabled and disabled for cluster use

14 Log Shipping Exchange 2007 leverages SMB shares for log shipping activities Exchange 2010 no longer uses shares Log files are stored in local directory Target replication service opens TCP socket connection to source replication service Source replication service provides logs to target replication service There is one TCP socket connection per database

15 Database Old New

16 Page Patching Allows page-level recovery from corruption Not meant to replace other failover mechanisms Basic flow: Database detects page failure (-1018?) Places marker in log stream Other DAG members send updated pages Original server replaces page with good copy, ignores later responses Obviously requires DAG

17 What s Wrong with DAS Isolation DAS isolates disk performance DAS isolates capacity Overhead DAS creates thousands of storage management agents Over purchase because DAS change is difficult

18 What s Wrong with SAN Cost Hardware cost Administration costs Isolation or lack thereof Share the fabric Share the controller Share the disks Complexity Now there could potentially be 3 groups involved with the provision of a LUN (network, server, storage)

19 Client Access Server

20 Load Balancing in General All CAS in a site must be configured the same for consistent results. Make sure you have the authn correct and the urls balanced

21 Load Balancing HW LB Cost Service awareness Windows NLB Source IP RRDNS is not service aware and its effectiveness is only as good as the client making the query

22 Hub Transport

23 Install Exchange

24 Installation Install Windows 2008 R2 Config IP, Time Zone, Pridat do AD Powershell ako admin Import-Module ServerManager Add-WindowsFeature NET-Framework, RSAT Restart Failover-Clustering NLB Install Exchange (stiahni SP2) Setup.com /mode:install /role:c,h,m /InstallWindowsComponents /OrganizationName:OrgName

25 Transport

26

27