تهیه کننده : آرش قمبری Ver:1.2 EXCHANGE 2010 SP2 HIGH AVAILABILITY.

Slides:



Advertisements
Similar presentations
Painless Transitions from Microsoft Exchange 2003 to Microsoft Exchange 2007 J. Peter Bruzzese Co-Founder of ClipTraining MCSE/MCT/ MCITP: Messaging for.
Advertisements

UNIVERSITY OF EDUCATION BY H.M.ISHTIAQ RAFIQUE. Domain Name Structure.
Module 13: Implementing ISA Server 2004 Enterprise Edition: Site-to-Site VPN Scenario.
1 Windows 2008 Failover Clustering Witness/Quorum Models.
Adnan Rafique Exchange Architect Board Of Director – GITCA Global Board Blog –
Daniel Kenyon-Smith UC Consultant – MCS UK. Optimize for Software + Services Deployment Flexibility Continuous Availability Simplify Administration Manage.
Site A But what if there is a catastrophic event? Fire, flood, earthquake … Same Physical Location.
EXCHANGE SERVER 2010 HIGH AVAILABILITY CONCEPTS Scott Schnoll Principal Technical Writer Microsoft Corporation SESSION CODE: EXL303 (c) 2011 Microsoft.
Overview of Server Roles in Exchange Server 2010 In Exchange Server 2010, servers are installed with specific functional roles: Mailbox Server role Edge.
Exchange Deployment Planning Services Exchange 2010 High Availability.
Scott Schnoll Exchange Server 2013 Site Resilience.
Topic Of This Hour Exchange 2013: Database Availability Group Sept 26, :00 PM EST / 12:00 PM CST / 10:00 AM PST / 7:00 PM CET / 6:00 PM UTC/10:30.
Module 12 Upgrading from Exchange Server 2003 or Exchange Server 2007 to Exchange Server 2010.
Feature Exploration : Exchange 2013 Transport High Availability Presented March 11, 2014 at NYExUG Meeting Last Updated on March 11, 2014 Ben Serebin Ehlo.
SQL Server 2000 Clustering Dave Fackler. Agenda Windows 2000 Clustering SQL Server 2000 Clustering Implementation Tips.
1 © Copyright 2010 EMC Corporation. All rights reserved. EMC RecoverPoint/Cluster Enabler for Microsoft Failover Cluster.
Microsoft Clustering Sean Roberts, Jean Pierre SLAC.
Lesson 1: Configuring Network Load Balancing
Manage backup vaults and servers Download and install backup agent Download a vault agent Create backup vault.
Workflow Steps Perform a datacenter switchover for a database availability group Version 1.2 (Updated 12/2012)
11 SERVER CLUSTERING Chapter 6. Chapter 6: SERVER CLUSTERING2 OVERVIEW  List the types of server clusters.  Determine which type of cluster to use for.
Implementing High Availability
Scott Schnoll Principal Technical Writer Microsoft Corporation UNC313.
EXC11: Migrating to Exchange 2010 from Exchange 2003 Jim McBee Ithicos Solutions LLC
Module 8 Implementing Backup and Recovery. Module Overview Planning Backup and Recovery Backing Up Exchange Server 2010 Restoring Exchange Server 2010.
Scott Schnoll Principal Technical Writer Microsoft Corporation Session Code: UNC3.
(ITI310) By Eng. BASSEM ALSAID SESSIONS 8: Network Load Balancing (NLB)
Microsoft Load Balancing and Clustering. Outline Introduction Load balancing Clustering.
Installing a New Windows Server 2008 Domain Controller in a New Windows Server 2008 R2.
Exchange Pre-Deployment Analyzer - ExPDA 8ead-7479dab1abf2&displaylang=en.
DB-12: Achieving High Availability with Clusters and OpenEdge® Replication Combining the two technologies Hugo Loera Chávez Senior Tech Support Engineer.
New York: Limerick: Hannover: Singapore: MVP Technical Series Surviving Disaster: Building Site.
Implementing Multi-Site Clusters April Trần Văn Huệ Nhất Nghệ CPLS.
INSTALLING MICROSOFT EXCHANGE SERVER 2003 CLUSTERS AND FRONT-END AND BACK ‑ END SERVERS Chapter 4.
Appendix B Planning a Virtualization Strategy for Exchange Server 2010.
Ross Smith IV Senior Program Manager, Exchange Server Microsoft Corporation SESSION CODE: UNC202 Kyryl Perederiy Senior Systems Engineer, Business Online.
DB-2: OpenEdge® Replication: How to get Home in Time … Brian Bowman Sr. Solutions Engineer Sandy Caiado Sr. Solutions Engineer.
Deploying a Web Application Presented By: Muhammad Naveed Date:
Module 9 Planning a Disaster Recovery Solution. Module Overview Planning for Disaster Mitigation Planning Exchange Server Backup Planning Exchange Server.
Scott Schnoll Principal Technical Writer Microsoft Corporation Session Code: UNC307.
Specview 32 Release 2.5 Enhancements
SQLCAT: SQL Server HA and DR Design Patterns, Architectures, and Best Practices Using Microsoft SQL Server 2012 AlwaysOn Sanjay Mishra Program Manager.
Daniela Anzellotti Alessandro De Salvo Barbara Martelli Lorenzo Rinaldi.
Module 10: Maintaining High-Availability. Overview Introduction to Availability Increasing Availability Using Failover Clustering Standby Servers and.
Module 3: Preparing for and Recovering from Non- Mailbox Server Failures.
DB4DB3 DB2 PassiveActiveLagged 4-member DAG 4 databases 4 copies of each database 4 databases per volume Symmetrical design.
1 Week #10Business Continuity Backing Up Data Configuring Shadow Copies Providing Server and Service Availability.
7. Replication & HA Objectives –Understand Replication and HA Contents –Standby server –Failover clustering –Virtual server –Cluster –Replication Practicals.
Gareth Ireland Infrastructure Consultant
Windows Server 2003 La migrazione da Windows NT 4.0 a Windows Server 2003 Relatore: MCSE - MCT.
High Availability and Failover Clusters in Exchange Server 2007.
Exchange Server versionForest "rangeUpper" attribute of ms-Exch-Schema-Version-Pt Exchange 2000 Server RTM4397 Exchange 2000 Server SP34406 Exchange.
4/26/2017 © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks.
A CHIEVING SITE R ESILIENCY WITH E XCHANGE SERVER Pradeep Kini.
SQL Server 2014 AlwaysOn Step-by-Step SQL Server 2014 AlwaysOn Step-by-Step A hands on look at implementing AlwaysOn in SQL Server 2014.
Appendix B Advanced Topics in Exchange Server 2010.
VIRTUAL SERVERS Chapter 7. 2 OVERVIEW Exchange Server 2003 virtual servers Virtual servers in a clustering environment Creating additional virtual servers.
All the things you need to know before setting up AlwaysOn Michael Steineke SQL & BI Solution Lead Enterprise Architect Concurrency, Inc.
AlwaysOn In SQL Server 2012 Fadi Abdulwahab – SharePoint Administrator - 4/2013
Microsoft Virtual Academy Module 9 Configuring and Managing the VMM Library.
Microsoft ® Exchange Server 2010 Mailbox Resiliency Name Title Microsoft Corporation.
Introduction to Clustering
Microsoft BackOffice Applications
Planning and Implementing High Availability
Verified Microsoft Study Material Exam Dumps Dumps4Download.us
Introduction to Clustering
Microsoft Exchange Server 2010 High Availability Design Considerations
AlwaysOn Availability Groups
Microsoft Virtual Academy
Designing Database Solutions for SQL Server
Presentation transcript:

