Recovery As A Service: Should you move your Disaster Recovery to the Cloud?


Published on

Disaster Recover in the Cloud is a relatively new concept, and like many technology trends, there’s a lot of hype and misinformation out there. Steve Stavridis, Product Marketing Manager APAC at NetIQ recently presented on this topic at the Australia VMware vForum event, November 2012, in Sydney, Australia.

“Should you move your DR to the cloud?”. (Also available as a blog post series: captures what Steve spoke about in his presentation:

1. Should you move your DR to the cloud? (this post – introduction)
2. Nobody likes expensive insurance
3. Some DR fundamentals so we’re all on the same page
4. Virtualization has changed nearly everything …. including DR
5. Taking DR to the cloud
6. What are my cloud DR options?
7. The fundamentals of DR don’t change in the cloud (conclusion)

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • My name is Steve Stavridis and I am a Product Marketing Manager for NetIQ covering the Asia Pacific Region. I focus on our PlateSpin Disaster Recovery and server consolidation products.In my travels across the Asia Pacific region in recent months, I've been talking to several Managed Service/Cloud Providers and customers about Recovery as a Service.So today, I hope to share with you my views on “Recovery As A Service: Should you move your Disaster Recovery to the cloud?”Upon looking at the Agenda, I notice that some of the other vendors sponsoring this event are talking about this topic as well. I won’t comment on what is being covered in these other sessions but what I will say that:If you’re wanting to know about “Disaster Recovery in the cloud” thank you for coming today. You’ve chosen the right session … Disaster recovery in the cloud is a relatively new concept, and like many technology trends, there's a lot of hype and misinformation out there. Sit back, relax and I hope to make the session entertaining by sharing a story and telling some jokes of my mother in law – which you may or may not find entertaining!
  • So this is our Agenda that I have put together for our session today.To begin, we will take a look at some Disaster Recovery important concepts/acronyoms that are essential before delving into any Disaster Recovery discussion so we’re all on the same page We will look at the benefits of Virtual Disaster Recovery where we are able to leverage Disaster Recovery technologies to bridge the gap in traditional Disaster Recovery solutionsMoving on, we will take a look at how virtual Disaster Recovery has evolved into “Disaster Recovery in the cloud” – which is referred to as “Recovery as a service”What RaaS options are available today How can NetIQ help – what are some of the technologies that we offer that enable RaaS whether you are a user or a service provider here todayI will finish off by reviewing the question on “should you move your Disaster Recovery to the cloud” – how you can begin and which applications are a good fit for RaaS or “Disaster Recovery in the cloud”I will run for about 30 minutes and leave some time at the end for some questions.
  • Before delving any further, let’s go through some important Disaster Recovery important concepts/acronyms that are essential in any Disaster Recovery discussion so we’re all on the same page …….
  • The first is a Server workload.Workload:Workload – defineImportant today - Virtual & Physical – workload is decoupled from its underlying hardware – moves around – physical/virtual & cloudFurther in business - Workload /collection of workloads makes up a business service – what end-user consumes!Disaster Recovery is about protecting workloads whereas backup is about protecting data. In the event of an outage, we want to be able to bring up our entire server workload quickly and not just the data ……so server workload protection is key in Disaster Recovery .
  • Server workload protection is like having a spare tyre in your car.Disaster Recoveryaw analogy.Go through 3 steps.- Backup whole server workloads (data, application, operating system) into a warm standby consolidated virtual environment-Run the failed workloads directly off of the secondary system in the event of downtime in minutes- Restore the workload to original or new hardware in hoursImportant to failback ….several solutions on the market today are one way and don’t provide the fail back …. Keep running on your spare tire.Backup and restore is about protecting data. It covers steps 1 and 3 and struggles to adDisasterRecoveryess step 2 which is recovery – during the outage, how do I recover my workloads quickly so that users are able to continue to access business services.
  • So in Disaster Recovery – recovery is what its all about and we need a way to measure recovery time ….The 2 most important measures of recovery time are RPO & RTO.RPO - A measure of maximum acceptable data loss in terms of time (minutes, hours, days). An RPO of 4 hours means that the most recent backup has to be no more than 4 hours old at the time of an outage.RTO -The target maximum allowable time to recover from an outage. An RTO of 4 hours means systems have to be back up and operational no more than 4 hours after an outage.In addition to RTO & RPO, availability tiers are also important as they define uptime requirements or servers and applications, or maximum allowable downtime per year ……
  • So bringing together RTO, RPO and availability together, we essentially are able to map downtime and availability to Disaster Recovery technologies. Looking at the table up on the slide, what we realise is that traditional Disaster Recovery solutions today do a good job at adDisasterRecoveryessing opposite ends of the availability tiers leaving a big in the middle.Essentially high cost expensive duplication mirroring solutions provide near instantaneous recovery for servers that require 4 to 5 9’s availability. The trade-off is that these solutions are extremely expensive (clustering SAN replication and can be complex to manage).Low cost / low performance backup solutions tend to be used to for servers that can be offline for some time (one nine). The challenge with backup is that it really is about data restore and falls short for system recovery as a number of other things need to take place prior to bringing a system online.The gap in the middle is where traditional solutions fall short – the 15 minute to 4 hour recovery. More and more customers that I speak to are looking for an economical Disaster Recovery solution that fits in this recovery window.
  • So this gap in traditional disaster recovery is what Virtual Disaster Recovery technologies adDisasterRecoveryess.Virtualization has changed the way companies plan and execute disaster recovery (Disaster Recovery).The flexibility and consolidation in a virtual infrastructure makes virtual disaster recovery more efficient and cost-effective.With Virtual Disaster Recovery, we are able to achieve a low recovery time (low RPO/RTO ) that is close to replication at a price that is closer to backup.
  • 1. So let’s take a look at the benefits of Virtual Disaster Recovery a little closer 2. and how they bridge this 15 minute to 4 hours recovery gap.
  • The first benefit of Virtual Disaster Recovery is that we can get back to business faster. We don’t want downtime that = days or weeks.We do this by quickly creating an image of our production servers in the virtual environment and in the event of an outage, we essentially “powering” then on as a virtual machine in our recovery environment.This is achieved by Production source workloads being automatically replicated into virtual machines inside the recovery environment.Any changes to the source workload can be replicated to the VM across the network at a particular time interval as defined by the recovery policy.In the event of a production workload outage, we can failover (recover) the workload to a VM allowing users to continue accessing the server and business to continue in a matter of minutes.In the event of the original server being repaired, we can restore the workload to the original location or we could potentially restore the workload to dissimilar hardware.
  • The second benefit is that we remove risk fromDisaster Recovery by being able to trust our Disaster Recovery plans. Virtual Disaster Recovery does this by allowing for simple testing to be done without affecting production servicesAs they say - "any recovery is as good as the last tested backup". Most customers using traditional Disaster Recovery that I speak to test their Disaster Recovery perhaps once or twice a year at best.With Virtual Disaster Recovery , testing Disaster Recovery is a case of powering on a protected workload’s virtual machine at the recovery site in an isolated environment. Testing can be done on this workload without affecting production and ensures that in the event of a disaster, we can trust that our workload will work and come online. We can also validate our RPO and RTO for the workload.
  • The third benefit is that we can maintain control of Disaster Recovery by:Being able to demonstrate policy compliance that our production servers are protected (by simply running a report or logging into the Virtual Disaster Recovery system)In the event of a production workload outage, actionable alerts or failure notifications can be sent via email or to smart phone devices.Administrators can then initiate a failover operation remotely without even being onsite.With the control we have in Virtual Disaster Recovery, we can facilitate better management of our disaster recovery plan.And generate reports that you’re actually meeting your RPO’s and RTO’s as defined by the business.
  • The flexibility and consolidation in a virtual infrastructure makes virtual disaster recovery ideal for protecting all workloads – both virtual & physical running Windows & Linux.Virtual Disaster Recovery allows for a Universal solution allowing customers to leverage existing VMware infrastructure they may already own to provide a smarter, faster way to replicate and protect whole server workloads.
  • So extending on Virtual Disaster Recovery, I would like to take a look at its natural evolution in taking Disaster Recovery to cloud ….
  • So what is cloud based Disaster Recovery?Theterm "cloud-based disaster recovery" is very broad and there are many definitions.Forrester research have summarised it quite well and Cloud Based Disaster Recovery delivery falls into one of three categories being:1) Do-it-yourself (DIY): Using the public cloud to architect a custom failover solution leveraging the agility and speed of the cloud.2) Disaster Recovery-as-a-service (Disaster RecoveryaaS): Prepackaged services that provide a standard Disaster Recovery failover to a cloud environment that you can buy on a pay-per-use basis with varying rates based upon your recovery point objective (RPO) and recovery time objective (RTO). Data is either sent using backups or replication.The 3rd and more advanced … referred to as the silver lining in Cloud Disaster Recovery is 3)Cloud-to-cloud disaster recovery (C2C Disaster Recovery): The ability to failover infrastructure from one cloud data center to another, either within a single vendor's environment or across multiple vendors.I will focus on the second category being Disaster Recovery-as-a-service and take a look at how it’s evolved.
  • The first approach to Disaster Recovery-as-service or Disaster Recovery in the cloud is via Storage-as-a-service.Storage-as-a-service is essentially where an enterprise rents storage capacity from a cloud service provider at a fixed per-gigabyte cost. Instead of paying for hardware, physical storage space and personnel to manage the storage, an enterprise can effectively only pay for the capacity they consume and scale this up or down based on demand. This provides significant cost savings.The challenge when using Storage-as-a-service for Disaster Recovery is that just copying data to the cloud is not true recovery.If a local outage occurs, data needs to be copied to a recovery environment adding time and complexity to the recovery process.The core feature required of any cloud-based recovery is theability to actually recover the entire server workloads at the providers' location using their cloud assets.
  • This is where Recovery-as-service comes in.RaaS is the combination of SaaS and IaaSand offers enterprises the ability recover the entire server workloads at the providers' location using their cloud assets.RaaS includes the same advantages as Storage-As-a-Service – the main difference is that the entire server workload is protected and not just the data. So in terms of Disaster Recovery, RaaS is ideal as the entire workload is replicated, recovered and run in the cloud – in the event of an outage.
  • So RaaS is about cloud-based workload recovery.It provides the benefits of traditional offsite recovery at a fraction of the price!Cloud based workload recovery has the potential to adDisasterRecoveryess many of these concerns with traditional approaches. Cost being the main concern - by eliminating significant hardware and maintenance costs, they cut out large upfront capital expenses. Disaster Recovery then becomes a flexible, pay-as-you-go operating expense, where companies only pay for the capacity they consume, and can fine-tune or terminate services altogether on demand.Flexibility is next. Making the process easier, they can enable many overburdened IT organizations to actually get a Disaster Recovery solution deployed in the first place. Without having to wait for new hardware or software to come online.All in all, cloud-based workload recovery moves the discussion from data centre space and hardware to one about cloud capacity planning.
  • Earlier we saw the gap the Virtual Disaster Recovery fills when compared to traditional disaster recovery.RaaS is the next evolution of Virtual Disaster Recovery.By combining the benefits virtual infrastructure and cloud, RaaSoffers the befits of offsite Disaster Recovery at a fraction of the price!
  • So the benefits are great, what RAAS options are available today ?
  • The first option is Private / Hybrid RaaS.Essentially, this option involves dedicated backup hardware that is not shared between customers.The dedicated hardware resides at the service provider premises and is either owned/managed/maintained by the Service Provider or the customer.The workloads are replicated to the offsite facility and in the event of an outage, the workloads are recovered and run in the dedicated recovery environment.
  • The secondoption is Public RaaS.Essentially, this option involves shared backup hardware that is shared between customers. Or what is referred to as a Multi-tennented environment.The shared hardware resides at the service provider premises and is owned/managed/maintained by the Service Provider.The workloads are replicated to the offsite facility and in the event of an outage, the workloads are recovered and run in the shared recovery environment.
  • In the market, there are quite a few Disaster Recovery service providers.I have named a few up on the slide. Locally, it is interesting to observe what BlueFire and InfoPlex offer in terms of their Disaster Recovery-as-a-service offerings. They are both sponsors at this event so its worth having a chat with the guys at their booths about their Disaster Recovery-as-a-service offerings.
  • So whether you a customer or a Managed Service Provider, NetIQ provides relevant technology whether you’re investigating Virtual Disaster Recovery or looking at RaaS options.
  • The first is NetIQ PlateSpin Protect.PlateSpin Protect leverages the VMware infrastructure you already own to provide a smarter, faster way to replicate and protect whole server workloads – both physical and virtual.
  • The second isPlateSpin Forge.PlateSpin Forge is the PlateSpin Protect Software in the form of an appliance.It is a simple & inexpensive Disaster Recovery appliance for protecting up to 25 windows or Linux workloads per appliance.If you are looking at a private/hybribRaaS, Forge is ideal as the appliance can quickly be installed as a dedicated appliance installed at the service providers premises.Talk about success of Forge across APAC and customer verticals.
  • So to finish up, I will go back to the question in my presentation title: Should you move your Disaster Recovery to the cloud?Gartner states that by 2014, over 30% of midsize companies will have adopted Disaster Recovery in the cloud or recovery-as-a-service. Whether your business can take advantage of the benefits of RaaS will depend on taking a hard look at your Disaster Recovery needs and matching them to a service that fits.Whether you’re looking at traditional or RaaS solutions, the fundamentals of Disaster Recovery don’t change.It begins with a Disaster Recovery plan. When was the last time you looked at your Disaster Recovery plan? How well does it map to the RTO/RPO requirements for servers/applications ?In the event of an outage, how confident are you that your services will come back online as you expect ?RaaS – provides you with an opportunity to rethink how you are doing Disaster Recovery today.The other “80 %” that our friend Geoffrey neglected in his insurance policy, the non mission critical servers is a good place to start when considering RaaSPerhaps start small – choose a few servers – and test it to see if it makes sense for your business.If you’re a Service Provider building Private/Public Disaster Recovery in the cloud offerings, our PlateSpin technology is cloud ready and allows you to build RaaS offering into your portfolio.I will finish up by saying that implementing a Disaster Recovery solution is never simple. The emergence of cloud-based Disaster Recovery services can make it much easier, affordable and reliable. Let’s have a chat at the end of the session or visit our booth to further the conversation.
  • I will open up for questions.
  • Recovery As A Service: Should you move your Disaster Recovery to the Cloud?

    1. 1. Recovery As A Service: Should you move your Disaster Recovery to the cloud?Steve StavridisProduct Marketing Manager - APACsteve.stavridis@netiq.comTwitter: @sstavridis
    2. 2. Agenda1. Intro to Disaster Recovery (DR)2. Virtual Disaster Recovery3. Taking Disaster Recovery to the Cloud4. Recovery as a Service (RaaS) Options5. How NetIQ enables RaaS?2
    3. 3. Introduction to Disaster Recovery3
    4. 4. Definition: Server Workload Server workload: • the contents of a server, including the operating system, applications and data4
    5. 5. What is Workload Protection? Workload protection means: 1. Backup of entire server workloads, 2. Recovery of workloads to virtual machines during an outage, and 3. Restore of workloads to their original production locations after the outage.5
    6. 6. Key Disaster Recovery Concepts RPO: Recovery Point Objective • A measure of maximum acceptable data loss in terms of time (minutes, hours, days). RTO: Recovery Time Objective • The target maximum allowable time to recover from an outage. Availability tiers: 99.9%, 99.99%, Five 9’s, etc.6
    7. 7. Key Disaster Recovery Concepts: Downtime and Availability Availability Maximum Maximum Cost Products Typical Allowable Allowable RPO/RTO Downtime Downtime per Year per Month 90% (“one nine”) 36.5 days 72 hours 95% 18.25 days 36 hours 12-24 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”) 52.56 minutes 4.32 minutes <5 minutes 99.999% (“five nines”) 5.26 minutes 25.9 seconds 7
    8. 8. Traditional Disaster Recovery$$$$ Offsite Replication Expensive; requires a secondary site, redundant hardware (which is idle / under-utilized most of the time)Cost Local Replication Only good for individual server failure. No protection against site failures. Virtual Disaster Vaulting (tape, imaging) Recovery Recovery can take days or weeks. Difficult to test. $ Best RPO/RTO Worst 8
    9. 9. The Benefits of Virtual Disaster Recovery9
    10. 10. Get Back to Business As Usual Faster Recovery Failback to Failback with workload runs dissimilar sync to on virtual hardware repaired infrastructure hardware Virtual recovery (remote site)Internal web server Repaired Email server New web server 10
    11. 11. Trust Your Plans Rapidly test Testing logged Isolated testing recovery for reporting of recovery workloads and workloads compliance Virtual recovery (remote site)Internal web server Email server 11
    12. 12. Maintain Control Demonstrate Actionable Failure policy alerts notification compliance Virtual recovery (remote site)Internal web server Smart Email server phone 12
    13. 13. Protect All Your Workloads Windows Physical Universal or Linux or Virtual Solution Virtual recovery (remote site).Net Application server Block-based replication LAMP server File-based replication 13
    14. 14. Taking Disaster Recovery to the Cloud14
    15. 15. Cloud-Based Disaster Recovery Delivery Do-It-Yourself: Configure & manage your own solution using public cloud resources Disaster Recovery-as-a-Service: Prepackaged pay-as-you-go recovery services to the cloud with specified RPO & RTO SLAs Cloud-to-Cloud Disaster Recovery: Failover from one cloud environment toSource: Forrester (March 2012) another 15
    16. 16. Storage as a Service Advantages  Fixed per-gigabyte cost Disadvantages  Off-site cloud-based  Data only, not workloads storage  Static storage can’t run  Scale up or down on server workloads demand  If a local outage occurs,  Service provider data needs to be copied handles hardware to recovery environment maintenance, backups first16
    17. 17. Recovery as a Service (RaaS)RaaS = Storage as a Service + IaaS Advantages  Fixed per-gigabyte cost  Protect whole  Off-site cloud-based workloads, not just data storage  Replicate to the cloud,  Scale up or down on recover and run in the demand cloud  Service provider  Live restore back to handles hardware repaired data center maintenance, backups 17
    18. 18. Cloud Based Workload Recovery The benefits of offsite disaster recovery at a fraction of the price Offsite Replication Cloud RecoveryRecovery Minutes-Hours Minutes-HoursCost High: Fixed monthly price • Disaster Recovery site purchase / lease • Redundant hardware • Software licenses • Setup & monitoringMaintenance Hardware upgrades, None (done on the MSP side) maintenance contractsFlexibility New workloads need to wait Scale up or down on demand for hardware orders (or keep extra idle 18 hardware)
    19. 19. RaaS vs. Traditional Disaster Recovery$$$$ Offsite ProtectionCost Local Protection RaaS Vaulting $ Best RPO/RTO Worst 19
    20. 20. Recovery As A Service Options20
    21. 21. Private/Hybrid RaaS• Dedicated backup hardware at service provider premise• Scale by adding hardware• Hardware owned, managed, maintained by customer or service provider• Replicate workloads directly to offsite facility• Run recovery workloads in dedicated environment 21
    22. 22. Public RaaS Shared backup hardware at service provider premise Scale using service provider’s resource pool Hardware owned, managed, maintained by service provider Replicate workloads directly to offsite facility Run recovery workloads in shared environment 22
    23. 23. Cloud-Based DR Resources & Service Providers Do-It-Yourself DR as a Service  Amazon Web  Microsoft Windows Services Azure / Geminaire  Microsoft Windows  RackSpace Azure  CA  Rackspace  Vodacom  Carpathia Hosting  Bluefire   Infoplex 23
    24. 24. How NetIQ enables RaaS?24
    25. 25. NetIQ PlateSpin Protect Software based workload protection for Windows/Linux workloads Physical servers Virtual Image archives hosts Blade Workload decoupled servers from hardware Backup to Incremental One-click Easy to testvirtual machines replication failover 25
    26. 26. NetIQ PlateSpin Forge All in one Disaster Recovery appliance for Windows/Linux workloads World’s first disaster recovery hardware appliance with virtualization Protects up to 25 workloads Plug-in & protect solution for: PlateSpin Forge includes: • Storage • Medium enterprises • Replication software • Branch use for large enterprises • Hypervisor26
    27. 27. Should you move your DR to the Cloud?  Review your existing DR plan • How well does it map to the RTO/RPO requirements for servers/applications? Rethink how you are doing DR today • A good starting place to consider RaaS: • The “other” or 80% category (under-insured servers) • Start small with RaaS • Choose a few servers and test to see if it makes sense Building DR as a service offerings? • NetIQ can help Visit our booth 27
    28. 28. Thank You! Check out our FREE eBook: 5 Things You Need to Know Today AboutDisaster Recovery Planning