Trial lock

This Research is for Members Only

Not a member? Unlock a free sample of our research now!

Already a member?

Sign in now

The vast majority of extended service interruptions are caused by relatively minor events, such as hardware or software failures, not major events, such as natural disasters. The challenge is recognizing when to escalate those incidents to your DR procedures.

IT leaders can fall victim to the “IT hero” and the familiar refrain of “I just need five more minutes to fix this,” and wait too long to failover to a standby system or hot site. Similarly, if there is a local power or network outage, and maintenance crews estimate a couple hours to repair the problem, do you wait or start preparing to failover to standby systems or a DR hot site?

The solution is to better integrate service management and DR processes. To that end, this template provides a framework for updating severity definitions and response times to meet DR requirements.

Also In

Bridge the Gap between Service Management & Disaster Recovery

Treating DR as separate from normal IT operations leaves organizations vulnerable to common causes of extended service interruptions.

Solution Set Steps

  1. Bridge the gap between service management and disaster recovery
  2. Identify system criticality and set RPO and RTO requirements
  3. Account for disaster scenarios in your severity definitions and response times
    • Severity Definitions and Disaster Recovery Timeline Template

Hide Details

Search Code: 55255
Published: June 19, 2012
Last Revised: June 19, 2012


Get Access

Get Instant Access
To unlock the full content, please fill out our simple form and receive instant access.