Your Cloud Availability: 99.99%, 99.9999% or 98%

We are interested in hearing your point of view. First and foremost, it is essential to ask, what do you consider “downtime”? How do you approach the matter of downtime with your customers? How do you compensate, if at all? Maybe even before discussing compensation, let us ask how or if you measure downtime? If so, are you able to calculate your own availability over the past week, month, or year? With your help, we can gain even greater insights on the topic. Start here

Transcript

1. Your  Cloud   Availability:   99.99%,   99.9999%  or   98%   ?     I  am  OnDemand  
2. Many  Ques<ons   In  this  cloud  market  stage  Business  Con<nuity   in  the  cloud  is  a  very  interes7ng  subject  since   the  market  is  s7ll  young  and  the  tradi7onal  tools   and  percep7ons  don’t  apply.       S7ll  many  ques7ons  arose  in  regards  to  specifics   on  the  topic  of  cloud  market  maturity.     I  am  OnDemand  
3. What’s  Down<me?   The  nines  (99.99...%)  are  more  marke7ng  than  the   real  deal  today.       The  concept  of  availability  in  the  cloud  is   determined  by  the  level  of  responsibility  and   liability  that  the  vendors  have  for  their  customers.      At  a  very  basic  level,  it  is  when  the  system  is  not   available.  However  depends  on  the  cri7cality  of   specific  features  and  components  of  an  applica7on   or  service.     What  do  you  think?     I  am  OnDemand  
4. What’s  Down<me?   •  What  do  you  consider  “down7me”?     •  How  do  you  approach  the  maNer  of  down7me   with  your  customers?     •  How  do  you  compensate,  if  at  all   •  How  or  if  you  measure  down7me?     •  Are  you  able  to  calculate  your  own  availability   over  the  past  week,  month,  or  year?       Start  here   I  am  OnDemand  
5. RTO  and  RPO  –     Nothing  Really  Changes     Recovery  Time  Objec<ve  (RTO)  is  the  dura7on  of   7me  and  a  service  level  within  which  a  business   process  must  be  restored  aOer  a  disaster  (or  disrup7on)  in   order  to  avoid  unacceptable  consequences  associated  with   a  break  in  business  con7nuity.     Recovery  Point  Objec<ve  (RPO)  It  is  the  maximum   tolerable  period  in  which  data  might  be  lost  from  an  IT  service   due  to  a  major  incident.   I  am  OnDemand  
6. RTO  and  RPO  –     Nothing  Really  Changes     The  cloud  changes  the  ways  in  which  you  achieve   op7mal  levels  of  RPO  and  RTO.  There  are  ways   now-­‐a-­‐days  to  deliver  robust  solu7ons  at  a  very  low   cost.         Keeping  the  applica7on,  and  its  actual  business   values,  in  mind,  you  can  address  both  RPO  and  RTO   and  make  sure  that  you  define  and  measure  these   metrics.       What  are  your  targeted   RTO  and  RPO  goals?     I  am  OnDemand  
7. DR  Cost  Impacts  and  ROI   When  you’re  an  online  retailer,  every  moment   that  your  website-­‐relevant  func7onali7es  are   down,  you  lose  money.       “…breaks  down  to  about  $120,000  per  minute.  Mul7ply  that  by   the  40  minutes  Amazon  went  down  and  you  get  around  $4.8   million  in  lost  dollars.”  Geekwire  release  following  Amazon  down7me  on  Aug-­‐2013   I  am  OnDemand   What’s  your  es7mated  cost  of  down7me?  
8. DR  Cost  Impacts  and  ROI   A  good  DR  deployment  on  the  cloud  should  be   based  on  the  pay-­‐per-­‐use  cloud  principle.       Cloud  users  can  avoid  tradi7onal  costs  by  using   an  “On-­‐demand  DR”  or  changing  their  DR   strategy  and  architecture.     I  am  OnDemand   Do  you  know  your  monthly  DR  costs?    
9. Calling  All  CIO/CTO/IT  Leaders  and   team  members:   To  see  how  your  disaster  recovery  and  backup   strategy  compares  to  your  peers,     Par7cipate  in  CloudEndure’s  Survey   I  am  OnDemand