DISASTER RECOVERY 
JOURNAL


P. O. Box 510110
St. Louis, MO 63151
(314) 894-0276 
Fax: (314) 894-7474
Internet
www.drj.com 
E-mail
drj@drj.com

PUBLISHER &
EDITOR-IN-CHIEF
Richard L. Arnold, CBCP
richard@drj.com

SENIOR EDITOR
Janette Ballman
janette@drj.com

MANAGING EDITOR
Jon Seals
jon@drj.com

ASSOCIATE EDITOR
Ed Pearce, CBCP
ed@drj.com

COPY EDITORS
Richard Sandhofer
richards@drj.com
Pamela Clifton
pamelaclifton@hotmail.com

ADVERTISING 
Robert Arnold
bob@drj.com

_____________

Corporate

President/CEO
Richard L. Arnold, CBCP
richard@drj.com

Vice President 
Robert Arnold
bob@drj.com

CONFERENCE COORDINATOR
Patti Fitzgerald, CBCP
patti@drj.com

CONFERENCE REGISTRAR
Merce Knese
mercedes@drj.com

CIRCULATION
Laura Baugh
laurab@drj.com

EXECUTIVE COUNCIL
Jeff Dato, MBCP, KPMG
John Jackson, IBM
Edward S. Devlin, E.S. Devlin & Associates
James Hammill, CBCP, JMH Consulting Inc.
Pat McAnally, SunGard Availability Services
Brian Turley, Strohl Systems
Belinda Wilson, Hewlett-Packard


INTERNATIONAL
CONTACTS
England: Thom Hetherington
Business Continuity 
Phone: 0161-237-1007
thomh@tempus.demon.co.uk

Australia: Anthony J. Harvey
Journal of Business Continuity
Phone: 0011-613-953-0055-8
fax: 0011-613-953-0528
sector@notability.com.au

Japan: Shinji Hosotsubo
Quake Japan Co., Ltd.
Phone: 03-3215-2880
fax: 03-3215-2881

Brazil: Jose Carlos Ferreira
Disaster Recovery Mercosul
Phone: 55 11 3666-9506
conc2000@uol.com.br
www.drms.com.br



 

Click Here for a Printable Version

DATA RECOVERY

You Can Never Go Home Again

By LARRY WISNIEWSKI

Ihave to admit that until recently, I was completely unfamiliar with the term “fail-back.” I’m still not sure if it’s even real computer lingo, but it did come up during a conversation with a client. He used it to refer to the process of resuming computer operations at the home office after a disaster recovery operation. His company was one of those affected by the blackout in the northeast. Rather than risk a prolonged outage, they decided to quickly initiate their disaster recovery plan, transferring all computer operations to their hot-site facility, not a trivial procedure.

The good news is that they were successful in restoring business operations from their remote location. There were some glitches, but for the most part, their recovery plan worked well. They were able to completely resume processing in less than 36 hours. The bad news is that their recovery planning didn’t give much thought to how operations would be brought back to the home office.

This processing disruption was relatively short in duration. Their equipment wasn’t harmed nor was their facility damaged. But when the lights went back on and they were ready to go back home, they realized that it wouldn’t be so easy. In fact, the process of returning was almost as difficult as the disaster recovery operation itself.
Transactions were processed for most of their critical applications for nearly two full days. Now files updated at this remote facility no longer matched those at the home office. To return, they were faced with either reprocessing all of these transactions or executing their disaster recovery plan in reverse; hence the term fail-back.

The situation might have been less painful if they had just given as much thought to returning from a disaster as they did planning for the disaster itself. My client is now working on his fail-back plan. His goal is to develop a way to identify, capture, and restore just the files that changed while processing at the hot site. Because only business critical applications were run at the remote facility, this solution could easily reduce the return effort to nothing more than restoring a few files.

It might be worth the time to prepare your own fail-back plan so you can go home again.



Larry Wisniewski is vice president of marketing for 21st Century Software, Inc. The company provides intelligent, enterprise-wide data protection and recovery solutions to the Global 1000 marketplace. Wisniewski can be reached at 21st Century Software, (800) 555-6845.

©Copyright 2004 Systems Support Inc. All rights reserved. Reproduction in whole or in part in any form or medium without the express written permission of System Support Inc. is prohibited.