Build a Better Disaster Recovery Plan to Improve RTO & RPO Lubomyr Salamakha

Size: px

Start display at page:

Download "Build a Better Disaster Recovery Plan to Improve RTO & RPO Lubomyr Salamakha"

Brittany Greene
5 years ago
Views:

1 Build a Better Disaster Recovery Plan to Improve RTO & RPO Lubomyr Salamakha Sales Engineer lubomyr.salamakha@netiq.com May 14 th,2013

2 Agenda Who is NetIQ Why Downtime Matters What is Workload Protection Understanding Disaster Recovery NetIQ Disaster Recovery Solutions 2

3 Who is NetIQ?

Management Collaboration File and Networking

4 Attachmate Group, Inc. Terminal Emulation Legacy Modernization Managed File Transfer Enterprise Fraud Management Identity, Security and Compliance Management IT Operations Management Collaboration File and Networking Services Endpoint Management Enterprise Linux Servers Software Appliances Linux Desktops 4

5 Scale to Deliver A Culture to Care Established software vendor that has the scale to execute our strategy and the focus to deliver on customer s expectations

6 SCALE 1,800 DISASTER RECOVERY CUSTOMERS PlateSpin Forge and PlateSpin Protect SCALE TO DELIVER, A CULTURE TO CARE. 6

7 Downtime Matters!

8 Why Downtime Matters - UPDATE $41.3 Billion Total economic damage from disaster in 2009* $10.8 Billion Economic impact felt in the U.S. from disasters in 2009* *September 2, 2010, Business Continuity and Disaster Recovery are top IT Priorities for 2010 and Forrester 8

9 Becoming a Priority 78% of enterprises have indicated that improving disaster recovery capabilities is a high priority* Critical Priority 30% - High Priority 48% Better able to identify and quantify risk Better understanding of economic impact Less tolerance for downtime and data loss *Jan. 25, 2010 The State of Enterprise IT: 2009 to Forrester 9

10 What is Workload Protection?

11 What is Workload Protection? Workload protection means: 1. Backing up entire server workloads (the contents of a server, including the operating system, applications and data), 2. Recovering them to virtual machines during an outage, and 3. Restoring them to their original production locations after the outage. 11

state Data in system lost at disaster time Amount of data entered since last backup

12 Define Your Objectives Recovery Time Objective (RTO) Recovery Point Objective (RPO) Time between declaration and service availability Time to restore services to useable state Data in system lost at disaster time Amount of data entered since last backup Test Time Objective (TTO) Time required to test recovery plans Resources used for testing 12

13 Key Disaster Recovery Concepts: Downtime and Availability Availability Maximum Allowable Downtime per Year Maximum Allowable Downtime per Month Cost Products Typical RPO/RTO 90% ( one nine ) 36.5 days 72 hours 95% days 36 hours hours 99% ( two nines ) 3.65 days 7.2 hours 99.5% 1.83 days 3.6 hours 15 minutes to 4 hours 99.9% ( three nines ) 8.76 hours 43.2 minutes 99.99% ( four nines ) minutes 4.32 minutes % ( five nines ) 5.26 minutes 25.9 seconds 13

14 Understanding Disaster Recovery

15 Backup Your Data Focus is on protecting data Tape backup Imaging Poor performance Slow RTO, RPO (days) Hidden costs How do we get the data back in to a useable state? How long to rebuild server? 15

16 Double Infrastructure Focus is on protecting application Clustering Like-for-like infrastructure Performance, but at what price? Near-zero RTO, RPO High cost Duplicate infrastructure Management complexity 16

17 Bridging the Gap Duplication Fast RTO and RPO Duplicate resources Costly and complex Backup Slow RTO and RPO Over commitment of recovery resources 17

18 Disaster Recovery Performance Needs 87% of the enterprises surveyed have RTO for their mission-critical applications/services as four hours or less RTOs of Mission-Critical Applications (n=93) Source: Gartner (August 2011) 18

19 Disaster Recovery Solutions

20 Consolidated Recovery Virtual production servers Physical production servers Virtual recovery hosts Solution Replicate workload into an offline virtual machine One-click failover One-click test restore Flexible failback Physical production servers 20

21 PlateSpin Disaster Recovery Solutions that replicate whole workloads into local or remote virtual environment (over WAN) Can replicate changes on hourly, daily or weekly basis Testing recovery plans provides peace of mind Can restore business operations in minutes Leverages existing investments in virtualization 21

22 PlateSpin Protect Whole-workload protection for all server workloads. Physical servers Virtual hosts Blade servers Workload decoupled from hardware Backup to virtual machines Incremental replication Easy to test One-click failover 22

solution for : Medium enterprises Branch use for large enterprises

23 PlateSpin Forge World s first disaster recovery hardware appliance with virtualization Protects up to 25 workloads Plug-in and protect solution for : Medium enterprises Branch use for large enterprises PlateSpin Forge includes: Storage Replication software Hypervisor 23

24 The (Very) Real Benefits of Virtual Disaster Recovery

How PlateSpin Protect Works Consolidate Recovery Users Production Server

a secondary virtual environment Users Production Server Secondary

they run as expected Production Server Secondary Environment Step 3:

25 How PlateSpin Protect Works Consolidate Recovery Users Production Server Secondary Environment Step 1: Replicate servers (physical or virtual) into a secondary virtual environment Users Production Server Secondary Environment Step 2: IT admin tests workloads in new environment to ensure they run as expected Production Server Secondary Environment Step 3: Production server goes down, power up virtual machines in secondary environment in minutes 25

to the failed-over workload Step 3: Perform incremental failback

26 Failback, Test and Cut Over Step 1: Failback the workload Step 2: Test the workload in production, while users are still connected to the failed-over workload Step 3: Perform incremental failback to sync changes and switch users over to the production workload 26

A virtual environment OR Physical Server - IBM OR

27 Failback Flexibility Failback can be used to restore workloads to: The same or different physical hardware A virtual environment OR Physical Server - IBM OR Physical Server - Dell Virtual Host: ESX, Hyper-V, Xen 27

28 Thank You! Lubomyr Salamakha Solution Engineer 28

29 Worldwide Headquarters 1233 West Loop South Suite 810 Houston, TX USA (Worldwide) (Toll-free) NetIQ.com 29

30 This document could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein. These changes may be incorporated in new editions of this document. NetIQ Corporation may make improvements in or changes to the software described in this document at any time. Copyright ActiveAudit, ActiveView, Aegis, AppManager, Change Administrator, Change Guardian, Compliance Suite, the cube logo design, Directory and Resource Administrator, Directory Security Administrator, Domain Migration Administrator, Exchange Administrator, File Security Administrator, Group Policy Administrator, Group Policy Guardian, Group Policy Suite, IntelliPolicy, Knowledge Scripts, NetConnect, NetIQ, the NetIQ logo, PSAudit, PSDetect, PSPasswordManager, PSSecure, Secure Configuration Manager, Security Administration Suite, Security Manager, Server Consolidator, VigilEnt, and Vivinet are trademarks or registered trademarks of NetIQ Corporation or its subsidiaries in the United States and other countries.

CAS8490 Delivering Recovery as a Service (RaaS) November 2014

CAS8490 Delivering Recovery as a Service (RaaS) November 2014 Gary Ardito Chief Architect Cloud Service Provider Solutions Jo De Baer Product Management Agenda The opportunity for Recovery as a Service