Unlock Bridge the Gap between Service Management & Disaster Recovery

Get Instant Access

Do not fill in this field

Full Name

Email

Company

Phone

Job Function

Job Title

IT Staff

Country

Yes. I would like to receive email updates from Info-Tech Research Group that include advice
and resources to help systematically improve my IT department.
You may unsubscribe at any time. By clicking the "Unlock" button, you are agreeing to the Info-Tech Research Group Terms of Use and Privacy Policy.

Bridge the Gap between Service Management & Disaster Recovery

Unlock Bridge the Gap between Service Management & Disaster Recovery

Get Instant Access

Do not fill in this field

Full Name

Email

Company

Phone

Job Function

Job Title

IT Staff

Country

Yes. I would like to receive email updates from Info-Tech Research Group that include advice
and resources to help systematically improve my IT department.
You may unsubscribe at any time. By clicking the "Unlock" button, you are agreeing to the Info-Tech Research Group Terms of Use and Privacy Policy.

Your Challenge

If a tornado destroys your data center, that’s an obvious DR scenario. However, the vast majority of extended service interruptions are caused by relatively minor events, such as hardware issues, isolated power or network outages, etc., that typically fall initially under service management procedures.

IT leaders can fall victim to the “IT hero” and the familiar refrain of “I just need five more minutes,” or maintenance crews promising that it should only take a couple hours to restore power or network connectivity, and wait too long to initiate DR procedures.

On the other hand, declaring a disaster is rarely a no-cost scenario, and should not be done lightly. For example, vendors often apply a surcharge to activate a hot site. At the very least, it’s a disruption to previously scheduled work as both IT and business leaders convene to manage the DR. IT leaders need guidance on when to escalate to DR procedures.

Our Advice

Critical Insight

Incorporating DR scenarios into service management processes leads to better decisions about how to respond to less obvious DR scenarios, when to escalate those incidents, and whether to initiate recovery procedures rather than continue troubleshooting.

Both service management and DR procedures require a strong understanding of the relative importance of the various systems used by the business. Incident response and recovery timelines for a mission critical system need to be shorter than for a relatively unimportant system.

Impact and Result

Understand how service management processes can help you meet your Recovery Point Objectives (RPOs) and Recovery Time Objectives (RTOs).

Perform a business impact analysis to establish system criticality and recovery objectives.

Extend service management processes to account for disaster scenarios, and to reflect different levels of system criticality as identified by the business impact analysis.

Book an Appointment

IT Research & Advisory Services

Do not fill in this field

Full Name

Email

Company

Phone

Job Function

Job Title

IT Staff

Country

Yes. I would like to receive email updates from Info-Tech Research Group that include advice
and resources to help systematically improve my IT department.
You may unsubscribe at any time. By clicking the "Submit" button, you are agreeing to the Info-Tech Research Group Terms of Use and Privacy Policy.