"You can fool some of the people all of the time, and all of the people some of the time, but you cannot fool all of the people all of the time."
Abraham Lincoln
Some of the outage figures quoted by organizations look ludicrously small to me. Without casting aspersions on the veracity of these figures (or availability statistics), I do feel that some examination of them is needed.
The non-availability of a system is often quoted thus:
where MTTR is the Mean Time To Repair a particular outage.
”We recognized we'd run the wrong job and restarted correctly in just 3 minutes, thus our MTTR = 3 minutes."
If you substitute the word "recover" for "repair" in the above definition you will be closer to the truth. However, your database(s) are almost certainly on Planet Zog as far as consistency is concerned and the "repair" of that will often take much longer. The correct definition of MTTR should be "mean time to recover" and the equation then looks as above but with a new MTTR:
The last item in this equation I call the ramp up time, the time to get the show back on the road. This can be small but is often much larger than repair time, as shown in the diagram below. A decent Service Level Agreement (SLA) will opt for this definition of "fixed" for an issue and will include the ramp up time in the recovery time specification.
The recovery of a database or other data and metadata corrupted by human error or malware can take a considerable time to restore to the working status demanded by the end users.
This is borne out by several “Never Again” cases outlined in the Availability Digest (under the heading: Never Again) where financial bodies — banks, stock dealings — have repaired faults but taken many hours to recover normal working conditions again. ”The system was repaired at 11am and trading commenced normally at 2:30pm" is a typical (hypothetical) report on such situations.
The final point to make is that there are several viewpoints of an “outage” or period of "downtime", depending on your place in an organization. The end user's view will be that the outage lasts as long as he/she is prevented from using IT to do the job they are supposed to do. The server specialist's view might be that the outage of his hardware was a mere minute or two before it was fixed whereas the network person will say" “what's all the fuss about; everything on the network is working fine?”
It all depends on your viewpoint and I know what viewpoint the company CEO, the users and the board will take. Do you?
Dr. Terry Critchley is the Author of “High Availability IT Services” ISBN 9781482255904 (CRC Press).
The Latest
If you were lucky, you found out about the massive CrowdStrike/Microsoft outage last July by reading about it over coffee. Those less fortunate were awoken hours earlier by frantic calls from work ... Whether you were directly affected or not, there's an important lesson: all organizations should be conducting in-depth reviews of testing and change management ...
In MEAN TIME TO INSIGHT Episode 11, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses Secure Access Service Edge (SASE) ...
On average, only 48% of digital initiatives enterprise-wide meet or exceed their business outcome targets according to Gartner's annual global survey of CIOs and technology executives ...
Artificial intelligence (AI) is rapidly reshaping industries around the world. From optimizing business processes to unlocking new levels of innovation, AI is a critical driver of success for modern enterprises. As a result, business leaders — from DevOps engineers to CTOs — are under pressure to incorporate AI into their workflows to stay competitive. But the question isn't whether AI should be adopted — it's how ...
The mobile app industry continues to grow in size, complexity, and competition. Also not slowing down? Consumer expectations are rising exponentially along with the use of mobile apps. To meet these expectations, mobile teams need to take a comprehensive, holistic approach to their app experience ...
Users have become digital hoarders, saving everything they handle, including outdated reports, duplicate files and irrelevant documents that make it difficult to find critical information, slowing down systems and productivity. In digital terms, they have simply shoved the mess off their desks and into the virtual storage bins ...
Today we could be witnessing the dawn of a new age in software development, transformed by Artificial Intelligence (AI). But is AI a gateway or a precipice? Is AI in software development transformative, just the latest helpful tool, or a bunch of hype? To help with this assessment, DEVOPSdigest invited experts across the industry to comment on how AI can support the SDLC. In this epic multi-part series to be posted over the next several weeks, DEVOPSdigest will explore the advantages and disadvantages; the current state of maturity and adoption; and how AI will impact the processes, the developers, and the future of software development ...
Half of all employees are using Shadow AI (i.e. non-company issued AI tools), according to a new report by Software AG ...
On their digital transformation journey, companies are migrating more workloads to the cloud, which can incur higher costs during the process due to the higher volume of cloud resources needed ... Here are four critical components of a cloud governance framework that can help keep cloud costs under control ...
Operational resilience is an organization's ability to predict, respond to, and prevent unplanned work to drive reliable customer experiences and protect revenue. This doesn't just apply to downtime; it also covers service degradation due to latency or other factors. But make no mistake — when things go sideways, the bottom line and the customer are impacted ...
