drj logo
drj logo

Welcome to DRJ

Already registered user? Please login here

Create new account
(it's completely free). Subscribe

x

Be Wary of Being Arbitrary When Choosing RTOs

Business Continuity ManagementCyber Resilience & IT Disaster RecoveryData Protection: Backup & Recovery

Few business continuity (BC) tasks exceed the importance or visibility of determining the recovery time objective (RTO). Unfortunately, dysfunctional practices can creep into this process and cause "arbitrary" RTOs to be created. Three key examples of arbitrary RTOs include those which are "calculated," "open-ended," and "elongated."

For an arbitrarily calculated RTO, a BC planner uses an application or software tool to compute it. Based on inputs (such as dependencies, relative criticality or risk, etc.), the tool determines that a particular RTO is required. These inputs are important considerations, but they do not entitle the planner to dictate an organization's RTO.

During my military service, I often participated in decision briefings for senior leaders in which the presenter described courses of action for the commanding officer's approval. Never did anyone say, "General, you must choose this option because my spreadsheet says so." To make that statement would have insulted the leader's competence and authority, decreased consideration of other options, and probably jeopardized the presenter's longevity in that role.

The arbitrary calculation approach does not consider whether its mandate is feasible. Its RTO may be practically impossible to achieve or prohibitively expensive, due to organizational or external constraints.

Methods can vary, but the norm seems to be that the business continuity management program (BCMP) doesn't fund the organization's recovery strategies. The "lines of business" or departments have that responsibility. In those instances, an infeasible computed RTO adds insult to injury. To update the earlier "general" example: "Mr./Ms. Managing Director, my spreadsheet requires your team to recover in four hours. Your budget has to fund it."

The discussion of facts, which are impartially presented, should lead rational people to similar conclusions. While the BC planner may recommend an RTO based on any number of logical considerations, the organization's leadership is best able to balance stakeholder expectations and the cost of the recovery strategy, when determining the urgency of recovery.
An open-ended RTO (such as "greater than 96 hours") has no upper boundary. I call this approach a "recovery time cop-out" because it is not a measurable objective. For instance, no citizen would want a minimum income tax rate of "greater than 25 percent."

In an example where an application RTO is a "greater than 96 hours," the application users probably would expect recovery in "96 hours" and ignore the "greater than." Conversely, the supporting technology team might prioritize this application's recovery whenever they "could get to it," after addressing more urgent tasks; 96 hours could be their minimum target. An open-ended RTO creates uncertainty and unshared expectations.

An arbitrarily elongated RTO exists when its duration is based solely on relative importance or prioritization of the function/application. In this situation, the BCMP could specify that all Priority 1 functions must recover within 24 hours, all Priority 2 functions within 48 hours, etc.

To be clear, there are many circumstances where this approach makes sense. Whenever it is not possible to recover everything at once, more important activities must take priority. These are a few of many factors which can compel organizations to prioritize recovery activities: recovery sites with limited seating; recovery sites located outside commuting distance; and the expense of recovery hardware and software.

Yet, artificially lengthened RTOs also may decrease the sense of urgency of lower priority teams to support the recovery effort. If a lower priority team could recover in four hours, it is unwise to lengthen the RTO solely because the team's priority put it in a "less than 48 hours" category. Should the teams with arbitrarily long RTOs conclude they can relax, while everyone else is responding to the outage? The BCMP must prioritize critical recovery without suppressing less important activities, provided the latter can occur without hindering the former.

Allowing arbitrarily calculated, open-ended, or elongated RTOs to exist in a BCMP can cause the your team to appear insensitive, disrespectful, inflexible, unreasonable, or even detached from reality. Organizations must diligently and prudently develop selection and approval procedures for recovery time objectives. Determining RTOs should provide opportunities to collaborate with our colleagues and achieve consensus on the best outcomes. These potentially positive discussions should not be arbitrarily sub-optimized.

Lady Frank opt126289Frank Lady (bcjfrank@gmail.com) is a senior vice president of business continuity at Bank of America, the chair of the Editorial Advisory Board and its Glossary of Terms Committee, and a non-voting board member of the BCI-US chapter. The author greatly appreciates, and has included suggested refinements from James O. Price, Jr.

Latest News
DRJ HOT ITEMS
Webinar Spotlight
Fetching Upcoming Webinars...
Journal Categories

AI: Automation & Innovation

Business Continuity Management

Crisis Management & Emergency Response

Cyber Resilience & IT Disaster Recovery

Leadership: Culture & Workforce Resilience

Operational Resilience

Risk Management & Quantification

Sector-Specific & Critical Infrastructure Resilience

Supply Chain & Third-Party Resilience

Governance: Compliance & Regulatory Readiness

Incident Management & Response Coordination

Resilience Strategy & Program Maturity

Data Protection: Backup & Recovery

Exercises: Testing & Scenario Planning

Emerging Threats: Geopolitical & Climate Risk

Contact Us

Newsletter

The Journal, right in your inbox.