Disaster Recovery for All VMware vcenter Site Recovery Manager 5 Puts Real-Time Replication and Disaster Recovery Within the Reach of Every Business

Size: px

Start display at page:

Download "Disaster Recovery for All VMware vcenter Site Recovery Manager 5 Puts Real-Time Replication and Disaster Recovery Within the Reach of Every Business"

Colin Carr
6 years ago
Views:

1 Disaster Recovery for All VMware vcenter Site Recovery Manager 5 Puts Real-Time Replication and Disaster Recovery Within the Reach of Every Business Craig M c Lellan, Hosting.com INF-BCO2065 #vmworldinf

2 DISASTER RECOVERY FOR ALL INF-BCO2065 Enterprise Class Service on an SMB Budget with VMware SRM 5 and the Hosting.com Cloud CRAIG MCLELLAN CHIEF TECHNOLOGY OFFICER 2

3 Agenda Introduction to Hosting.com The State of Disaster Recovery Traditional Approaches to Disaster Recovery The Backstory Considerations of Cloud Based Disaster Recovery Customer Case Studies Q&A 3

4 Introduction 4

5 Introduction Focus on High Availability and Recovery Solutions High availability with integrated recovery Enterprise-Class Cloud Platform One of the largest production workloads in North America Strategic relationships with VMware, Microsoft, EMC, Dell, Juniper, etc. Standardized for seamless platform migrations Recognized By our Customers for Outstanding Customer Experience Industry-leading NPS score of 71 Customers determine company bonus based on their satisfaction level Superior monitoring & management (Customer Portal) 5

6 The State of Disaster Recovery 80% Lack a DR plan Of U.S. Companies Disaster Recovery Journal 1 in 4 Disaster Recover Tests 50% Of SMBs Worldwide Have no Recovery Plan Symantec 2011 SMB Disaster Preparedness Survey Global FAIL Symantec 6

7 So What? 43% of companies experiencing disasters never re-open, and 29% close within 2 years. (McGladrey and Pullen) 93% of business that lost their data center for 10 days went bankrupt within one year. (National Archives & Records Administration) 7

8 The BIG Myth: Catastrophic Events Are the Basis for Most Disasters SOCIAL ENGINEERING FIRE FLOOD SYSTEMS FAILURES 27% WEATHER EARTHQUAKE MALICIOUS ACTIVITIES 73% OF DISASTERS ARE CLINICAL HUMAN ERROR 8

AND AUDITORS ARE IMPATIENT 73% FIRE 27% OF DISASTERS ARE CLINICAL

9 The BIG Myth: Catastrophic Events Are the Basis for Most Disasters MALICIOUS ACTIVITIES SOCIAL ENGINEERING SYSTEMS FAILURES CUSTOMERS AND AUDITORS ARE IMPATIENT 73% FIRE 27% OF DISASTERS ARE CLINICAL FLOOD CUSTOMERS AND AUDITORS ARE WEATHER UNDERSTANDING EARTHQUAKE HUMAN ERROR 9

10 The History of Disaster Recover 80% 5% 10% 4% 1% 10

11 The State of Traditional Critical System Recovery Expensive Infrastructure Software Hosts Storage Facilities Complex Recovery Plans Apps +?? = Hosts? Storage?? Network Untested Recovery REALITY GAP BOTTOM LINE FAILURE TO MEET BUSINESS EXPECTATIONS EXCESSIVE RESOURCE CONSUMPTION 11

12 Challenges Implementing Traditional Recovery Traditionally, organizations have faced many challenges implementing workable disaster recovery for their systems Challenges: - Legacy DR solutions are complicated and slow to implement - Legacy DR solutions are difficult or impossible to fully test - Implementing DR often requires specialized skill sets - Not all organizations have a second DR site or data center - Not all organizations have 24x7 ready staff for failover tasks - Legacy DR solutions are too costly for many organizations Which is why Cloud based DR just makes sense! 12

13 The Backstory 13

14 The Backstory 90+% of the Workload on the Hosting.com Cloud is comprised of Mission & Business Critical Applications Analysis Showed that the BEST use case for nonbelievers was Disaster Recovery Why? No Migration of Workload Required Cost Re-alignment potential Ease of Use positioning 14

15 In the Last Twelve Months We Announced V1 of our Cloud Replication Service in Partnership with VMware at VMworld 2011 We Created two Offers Inter-cloud replication Customer Premises to Hosting.com replication We Have Implemented Dozens of Customers During which we made many discoveries Undertook a Major Upgrade to Address Technology Challenges Product short comings Customer use-cases outside of original scope 15