تهیه کننده : آرش قمبری Ver:1.2 EXCHANGE 2010 SP2 HIGH AVAILABILITY

Overview of Exchange Clustering: 1. Exchange 2003 (backend Role) 2. Exchange 2007 (Mailbox Role) * continuous replication (CR)

3. Exchange 2010 (Mailbox Role) * Continuous Replication (( Block mode(SP1) VS File mode(RTM))) * Data Availability Group(DAG) * Database Mobility * Incremental Deployment * lagged Mailbox database copy * Mailbox database Copy * Mailbox Resiliency & Site Resiliency * Shadow Redundancy (On Transport Roles) * Switchover & Failover * DB Size Limit to 2TB

Other changes related to Exchange 2010 HA: * Transport Dumpster keep MSG until replicate to all DAG nodes * Transport Dumpster on Mailbox * Online Move Mailbox * Shadow Redundancy * Third Party Replication API *Active Manager - runs on all DAG & manage switchover or failover - Primary Active Manager (PAM) manage switchover or failover and Best Copy Selection - Secondary Active Manager (SAM) provide information to cas & hub

Exchange 2010 Clustering Quorum Models: * Even Nodes -> File share Majority * Odd Nodes -> Node Majority

DAG Cluster For two nodes 1.Configure NICs on mailbox servers 2.Configure Firewall 3.Setup exchange trusted subsystem group 4.Install Failover Cluster 5.Restart servers 6.Create Witness Folder 7.Create DAG 8.Configure DAG IP Address 9.Add Servers to DAG 10. Create DB on DAG Members

Configuring CAS HA on two nodes 1.Install NLB On server 2.Configure DNS 3.Configure NLB & Add one node UDP&TCP 5.80 TCP – 443 TCP – 135 TCP 6. Add another node 7.new-clientaccessarray -name "" -FQDN -Site 8.set-mailboxdatabase -identity "" –rpcclientaccessserver 9.Restart CAS Server