Severity Definitions and Disaster Recovery Timeline Template

1 Download

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

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.

View the Complete Blueprint:

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.

Related Content

Visit our IT Cost Optimization Center
Over 100 analysts waiting to take your call right now: 1-519-432-3550 x2019