16 The Primary Benefits We Wanted to Achieve Cost Effectiveness Capitalize on Shared Recovery Site Why use dedicated infrastructure when the Cloud was built for this Test Centric Validation Automated Testing Capabilities Reduce the recovery risk associated with elapsed time Simplicity Of Use Performance And Automation Holistic Application Protection Encapsulation of the entire system including application, OS, and data Stored as virtual machine file Improve Speed and Reduce Errors From complex run books to simple recovery plans Failover automation improves recoverability 16

17 Drivers of Cost Effectiveness All This AND Be Different from Others Working with SRM 17

18 Test Centric, Non-Disruptive Validation Non-disruptive Testing Recovery Site Replication Recovery Site Isolated test environment vsphere Overview Automate test execution Execute recovery plan Customizable for testing with extra callouts and breakpoints Log results of the test Isolated test environment Snapshot replicated LUNs Launch VMs in fenced network Reset environment after test Benefits Confidence and documentation that DR requirements are satisfied Quickly identify and remediate potential issues LUN snapshot Reduce cost and resources required for DR testing Eliminate traditional DR testing weekends 18

Simplicity of Use Physical Configure hardware Complicated Recovery Install OS Operating systems need re-install or bare-metal recovery Lots of time spent sourcing and reconfiguring hardware Configure

19 Simplicity of Use Physical Configure hardware Complicated Recovery Install OS Operating systems need re-install or bare-metal recovery Lots of time spent sourcing and reconfiguring hardware Configure OS Install backup agent Start Single-step automatic recovery Non-standardized Recovery Processes Inconsistent process independent of applications, operating systems, and hardware Reconstitution of the backup infrastructure complicates recovery 40+ Hrs. 19

20 Simplicity of Use Physical Configure hardware Complicated Recovery Install OS Operating systems need re-install or bare-metal recovery Lots of time spent sourcing and reconfiguring hardware Virtual Restore VM Power on VM Simplify recovery Configure OS No operating system re-install or bare-metal recovery No time spent reconfiguring hardware Install backup agent Start Single-step automatic recovery Non-standardized Recovery Processes Inconsistent process independent of applications, operating systems, and hardware Reconstitution of the backup infrastructure complicates recovery Standardize recovery process Consistent process independent of applications, operating systems, and hardware 40+ Hrs. < 4 Hrs. 20

Performance and Automation DR Failover Overview 1 Raise alert when heartbeat lost Automatically detect site failures Require customer to manually initiate failover Site A vsphere 2 User initiates

21 Performance and Automation DR Failover Overview 1 Raise alert when heartbeat lost Automatically detect site failures Require customer to manually initiate failover Site A vsphere 2 User initiates failover Replication Site B vsphere 4 Recover VMs Automated recovery process Stop replication and present volumes Execute user-defined recovery plan Benefits Ensure fast and predictable failovers and migrations Consistently meet business requirements 3 Stop replication and present LUNs to vsphere Minimize risk of user errors 21

22 So, Why A Service Provider Many of You Could Afford to Do This Yourself But, Would it be Beneficial to have Access to our Collective Experience? Let s take a look at some findings and what we ve done to addressed them 22

23 Synchronization and Seeding Bandwidth consumption scales linearly based on the number of virtual machines (VMs) being replicated. Initial synchronization is faster than ongoing synchronization Bandwidth consumption varies by traffic type with initial synchronization being faster than ongoing synchronization. Guest OS type and File System Impact performance Bandwidth consumed by VR traffic varies depending on the guest operating system and underlying file system with VMs. 23

24 Bandwidth Optimization Traffic shaping is not easy or native Distributed vswitch and NIOC do not allow for replication isolation Network infrastructure throttling: Works if your devices allow per port Traffic Shaping Network Timeouts are a constant challenge on VPN connections 24

25 The Network Complexity Is Challenging VMware VirtualCenter/vCenter Server Ports 80, 443, 902, 8096 vsphere Client requires port 8095 and 9007 for the SRM plugin to function VMware Site Recovery Manager (SRM) Ports 80, 902, 8095, 9085, 9007 vsphere Replication Management Server (VRMS) Ports 80, 8043, 8080 vsphere Replication Server (VR Server) Ports 902, 8123, 5480, 31031,

26 How Did We Address this Complexity 26

27 We Abstracted the Entire SRM Interface into the Hosting Portal 27

28 We Automated Testing with 3 Mouse Clicks 28

29 We Made Compliance and Performance Reporting Self Service 29

30 Customer Examples 30

