Advertisement
Promo

Network management Toolkit

Recovery after the first 24 hours of a disaster

Mike Talon

Published: 24 Jun 2005 12:05 BST

  • Email
  • Trackback
  • Clip Link
  • Print friendly
  • Post Comment

After dealing with the immediate impact of a disaster, you must start the process of moving forward. This usually begins about a day after the emergency occurs, but it could be much later in the case of major disasters.

During this pivotal time, you face two major, and simultaneous, projects. First, you must continue your efforts to restore services to your end users. Second, you must begin planning how to bring operations back to normal.

The continuation of service is your primary concern. After you've completed emergency restoration operations, you'll typically need to bring several more systems back online.

These are usually the company's semi-critical systems -- important to continued business, but not so critical that they need to be back up immediately. Common examples include file servers used for archival purposes and secondary databases used for reporting and other purposes.

Even if these systems can afford to be offline for a few days, you must get these servers up and running eventually, and therefore you need to plan your next steps.

Organisations generally don't protect these servers with real-time replication and failover systems, since the recovery point objectives (RPO) for these servers typically allow for the loss of a day's worth of data or more. So if you don't already have standby systems in place, you must first obtain the necessary hardware and software to restore the servers.

After restoring the platforms, find the latest backup tapes available (again assuming that you're not using some other form of data protection), and restore the data to the new servers, making adjustments as necessary along the way to deal with configuration issues.

In addition, you need to start restoring data protection services for the data generated in the DR systems. Therefore, in the (hopefully) unlikely event of a problem at the DR data centre, you won't lose newly created data while you're in a failover state.

Meanwhile, you should begin to determine if and when you can return to your production facilities and data systems -- depending on the depth of the outages. You need to find ways to bring the old and new data back to the original systems, and you should make preparations for getting your end users back to their normal lives.

At this early stage, keep in mind that it may very well be impossible to begin restoration efforts, but you must still begin preparing for that time. While you may not be able to act at this juncture, you must begin to plan now so you can successfully complete restoration at the nearest available time.

  • Email
  • Trackback
  • Clip Link
  • Print friendly
  • Post Comment

Did you find this article useful?
58 out of 159 people found this useful


Full Talkback thread

0 comments


Company/Topic Alerts

Create a new alert from the list below:





Video icon

Video

On The Road Blog

O2 to carry Samsung's i7500 Android ph...

Samsung's first Android handset, the i7500, has appeared in O2's in-house magazine, and a spokesperson for the operator confirmed to ZDNet UK on Monday that the handset will be carried... More

Post a comment

Nokia Android rumours earn outright de...

Nokia has strongly denied working on an Android-based handset, following a report early on Monday that it was planning to do so. The report, carried in The Guardian, took a cue from... More

Post a comment

Behind the Scenes: Next Gen Mobile Tec...

Behind the Scenes: Next Gen Mobile Technology Author: Eric Everson, Founder MyMobiSafe.com With infrastructure speeds continually improving at the network level of the world’s leading... More

Post a comment


Skip Sub Navigation Links to CNET Brand Links

Help

Become part of the ZDNet community.

Newsletters