Review of ILL & MSP reflect on Performance Test Results

Transcription

1 Strategic Disaster Recovery with Exchange 2010 Technology Operations SOSPG2 Speakers Steven Shock Chief Technology Officer Irell & Manella LLP (310) Patrick Sklodowski Managing Director mindshift Technologies, Inc. (856) Booth 823/825 Session Overview Not an Overview Focus on High Availability (HA) Disaster Recovery (DR) Strategic Discussion Design Philosophy Affects on Policy Tactical Discussion 1

2 Irell & Manella LLP 450 users 2 Offices IP Litigation Concierge Service Retention Policy mindshift Technologies IT Consulting and Cloud Services Provider Serving Law Firms Nationwide for Over A Decade ILTA and ALA Sponsor Named #1 MSP by MSPmentor (2009/2010/2011/2012) Division Dedicated to Legal Customers BASIC CONCEPTS 2

3 Client Connections MAPI Connects through the CAS Role What Mailbox Server is listed in Outlook Profile? Database Availability Group Replication Boundary High Availability vs. Site Resiliency HA is Site-based Site Resiliency Across Sites Consider Recovery Objectives Quorum Isolation Active / Passive DAG 3

4 Active / Active DAG Failure Domains Failure Maintenance Redundancies Servers / VMs Load Balancing Multiple Database Copies Shadow Redundancy 4

5 DESIGN CONSIDERATIONS Design Philosophy New Design Philosophy Recovery Objectives Database Design Dependent on Environment Simple Complex Moderately Complex Staggering Number of Options! Design Options Too Many Options! High Availability Exchange Native VMware Third Party On-premise Third Party Continuity Client Connectivity Outlook AnyWhere Outlook WebApp SSLVPN / UAG Mobile Devices MDM Replication Exchange Native Third Party Software SAN-based Future Integration Disaster Recovery Exchange Native Third Party Continuity Third Party On-premise Software Based SAN Solutions 5

6 Recovery Objectives Reasonable Objectives are Usually Exceeded Don t Increase Firm Expectations! What Failures are you Designing for? Failure Domain(s) Time Objective (RTO) Point Objective (RPO) Failure Domains Failure Maintenance DESIGN CONCEPTS 6

7 Database Design Philosophies: Old and New Policy Backups Recovery Objectives Large Databases Archive Database Lagged Copies Single Item Recovery Recovery Database Override Mount Dial Database Database Copy Seeding CAS / Hub Roles Multiple Servers Hosting Roles Production and DR NLB for CAS Hub Native HA 7

8 WAN Redundancy Links Carriers Equipment Replication Network Network / WAN DAG Replication Maximum Latency Adjust Cluster Settings? Backup / Recovery Portable Database Monolithic Recovery Database Point in Time SAN Replication No Backups Other Options HA at Virtualization Level SAN Replication Database or Full Environment Managed & Cloud Services 8

9 RECOVERY Worse Than a Disaster? DR Testing Full Failover vs. Unit Testing VMware / Site Recovery Manager Restore Environment in a Bubble Restoring DAG Can be Difficult Consider New Server and Database Portability Site Failover Database Failover Activation Blocking CAS Proxying Site Failover Start/Restore DAG Update DNS Internet Mail 9

10 Site Failback Restore / Resume Servers Resume / Update Database Copies Verify Health Failover Databases Update DNS Lessons Learned - 1 NLB / Kerberos Authentication Consider DR site DAG in a Single Site? Put DAG in DAC Mode Anyway DatacenterActivationMode [DAGName] DatacenterActivationMode DAGOnly Only One CAS Server? Still Consider using CASArray Setting Future Growth Lessons Learned - 2 Failback URL Namespace Considerations Internet Name(s) MAPI Don t Mix! 10

11 DNS Use CNAMEs Time to Live (TTL) Lessons Learned - 3 Public Folders Change on Mailbox DB Slow WAN Links Change Cluster Settings? Speakers Steven Shock Chief Technology Officer Irell & Manella LLP SShock@irell.com (310) Patrick Sklodowski Managing Director mindshift Technologies, Inc. Patrick.Sklodowski@mindSHIFT.com (856) Booth 823/825 11