31 CUSTOMER USE CASE 1 (Back-Office Applications; Mining Services Industry) CUSTOMER PROBLEM Continue to operate existing data center while partnering with a Cloud provider for Disaster Recovery Parent company mandated strict compliance requirements that were challenging to meet with the desired budget SOLUTION BENEFITS Provided solution at a price point that company could not find anywhere on the market Flexibility to offer cloud private resources to ensure maximum levels of security 31

32 CUSTOMER USE CASE 1 (Back-Office Applications; Mining Services Industry) Customer On-Premises Cloud to Hosting.com Secure Multi-tenant Cloud 32

33 CUSTOMER USE CASE 2 (SaaS Application; Home Mortgage Industry) CUSTOMER PROBLEM Company needed to satisfy very strict SLA requirements in order to comply with client contracts Company did not own/operate infrastructure and thus needed Hosting.com to provide it SOLUTION BENEFITS Offered comprehensive solution of services centered around application uptime Provided not only a highly available architecture with high security aspects, but also provided a DR aspect Delivered a recovery time measured in minutes at a fraction of the cost of traditional recovery 33

34 CUSTOMER USE CASE 2 (SaaS Application; Home Mortgage Industry) Customer On-Premises Cloud to Hosting.com Secure Multi-tenant Cloud 34

35 CUSTOMER USE CASE 3 (Back-Office Applications; Financial Services Industry) CUSTOMER PROBLEM Replace existing DR datacenter to cloud-based DR datacenter while maintaining protected status throughout the project Strict privacy requirements dictated complex recovery plan development and networking configuration SOLUTION BENEFITS Provided DR expertise that company could not supply on their own Flexibility to offer complex disaster recovery for multiple mission-critical applications Delivered testing capability in complex environment with no impact to production systems 35

36 CUSTOMER USE CASE 3 (Back-Office Applications; Financial Services Industry) Customer On-Premises Cloud to Hosting.com Secure Multi-tenant Cloud 36

37 Lessons Learned - Implementations Prioritization Systems/applications to include or exclude Recovery sequencing is important Application choice are there applications that could be replaced to improve recoverability Recovery Environment Design & Sizing Ensure that mission-critical applications have the resources to operate at an acceptable level remember the customer experience! Consider the length of time the recovery site will be in production 37

38 Lessons Learned - Implementations Network Ensure there is enough bandwidth to support a failover Bandwidth dependent on rate of change of data to ensure RPO Latency considerations RPO what should my RPO be? Data change rate Criticality of most recent data Recoverability of lost data Industry specific dependencies 38

39 Lessons Learned - Validation Regular Validation Makes a Difference Non-disruptive Proves ability to instantiate recovery environment Validation from an IT perspective End-to-end Testing Should be Less Frequent Disruptive Includes all automatic and manual processes Validation of the end user experience Use with caution! 39

40 Lessons Learned - Validation Recovery Plan update Validate your recovery infrastructure as part of change control process Formalize and document the entire recovery process Do not rely on people s memories Incorporation of Operations into You Testing Plan is Critical Regularly scheduled activity Be sensitive to policy and regulatory control objectives Changes in production environment 40

41 Why Hosting s Cloud Replication is the Best Way to address your D/R Needs Problems Solved Desire for Disaster Recovery but customer operates only 1 DC or can t afford traditional DR Require the ability to test the failover of applications to ensure the replication is working Lack of in-house expertise to meet the recovery metrics required by the business Benefit to Customer Protect only the resources needed Pay only for the virtual machines and storage they use Testing services can be conducted anytime, anywhere through the customer portal Recovery objectives as low as 15 minutes Portal integration w/fully automated recovery Need to create a tiered DR plan based upon the application priority Ability to create a custom DR plan that recovers VMs in the order specified 41

42 Additional Resources Download my free ebook about building an always on enterprise 42

43 FILL OUT A SURVEY EVERY COMPLETE SURVEY IS ENTERED INTO DRAWING FOR A $25 VMWARE COMPANY STORE GIFT CERTIFICATE

44 Disaster Recovery for All VMware vcenter Site Recovery Manager 5 Puts Real-Time Replication and Disaster Recovery Within the Reach of Every Business Craig McLellan, Hosting.com INF-BCO2065 #vmworldinf

Business Continuity and Disaster Recovery Disaster-Proof Your Business

Business Continuity and Disaster Recovery Disaster-Proof Your Business Jon Bock Senior Product Marketing Manager October 16, 2008 Agenda Disaster Recovery Requirements and Challenges Disaster Recovery