Home > Ask the Storage Technology Experts > Questions & Answers > What to consider when calculating availability
Ask The Storage Expert: Questions & Answers
EMAIL THIS

What to consider when calculating availability

Evan Marcus EXPERT RESPONSE FROM: Evan Marcus

Pose a Question
Other Storage Categories
Meet all Storage Experts
Become an Expert for this site


Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us   


>
QUESTION POSED ON: 07 May 2004
I am trying to calculate availability for a proposed system. The system is to be available for six days a week between 0600-2100 -- business hours. However, in the business hours, it is to be available within 30 minutes. If the system goes down, what would the availability be -- 1-30/17*6, 1-30/24*6 or 1-30/24*7?

>
I'm afraid that availability calculations don't really work the way you describe. You cannot calculate availability based on a recovery requirement, nor can you calculate it before the fact.

Availability calculations are traditionally a historic look back at how available a system was over a given period of time. The formula that is most commonly used is:

         MTTF
A = -----------------
      MTTF + MTTR 
Where "A" stands for the availability, presented as a percentage. "MTTF" is mean time to failure. That's the time that the system is actually operational and "MTTR" is the time it takes to repair, restore, or recover the system. Normally you only consider the period of time when the system was required to be operational.

So, if your system is down 30 minutes during a full seven days, 168 hour week, you would divide 167.5 (the uptime) by 168 (the total available time) and get 99.7%.

If the requirements were that the system be up only five days a week, eight hours a day, that same 30 minute outage would bring your availability number down to 39.5/40, or 98.75%.

In your question, you are not telling me how long the system was up. What you are asking is for a way to calculate availability based on a recovery time objective. If, in your example, the system were to recover in 30 minutes once in a week, your availability figure would be the 99.7% we discussed above. If instead, the system went down for 30 minutes every hour but never for longer than 30 minutes, you would still meet the Service Level Agreement you describe, but you'd only achieve 50% availability.

When you do us historical data to calculate uptime percentages, you should base them on the operational hours. So, I would use 90 hour weeks (6 * 15 hours) in my calculations. And. I would count any outage, scheduled or not, that occurred during those periods.

If I misunderstood your question, or if you have other questions, don't hesitate to ask. Evan L. Marcus

Editor's note: Do you agree with this expert's response? If you have more to share, post it in one of our discussion forums.


BROWSE BY TAG
High Availability,   Administrative Tools and Strategies,   Data Protection,   Disaster recovery and planning,   VIEW ALL TAGS

Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us   



RELATED CONTENT
High Availability
Clustering products for Windows
Calculating parallel availability
Making a case for high-quality failover management software
Evaluating clustering software products
Increasing uptime in the data center with a SAN
Automating site-to-site failover
Stretch clustering with host-based mirroring
Implementing an active/active data center
Implementing bi-directional data replication
Upgrading from GroupWise to Exchange 2003

Disaster recovery and planning
Virtualize disaster recovery
Backup in a snap: A guide to snapshot technologies
Storage Decisions Chicago 2009 Session Downloads
Storage Decisions Session Downloads: Disaster Recovery Track (Chicago 2009)
Storage Decisions Session Downloads: Data Retention & Retrieval Track (Chicago 2009)
More testing, more confidence for DR plans
The under-over on DR
Best storage Products of the Year 2008
Disaster recovery site options
DR for virtualized servers

RELATED GLOSSARY TERMS
Terms from Whatis.com − the technology online dictionary
application-aware storage  (SearchStorage.com)
bare metal restore  (SearchStorage.com)
Business Continuity and Disaster Recovery (BCDR)  (SearchStorage.com)
cold backup  (SearchStorage.com)
continuous data protection  (SearchStorage.com)
hot backup  (SearchStorage.com)
online backup  (SearchStorage.com)
recovery  (SearchStorage.com)
recovery point objective  (WhatIs.com)
recovery time objective  (WhatIs.com)

RELATED RESOURCES
2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems
Search Bitpipe.com for the latest white papers and business webcasts
Whatis.com, the online computer dictionary



Search and Browse the Expert Answer Center
Search and browse more than 25,000 question and answer pairs from more than 250 TechTarget industry experts.
Browse our Expert Advice



Search for Data Management Tools
TechTarget Storage Media
Storage Magazine View this month\\'s issue and subscribe today.
Storage Decisions Apply online for free conference admission.
SearchStorage.com
HomeNewsMagazineTopicsLearningMultimediaWhite PapersBlogsEventsAbout Us

About Us  |  Contact Us  |  For Advertisers  |  For Business Partners  |  Site Index  |  RSS
TechTarget provides technology professionals with the information they need to perform their jobs - from developing strategy, to making cost-effective purchase decisions and managing their organizations' technology projects - with its network of technology-specific websites, events and online magazines.

TechTarget Corporate Web Site  |  Media Kits  |  Site Map




All Rights Reserved, Copyright 2000 - 2010, TechTarget | Read our Privacy Policy
  TechTarget - The IT Media ROI Experts