Calculating Downtime Costs: How Much Should You Spend on DR?
•Télécharger en tant que PPTX, PDF•
7 j'aime•3,324 vues
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (20)
En vedette
En vedette (6)
Similaire à Calculating Downtime Costs: How Much Should You Spend on DR?
Similaire à Calculating Downtime Costs: How Much Should You Spend on DR? (20)
Plus de Rackspace
Plus de Rackspace (20)
Dernier
Dernier (20)
Calculating Downtime Costs: How Much Should You Spend on DR?
- 1. 1 CALCULATING DOWNTIME COSTS: How much should you spend on DR? Paul Croteau – Enterprise Cloud Strategist Rackspace Hosting
- 2. 2 Agenda • Downtime: The Numbers • Building Your Case • Managing Expectations • Reference Architectures • Roles & Responsibilities • Q&A
- 4. 4 Outages Happen 59% of Fortune 500 companies experience a minimum of 1.6 hours of downtime per week, according to Dunn & Bradstreet.
- 5. 5 F500 2012 Hourly Loses Total 2012 Revenue = $11.75T Total 2012 Profit = $824B • Ave. F500 Revenue = $23.5B • Med. F500 Revenue = $10B • Ave. F500 Profit = $1B • Med. F500 Profit = $646M
- 6. 6 F500 2012 Hourly Loses Total 2012 Revenue = $11.75T Total 2012 Profit = $824B • Ave. F500 Revenue = $23.5B • Med. F500 Revenue = $10B • Ave. F500 Profit = $1B • Med. F500 Profit = $646M ($2.7M/hr) ($1.2M/hr) ($122k/hr) ($74k/hr)
- 7. 7 Minutes Matter • The average cost of data center downtime across industries: approximately $5,600 per minute. • For a partial data center outage, averaging 59 minutes in length, average costs were approximately $258,000. • For total data center outages, which had an average recovery time of 134 minutes, average hourly costs were approximately $680,000. • 93% of companies that lost their data for 10 days or more filed for bankruptcy within one year of the disaster, and 50% filed for bankruptcy immediately.
- 8. 8 Humans Make Mistakes Through 2015, 80% of outages impacting mission-critical services will be caused by people and process issues, and more than 50% of those outages will be caused by change/configuration/release integration and hand-off issues. – Gartner Research
- 9. 9 Building Your Case Quantifying Risk
- 10. 10 Do You Have A Plan? 41% of SMBs surveyed said that putting together a Disaster Recovery plan never occurred to them. Less than half of SMBs back up their data weekly or more frequently, and only 23% backup daily. Backups are not enough! The goal of a backup is to enable data restoration. A DR plan helps quickly restore operations. DR is a holistic strategy for restoring IT systems that powers business ops that includes people, process, policies and technology.
- 11. 11 From minutes to weeks Downtime Perspective How Resilient Is Your DR plan? – Device failure – Cabinet failure – Facility failure Time To Recovery
- 12. 12 Cost of Downtime Scenarios Annual Revenue App/Productivity Annual Revenue $15,000,000 Annual Revenue $75,000,000 Percentage of Revenue from Online 90% Number of employees 400 Average shopping hours per day 12 Annual revenue per employee $187,500 Annual total revenue hours 4380 Work hours per year (2000 hours/employee) 500,000 Cost of downtime per hour $3,082 Employee revenue per hour $150 Hours of downtime 10 Sales Lost Percentage employees affected by downtime 20% Duration of Event (days) 4 Cost of downtime per hour $375,000 Hours of event 96 Expected visits generated 500,000 Event Revenue Conversion rate (visits to purchase) 6% Expected Event Revenue $100,000 Average revenue per purchase $500 Event Duration (days) 3 Revenue per event $15,000,000 Event hours 72 Cost of downtime per hour $156,250 Cost of downtime per hour $1,389 If you don’t know your actual cost of downtime, you are wasting time.
- 13. 13 Annual Revenue Basis Cost of Downtime Scenarios Annual Revenue Annual Revenue $15,000,000 Percentage of Revenue from Online 90% Average shopping hours per day 12 Annual total revenue hours 4380 Cost of downtime per hour $3,082
- 14. 14 Cost of Downtime Scenarios Event Revenue Expected Event Revenue $1,000,000 Event Duration (days) 3 Event hours 72 Cost of downtime per hour $13,089 Single Event Revenue
- 15. 15 Cost of Downtime Scenarios Sales Lost Duration of Event (days) 4 Hours of event 96 Expected visits generated 500,000 Conversion rate (visits to purchase) 6% Average revenue per purchase $500 Revenue per event $15,000,000 Cost of downtime per hour $156,250 Sales Lost
- 16. 16 Cost of Downtime Scenarios App/Productivity Annual Revenue $75,000,000 Number of employees 400 Work hours per year (2000 hours/employee) 500,000 Employee revenue per hour $150 Annual revenue per employee $187,500 Hours of downtime 10 Percentage employees affected by downtime 20% Cost of downtime per hour $120,000 Productivity Basis
- 17. 17 Get The Downtime Calculator rackspace.com/dt-cost
- 24. 24 RPO / RTO Recovery Point Objective How much data is lost Recovery Time Objective How long to recover Weeks Days Hours Min Sec Sec Min Hours Days Weeks
- 25. 25 RPO / RTO Recovery Point Objective How much data is lost Recovery Time Objective How long to recover Weeks Days Hours Min Sec Sec Min Hours Days Weeks Tape Periodic Replication Snapshots Replication Clustering Snapshots Tape Restore
- 26. 26 RPO / RTO Recovery Point Objective How much data is lost Recovery Time Objective How long to recover Weeks Days Hours Min Sec Sec Min Hours Days Weeks Tape Periodic Replication Snapshots Replication Clustering Snapshots Tape Restore CostImpact
- 27. 27 RTO/RPO Cost Expectations HOT COLDWARM RTO RPO Tier • DNS Failover • Array-based Replication • Host-based Replication • DB Replication (Transactional) • DB Rep. (Log Shipping) $$$ $$ $ 0-24 2-6 0-24 4-24+ 24-48+ 1 2 3 4 0-2 • MBU (Disk) • VM Replication Price • MBU (Tape) • MBU (Offsite) Elements of DR, not an end-to-end solution Missing process, policies and procedures• GSLB
- 28. 28 Architectures Defined By Your Priorities
- 29. 29 Designing for Redundancy HA FirewallsHA Load Balancers Private Cloud DB Cluster Shared StorageDedicated Storage Hypervisor
- 31. 31 I need backup! DR Site Requirements How long must you depend on your DR site? How do you define your DR site requirements? DR = Insurance.
- 35. 35 Staging as Warm DR Prod DR
- 36. 36 Staging as Warm DR Prod DR
- 37. 37 Staging as Warm DR Prod DR
- 40. 40 Leverage Expertise Common questions from customers: Who owns the overall DR strategy? Who will design it? Who is going to manage and monitor it? Who will perform the failover?
- 41. 41 Designing Your DR Strategy Businesses own the strategy. Vendors enable the strategy. The strategy is unique to your needs. Testing matters.
- 42. 42 Prioritizing Content/Apps How do you prioritize? What are you protecting? – Business Operations – Revenue – Data – Customers – All of the above
- 43. 43 Roles & Responsibilities Role Responsibility DR Plan Failover Plan / Run Book Business “Pushing the failover button” Business Failover Process Partner Replication Applications Partner Virtual Machine Partner Database Partner Guest OS Partner Hypervisor Partner Server Partner Storage Partner Network Partner Data Center Partner
- 44. 44 Testing Companies don’t test their failover plan enough. Some replication services charge per test: expensive The failover/back process can be risky in production Risk dictates extensive planning around every test
- 45. 45 So, How Much Should You Spend On DR? How much revenue will you lose? How much else will you lose? How much can you afford? Based business decisions on fact, not emotion.
- 46. 46 Summary DR is Your Responsibility Know Your Cost of Downtime Prioritize Your Apps Select The Right Tools Select The Right Partner
- 47. 47 Rackspace Hosting A Diverse Portfolio
- 48. 48 The Rackspace Portfolio PRIVATE CLOUD PUBLIC CLOUD CUSTOMER PREMISE PARTNER DATA CENTER PRIVATE CLOUD PRIVATE CLOUD VIRTUALIZED VMware DEDICATED BARE METAL RACKSPACE DATA CENTER Powered by Powered by Powered by Powered by Powered by
- 49. 49 Q&A
Notes de l'éditeur
- Good afternoon and welcome. My name is Paul Croteau, I’m currently in my 9th year at Rackspace, the first 7 of those were spent as an Enterprise Solution Engineer…these days I work as a member of our product team helping to create technical content for our customers and the market as a whole. At the end of this session you will hopefully have a better understanding of how to asses your cost of downtime, you will have more clarity on the role a hosting provider plays in protecting your business, and will see where EMC fits into the equation.A QUICK SHOW OF HANDS: Raise your hand if you are here representing a small to medium business sized company. <WAIT> OK. My content today is very high level, I’m not going to dive into specific EMC storage management apps or hardware configuration settings. My goal today is to get you thinking about how to properly assess your cost of downtime, give you some tools or scenarios to help set expectations, and then your homework will be to take what you’ve learned and use that information to frame your DR solution architecture discussions back at the office. Let’s get started.
- Here’s our agenda.
- We know that data center outages and unplanned downtime are inevitable. IT downtime is like traffic. It’s not a matter of if it will happen, but when. There have been numerous public examples; we see it all the time in the news. Netflix suffered a very public and painful multi-hour outage last Christmas Eve. A variety of Amazon cloud outages have hit some very large and very popular web and social media properties. And thanks to social media, we can learn about and track the status of these outages and their recovery (or lack thereof) in real-time.InformationWeek published a study showing that IT downtime costs us $26.5 Billion in lost revenue every year. In another study by to Dunn and Bradstreet, 59% of Fortune 500 companies experience a minimum of 1.6 hours of downtime PER WEEK. That works out to more than 6 hours per month per company. LETS LOOK AT THE NUMBERS MORE CLOSELY.Source:Ronni J. Colville and George SpaffordConfiguration Management for Virtual and Cloud InfrastructuresAssessing The Financial Impact Of DowntimeBy Alan Arnold, in Analysis April 20, 2010http://www.businesscomputingworld.co.uk/assessing-the-financial-impact-of-downtime/IT Downtime Costs $26.5 Billion In Lost RevenueBy Chandler Harris InformationWeekMay 24, 2011 10:21 AM http://www.informationweek.com/storage/disaster-recovery/it-downtime-costs-265-billion-in-lost-re/229625441Network WorldHow much will you spend on application downtime this year?Aug. 2, 2009http://www.networkworld.com/newsletters/nsm/2009/080309nsm1.htmlOnline Banking Upgrade Contributed to Bank of America OutageOct. 2011Bank of America Corp., whose website has been down sporadically since last Friday, says the problem stems from technical hiccups, not a hack attack.BusinessNavitaire booking glitch earns Virgin $20m in compohttp://www.theaustralian.com.au/business/navitaire-booking-glitch-earns-virgin-20m-in-compo/story-e6frg8zx-1226033624246IT Downtime Costs $26.5 Billion In Lost RevenueBy Chandler Harris InformationWeekMay 24, 2011 10:21 AM http://www.informationweek.com/storage/disaster-recovery/it-downtime-costs-265-billion-in-lost-re/229625441------------------------------Target’s Online President Departs Following Website CrashTarget generates about 2% (or 1.35B) of its $67.4 billion revenue online.The day the revamped site went live, links such as “learn all about what’s new” didn’t work. On Sept. 13, the online store crashed when demand for products from the Italian fashion house Missoni exceeded expectations.Source: Bloomberg/Businessweek, 10/13/2011http://www.businessweek.com/news/2011-10-13/target-s-online-president-departs-following-website-crash.html------------------------------Navitaire booking glitch earns Virgin $20m in compo by: Teresa OoiApril 05, 201112:00AMRESERVATIONS management company Navitaire is understood to have compensated Virgin Blue for up to $20 million for a customer service meltdown that resulted in 130 cancelled flights and delays for more than 60,000 passengers in September.Source: The Australianhttp://www.theaustralian.com.au/business/navitaire-booking-glitch-earns-virgin-20m-in-compo/story-e6frg8zx-1226033624246
- Here is some 2012 financial data for the Fortune 500. Total Revenue was almost $12 T, total profit almost $1 T. <NEXT> Here are the Averages and Means. (ELABORATE) These are large numbers, so let’s break them down into smaller more digestible chunks. <NEXT> These are the HOURLY downtime averages and medians for the F500. (ELABORATE) If we go back to that BusinessWeek study I mentioned on the previous slide, 6 hours of downtime per month at the median costs more than $7M in revenue loss or more than $450k in lost profit per month. LETS LOOK AT SOME MORE NUMBERS. <NEXT>Dividing by 8760 hours in a year$1.2M/hr x (59% x 500 = 295) = $354M/wk x 52 = $18.4B/yr
- Here is some 2012 financial data for the Fortune 500. Total Revenue was almost $12 T, total profit almost $1 T. <NEXT> Here are the Averages and Means. (ELABORATE) These are large numbers, so let’s break them down into smaller more digestible chunks. <NEXT> These are the HOURLY downtime averages and medians for the F500. (ELABORATE) If we go back to that BusinessWeek study I mentioned on the previous slide, 6 hours of downtime per month at the median costs more than $7M in revenue loss or more than $450k in lost profit per month. LETS LOOK AT SOME MORE NUMBERS. <NEXT>Dividing by 8760 hours in a year$1.2M/hr x (59% x 500 = 295) = $354M/wk x 52 = $18.4B/yr
- <NEXT> According to InformationWeek, the average cost of unplanned downtime is about $5,600 per minute. Let’s take a look at a couple of outage scenarios, and the average cost associated with each. <NEXT> For a partial DC outage, the average downtime is about an hour and costs approximately $260,000. <NEXT> For a total DC outage, the average recovery time is over two hours and costs on average, $680,000. For larger companies, or companies with an ecommerce business model, that number could easily go much higher. What would that cost look like if you were down for a few days? Here’s a sobering factoid, <NEXT> “93% of companies that lost their data for 10 days or more filed for bankruptcy within one year of the disaster, and 50% filed for bankruptcy immediately.” What’s the main takeaway here? Your company’s survival depends on quantifying the impact of downtime. SO, DEPLOYING MORE TECHNOLOGY IS THE FIX FOR THIS? NOT NECESSARILY. <NEXT>(Source: National Archives & Records Administration in Washington.)According to InformationWeek, the average cost of unplanned downtime is about $5,600 per minute. Let’s take a look at a couple of outage scenarios, and the average cost associated with each. For a partial DC outage, the average downtime is about an hour and costs approximately 260 thousand dollars. For larger companies or companies with an ecommerce business model, that number could easily go much higher. For a total DC outage, the average recovery time is over two hours and costs on average, 680 thousand dollars. What would that cost look like if you were down for a few days? Here’s a sobering factoid: “93% of companies that lost their data for 10 days or more filed for bankruptcy within one year of the disaster, and 50% filed for bankruptcy immediately.”Your company’s survival depends on quantifying the impact of downtime.According to InformationWeek, the average cost of unplanned downtime is about $5,600 per minute. Let’s take a look at a few outage scenarios, and the average cost associated with each. For a partial DC outage, the average downtime is about an hour and costs approximately 260 thousand dollars. For larger companies or companies with an ecommerce business model, that number could easily go north of 6 figures per hour. For a total DC outage, the average recovery time is over two hours and costs on average, 680 thousand dollars. What would that cost look like if you were down for a few days? Here’s a sobering factoid: “93% of companies that lost their data for 10 days or more filed for bankruptcy within one year of the disaster, and 50% filed for bankruptcy immediately.”Your company’s survival depends on quantifying the impact of downtime.
- We also know that humans make mistakes, and Gartner predicts over the next several years the vast majority of outages impacting mission critical services will be caused by people and process issues, and more than half of these will be caused by change/configuration/release integration and hand off issues.You can deploy wonderfully reilient technology and still suffer downtime. What I want to do today is help you understand how much your inevitable downtime might cost your company so that you can determine how much to spend based on your business needs, financial needs, and your tolerance for risk. At the end of the day, the cost of any DR solution is analogous to an insurance policy. We may not like paying for it, but when you need it you are very happy you did so. <NEXT>Source:Ronni J. Colville and George SpaffordConfiguration Management for Virtual and Cloud InfrastructuresAssessing The Financial Impact Of DowntimeBy Alan Arnold, in Analysis April 20, 2010http://www.businesscomputingworld.co.uk/assessing-the-financial-impact-of-downtime/IT Downtime Costs $26.5 Billion In Lost RevenueBy Chandler HarrisInformationWeekMay 24, 2011 10:21 AM http://www.informationweek.com/storage/disaster-recovery/it-downtime-costs-265-billion-in-lost-re/229625441Network WorldHow much will you spend on application downtime this year?Aug. 2, 2009http://www.networkworld.com/newsletters/nsm/2009/080309nsm1.htmlOnline Banking Upgrade Contributed to Bank of America OutageOct. 2011Bank of America Corp., whose website has been down sporadically since last Friday, says the problem stems from technical hiccups, not a hack attack.BusinessNavitaire booking glitch earns Virgin $20m in compohttp://www.theaustralian.com.au/business/navitaire-booking-glitch-earns-virgin-20m-in-compo/story-e6frg8zx-1226033624246IT Downtime Costs $26.5 Billion In Lost RevenueBy Chandler HarrisInformationWeekMay 24, 2011 10:21 AM http://www.informationweek.com/storage/disaster-recovery/it-downtime-costs-265-billion-in-lost-re/229625441------------------------------Target’s Online President Departs Following Website CrashTarget generates about 2% (or 1.35B) of its $67.4 billion revenue online.The day the revamped site went live, links such as “learn all about what’s new” didn’t work. On Sept. 13, the online store crashed when demand for products from the Italian fashion house Missoni exceeded expectations.Source: Bloomberg/Businessweek, 10/13/2011http://www.businessweek.com/news/2011-10-13/target-s-online-president-departs-following-website-crash.html------------------------------Navitaire booking glitch earns Virgin $20m in compo by: Teresa OoiApril 05, 201112:00AMRESERVATIONS management company Navitaire is understood to have compensated Virgin Blue for up to $20 million for a customer service meltdown that resulted in 130 cancelled flights and delays for more than 60,000 passengers in September.Source: The Australianhttp://www.theaustralian.com.au/business/navitaire-booking-glitch-earns-virgin-20m-in-compo/story-e6frg8zx-1226033624246------------------------------
- OK, four slides of data, is anyone nervous yet? ;-) I’m building a case to help you understand the potential impact of downtime in real terms. We all understand that downtime is a problem, but the data I’m presenting here should move us get past the emotional aspects of the topic and help quantify the impact of downtime so that you can go to your technical and financial stakeholders with a compelling case to take action to protect your business and your customers.In my many years as an engineer/architect I’ve talked to thousands of customers of all sizes. One of the things that has remained constant in these interactions is the fact that so many of the people I’ve talked to had been so busy running their businesses that they never pulled the trigger on a DR plan. And sadly, some of those conversations I had took place after disasters took place and customers were trying to save what they could after the fact. TIME FOR SOME MORE NUMBERS. <NEXT>
- Here is some data from a 2011 Symantec SMB Disaster Preparedness Survey, when I first read this I was surprised. <NEXT> 41% of SMBs never thought about putting together a DR plan. <NEXT> Less than half backup weekly, less than ¼ backup daily. Granted. this may not be a surprise to some of you, as you know that depending on the amount of data your backing up, restore times can take many hours or even days. <NEXT> Backups are NOT enough. Your data may be protected but this approach doesn’t address downtime well. For some perspective, It’s difficult to say how long a restore will take b/c it depends on what kind of data your restoring, but on average on a 1Gbps network, restore time will take 60GB/hr.. <NEXT>Disaster recovery is a holistic strategy comprised of people, process, policies and technology. It’s focus is to restore IT systems critical to business function. In other words, it helps keep the business running after a major disruption. Remember a disaster could be mother nature’s wrath or a guy named Bob who installed a patch that broke a critical application. A DR Plan helps to keep the lights on and the company open for business. SO LETS TALK ABOUT RECOVERY PERSPECTIVE. <NEXT>
- You don’t get to choose the type of disaster that hits your business. <NEXT> You might suffer a localized failure like a single device, or a cabinet or two of damage due to a burst pipe or fire or electrical surge. <NEXT> Or, you might face a facility wide failure like a flood, cooling failure (melting servers), or massive explosion (bomb, plane, volcano). So, depending on the scale of the event, your IT team or outsourcing provider faces the task of replacing thousands of devices, or maybe even tens of thousands. ELABORATE on channel issues, manpower issues, MRR stack ranking, etc.AND, if you don’t have your data in more than a single data center, I don’t want to see you out there on Twitter griping about downtime. You can RAID this and cluster that, but when downtime hits, a single data center is still a single point of failure. Alright. We’ve seen how much downtime can cost, and we’ve seen that downtime is unpredictable. So WHAT THIS ALL BOILS DOWN TO: <NEXT>
- If you don’t know your actual cost of downtime, you are wasting time talking about or designing a DR solution. And you may be wasting money(maybe lots of money) if you spend too much on DR. Let’s look at some specific business scenarios with real dollars tied to them to help gain even more perspective. <NEXT>
- Here we have a company with annual revenue of $15M. Let’s assume this is an ecommerce site with limited retail space, where the vast majority of revenue comes from online sales. Since their market is mainly in the US, most of the committed transactions take place during business/daylight hours. So, assuming 12 hours of shopping every day, and 365 days per year, that gives us 4,380 peak shopping hours and a cost of downtime of just over $3000. (that’s 15M * 90% ,then divided by the total number of hours (4380), A 12 hour outage would mean more than $36k in lost revenue.AND, don’t forget to include the damage to your brand name, or lost future transactions for customers than went to a different vendor not just for this purchase but future purchases. LET’S LOOK AT ANOTHER SCENARIO. <NEXT>.
- Here’s some math for a single online event. This could be a weekend charity fund raiser, or an annual pledge drive. Assuming a goal of $1M, every our of this 72 hour event should generate an average of more than $13k. And with an event this short, you better have a quickly scalable solution, something that lets you move fast in more than one data center location. <NEXT>
- Here’s a different view on a single event, this time from the perspective of sales lost instead of pure revenue generation on the previous slide. Assume a four day online event, perhaps something over a holiday weekend. Lots of advertising dollars spent, print, television, online, etc. In this scenario we are using numbers that any good retail business should have readily available: things like historical web traffic stats, conversion rate percentages from click-through traffic, etc. Here we expect to see half a million visitors hitting our web property. We know in the past that we’ve had a great conversion rate of 6%. If the average price of our goods is $500 (maybe one of those fancy purses, or a wildly popular electronic device), we expect to generate $15M in sales over this four day period. And the math works out to more than $150k of downtime per hour. <NEXT>
- OK, last one. This one looks at downtime from a productivity basis. Instead of focusing on sales or e-commerce, let’s assume we are talking about an outsourced back office application. (financlal, CRM, email, etc.). Take your annual revenue and divide it by the number of employees you have. This gives us an average revenue per hour per employee. Now multply the number of hours of downtime by the percentage or number of employees affected by the outage and you get $120k/hr in this example. Now, these examples have been very general, you can poke all sorts of holes or throw exceptions out there. These aren’t meant to be specific examples, they are meant to show averages, and more importantly, to show different ways of thinking about this topic. Now, wouldn’t it be great if you had a worksheet or app that you could play with to enter your own numbers and see how much downtime might cost your business? <NEXT>
- This little web-based tool is available right now for you to try out. It’s a simple calculator with three of the business scenarios we just walked through. This link gets you to our DR Planning page, the link to the calc is down the page just a bit. Give it a try, see how things look, and feel free to use it to help get your point across to decision makers back home. <NEXT>
- I’ve spent a lot of time talking about financial numbers, now let’s look at things from a process perspective. We all agree that downtime needs to be avoided and that it can get expensive very fast. Therefore, businesses need to determine how fast they want to get back online after an outage, and how far back in time they need to go to recover data and resume normal operations. <NEXT>
- Here’s a common DR timeline of a generic business. Every week this company performs full data backups. <NEXT> Then an outage hits. Since this company isn’t using something really cool like VMware for virtualization with Site Recovery Manager, they have to rely on recovering data from backup tapes. Maybe the tapes are still on site and were not damaged. Or, perhaps the tapes are off-site. <NEXT> The company has a documented goal of resuming online operations within 60 hours of an outage. Plenty of time to get your tapes delivered and re-load al of your data. <NEXT> Unless your tape machine was destroyed by the disaster making your tapes useless until you replace that hardware. So, <NEXT> this company missed its desired RTO by 18 hours. <NEXT>
- Here’s a common DR timeline of a generic business. Every week this company performs full data backups. <NEXT> Then an outage hits. Since this company isn’t using something really cool like VMware for virtualization with Site Recovery Manager, they have to rely on recovering data from backup tapes. Maybe the tapes are still on site and were not damaged. Or, perhaps the tapes are off-site. <NEXT> The company has a documented goal of resuming online operations within 60 hours of an outage. Plenty of time to get your tapes delivered and re-load al of your data. <NEXT> Unless your tape machine was destroyed by the disaster making your tapes useless until you replace that hardware. So, <NEXT> this company missed its desired RTO by 18 hours. <NEXT>
- Here’s a common DR timeline of a generic business. Every week this company performs full data backups. <NEXT> Then an outage hits. Since this company isn’t using something really cool like VMware for virtualization with Site Recovery Manager, they have to rely on recovering data from backup tapes. Maybe the tapes are still on site and were not damaged. Or, perhaps the tapes are off-site. <NEXT> The company has a documented goal of resuming online operations within 60 hours of an outage. Plenty of time to get your tapes delivered and re-load al of your data. <NEXT> Unless your tape machine was destroyed by the disaster making your tapes useless until you replace that hardware. So, <NEXT> this company missed its desired RTO by 18 hours. <NEXT>
- Here’s a common DR timeline of a generic business. Every week this company performs full data backups. <NEXT> Then an outage hits. Since this company isn’t using something really cool like VMware for virtualization with Site Recovery Manager, they have to rely on recovering data from backup tapes. Maybe the tapes are still on site and were not damaged. Or, perhaps the tapes are off-site. <NEXT> The company has a documented goal of resuming online operations within 60 hours of an outage. Plenty of time to get your tapes delivered and re-load al of your data. <NEXT> Unless your tape machine was destroyed by the disaster making your tapes useless until you replace that hardware. So, <NEXT> this company missed its desired RTO by 18 hours. <NEXT>
- Here’s a common DR timeline of a generic business. Every week this company performs full data backups. <NEXT> Then an outage hits. Since this company isn’t using something really cool like VMware for virtualization with Site Recovery Manager, they have to rely on recovering data from backup tapes. Maybe the tapes are still on site and were not damaged. Or, perhaps the tapes are off-site. <NEXT> The company has a documented goal of resuming online operations within 60 hours of an outage. Plenty of time to get your tapes delivered and re-load al of your data. <NEXT> Unless your tape machine was destroyed by the disaster making your tapes useless until you replace that hardware. So, <NEXT> this company missed its desired RTO by 18 hours. <NEXT>
- So, when measuring how far back you need to go to get useful data, and how fast you want to resume business operations after a disaster, different technologies get you there in different amounts of time. <NEXT> Tape is at one end of the spectrum, on the outer limits of this timeline, while things like replication and clustering are closer to the center. <NEXT> And as you might expect, the faster you want to recover, the more money you will need to spend. And, the longer it takes you to recover, the deeper the potential financial impact. < NEXT>
- So, when measuring how far back you need to go to get useful data, and how fast you want to resume business operations after a disaster, different technologies get you there in different amounts of time. <NEXT> Tape is at one end of the spectrum, on the outer limits of this timeline, while things like replication and clustering are closer to the center. <NEXT> And as you might expect, the faster you want to recover, the more money you will need to spend. And, the longer it takes you to recover, the deeper the potential financial impact. < NEXT>
- So, when measuring how far back you need to go to get useful data, and how fast you want to resume business operations after a disaster, different technologies get you there in different amounts of time. <NEXT> Tape is at one end of the spectrum, on the outer limits of this timeline, while things like replication and clustering are closer to the center. <NEXT> And as you might expect, the faster you want to recover, the more money you will need to spend. And, the longer it takes you to recover, the deeper the potential financial impact. < NEXT>
- Here’s a graphic to help set cost expectations around certain technologies. Pricing ranges from hot to cold; the tier rankings are just a way to group things. The RTO and RPO numbers here are telling, because while DR recovery scenarios are unique, you generally find that each Objective falls into one of three timeframes: <ELABORATE ON RTO/RPO ROWS>. Array-based at storage layer / vSphere/VM replication = at Hype layerArray = replicate physical servers / vSphere cannot . Array configured per LUN or volume / Host = configured per VMArray = storage eng / VM = sys admin
- OK, we’ve covered lots of numbers so far. Let’s take a look at some architecture drawings. <NEXT>
- Walk the audience through the basics of redundancy throughout the typical hosting tiers, while pointing out EMC products in the mix. BUT, this focuses on a single data center, which is still a single point of failure.
- This slide expands the config to a second data center, points out a smaller DR config, plus the EMC technologies in play.
- Earlier I mentioned how we don’t get to choose our disasters. You might suffer a localized failure like a cabinet or two of damage due to a burst pipe or fire or electrical surge. Or, you might face a facility wide failure like a flood, cooling failure (melting servers), or massive explosion (bomb, plane, volcano). Now your provider faces replacing thousands of devices, or even tens of thousands, Channel issues, manpower issues, MRR stack ranking, etc. Don’t complain about downtime if you are running out of a single data center.
- This slide expands the config to a second data center, points out a smaller DR config, plus the EMC technologies in play.
- This slide expands the config to a second data center, points out a smaller DR config, plus the EMC technologies in play.
- This slide expands the config to a second data center, points out a smaller DR config, plus the EMC technologies in play.
- Showing how you can deploy Dev/Staging in a second DC and then use it as your DR site. Get more bank for your hosting dollar.
- Showing how you can deploy Dev/Staging in a second DC and then use it as your DR site. Get more bank for your hosting dollar.
- Showing how you can deploy Dev/Staging in a second DC and then use it as your DR site. Get more bank for your hosting dollar.
- If you need to depend on your DR location longer than expected, you can make it more robust.
- Here are the areas where Rackspace can lend a helping hand, and the areas that the customer must own. The top level is the holistic DR strategy. This is owned by the customer. Remember when we defined disaster recovery? It’s encompasses more than just the technology, but also the policies, people, and process. The customer is responsible for creating the DR plan, training the appropriate employees, and creating the failover run book, testing the failover often, making the “go-time” decision to failover after a disruption occurs, and then deciding to failback once the primary DC comes online. Rackspace is responsible for failing over to the Target DC once the authorization has been given by the customer. Rackspace also monitors the VM Replication virtual appliance, and alerts the customer when a replication fails to complete. As part of the Managed Virtualization service, Rackspace also manages the VM, guest OS, and hypervisor layer. In addition to the software layers, dedicated hardware, network and the DC is also covered. Failover is the customer’s responsibility but we assist and are on-call during the process.