02
Sat, Nov
2 New Articles

From the Editor: Anatomy of a Disaster: Four Lessons of Contingency

Commentary
Typography
  • Smaller Small Medium Big Bigger
  • Default Helvetica Segoe Georgia Times

This year, we’re all especially concerned about the potential for catastrophe as we approach the dreaded Year 2000. Unfortunately, the hype surrounding the potential of a Y2K meltdown has been so emphasized by the press that many of us are not yet addressing the greater threats facing our information systems. After all, what is Y2K but a known, impending event that will test everyone’s contingency plans simultaneously? No, the real threat is not Y2K but rather the rapid addition of new software and hardware packages into our organizations. These packages are arriving so quickly and being so swiftly implemented and accepted by our users that we in IS can hardly measure their strategic importance to the organization. Take Lotus Domino and email for instance: We implement the applications and turn users loose with them. They seem happily preoccupied building large Notes and email databases, blithely assuming that we will rescue them if they run into a problem. Little do these users realize that, in the crunch of a catastrophe, they might actually know more about these applications than we do.

This scenario reminds me of the four lessons that every IS manager learns about contingency planning. The first lesson is that, as a practical matter, no one in your management will take contingency planning seriously until after the organization has actually experienced a catastrophe. No matter how long or how loud you gripe about the need to prepare for a disruption, management will always delay the resources until it’s too late. Some critical file must be lost, some important database must become corrupted, some crucial piece of hardware must crash, or some vital service must be disrupted before management will actually feel the pain. Of course, once the pain has been experienced and the price paid, you can rest assured that you’ll have everyone’s attention. Suddenly, everyone will want information systems that are secured, backed up, and archived in gold- lined vaults.

The second lesson that every IS manager learns is how to capitalize upon that catastrophe in order to actually institute some real contingency planning. This doesn’t mean just having an adequate daily archive or implementing AS/400 journaling on key databases, but really setting up a chain of command and disaster scenarios and then testing them on a regular basis.

The first two lessons are the easiest to learn because they are predictable: Accidents will happen (lesson 1), and management will spend money and resources to prevent them from happening again (lesson 2). However, it’s the third lesson of contingency planning that is by far the most difficult: The hardest part of implementing any plan is the communication of the plan itself. In my experience, it was never the contingency plan (if, in fact, one existed) that failed in a disaster. It was the inability of IS to communicate that plan that brought the work environment to its knees. Always, some key piece of knowledge was missing because some key individual was absent. It might have been a server password, a configuration parameter, or even the knowledge of where the manual for contingency resided. Still, hardware can be replaced quickly, software can always be reconfigured, and data can be rekeyed. It’s what you don’t know that hurts, and ignorance is a hole that takes time to fill during a catastrophe. Since time is the enemy in a business of deadlines and dollars, ready access to information about what to do in an emergency is crucial to rapid recovery.

Unfortunately, most IS organizations exist in a “need-to-know” sort of haze. Resources these days are so scarce that there is hardly time enough to get the job done the first time, much less time to tell anyone else how it was accomplished. When a disaster strikes, the fastest route to recovery is always to go to the person who originally installed or configured or worked on the system. However, this is the fourth—and cruelest—lesson that contingency planning teaches: The person who knows the most about a system will always become your weakest link. Why? Because, unless you are careful, that person will soon become the only person who can help in a disaster. That’s why, whenever a serious problem occurs, I always stress that the resolution of that problem must be handled within a team structure. The expert can lead the team, even if it is a small team of two, but he cannot solve the problem alone. Even if the other member of this team is from another department, you are better off with two people than with one. This emergency team structure can cross-train the staff and strengthen the organization as a whole. This approach may be less efficient in the short run, but almost always pays dividends the next time a problem occurs.

All of these lessons go against the grain of common sense, but you should start considering them now—today—before the great Y2K event. Ultimately, I think you’ll agree that the best contingency plan is one that recognizes that every day is a catastrophe in the making—that is, preparing you for the ultimate test. In this light, the Year 2000 may be seen merely as the final exam at the end of a series of daily quizzes.

Thomas Stockwell

Thomas M. Stockwell is an independent IT analyst and writer. He is the former Editor in Chief of MC Press Online and Midrange Computing magazine and has over 20 years of experience as a programmer, systems engineer, IT director, industry analyst, author, speaker, consultant, and editor.  

 

Tom works from his home in the Napa Valley in California. He can be reached at ITincendiary.com.

 

 

BLOG COMMENTS POWERED BY DISQUS

LATEST COMMENTS

Support MC Press Online

$

Book Reviews

Resource Center

  • SB Profound WC 5536 Have you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application. You can find Part 1 here. In Part 2 of our free Node.js Webinar Series, Brian May teaches you the different tooling options available for writing code, debugging, and using Git for version control. Brian will briefly discuss the different tools available, and demonstrate his preferred setup for Node development on IBM i or any platform. Attend this webinar to learn:

  • SB Profound WP 5539More than ever, there is a demand for IT to deliver innovation. Your IBM i has been an essential part of your business operations for years. However, your organization may struggle to maintain the current system and implement new projects. The thousands of customers we've worked with and surveyed state that expectations regarding the digital footprint and vision of the company are not aligned with the current IT environment.

  • SB HelpSystems ROBOT Generic IBM announced the E1080 servers using the latest Power10 processor in September 2021. The most powerful processor from IBM to date, Power10 is designed to handle the demands of doing business in today’s high-tech atmosphere, including running cloud applications, supporting big data, and managing AI workloads. But what does Power10 mean for your data center? In this recorded webinar, IBMers Dan Sundt and Dylan Boday join IBM Power Champion Tom Huntington for a discussion on why Power10 technology is the right strategic investment if you run IBM i, AIX, or Linux. In this action-packed hour, Tom will share trends from the IBM i and AIX user communities while Dan and Dylan dive into the tech specs for key hardware, including:

  • Magic MarkTRY the one package that solves all your document design and printing challenges on all your platforms. Produce bar code labels, electronic forms, ad hoc reports, and RFID tags – without programming! MarkMagic is the only document design and print solution that combines report writing, WYSIWYG label and forms design, and conditional printing in one integrated product. Make sure your data survives when catastrophe hits. Request your trial now!  Request Now.

  • SB HelpSystems ROBOT GenericForms of ransomware has been around for over 30 years, and with more and more organizations suffering attacks each year, it continues to endure. What has made ransomware such a durable threat and what is the best way to combat it? In order to prevent ransomware, organizations must first understand how it works.

  • SB HelpSystems ROBOT GenericIT security is a top priority for businesses around the world, but most IBM i pros don’t know where to begin—and most cybersecurity experts don’t know IBM i. In this session, Robin Tatam explores the business impact of lax IBM i security, the top vulnerabilities putting IBM i at risk, and the steps you can take to protect your organization. If you’re looking to avoid unexpected downtime or corrupted data, you don’t want to miss this session.

  • SB HelpSystems ROBOT GenericCan you trust all of your users all of the time? A typical end user receives 16 malicious emails each month, but only 17 percent of these phishing campaigns are reported to IT. Once an attack is underway, most organizations won’t discover the breach until six months later. A staggering amount of damage can occur in that time. Despite these risks, 93 percent of organizations are leaving their IBM i systems vulnerable to cybercrime. In this on-demand webinar, IBM i security experts Robin Tatam and Sandi Moore will reveal:

  • FORTRA Disaster protection is vital to every business. Yet, it often consists of patched together procedures that are prone to error. From automatic backups to data encryption to media management, Robot automates the routine (yet often complex) tasks of iSeries backup and recovery, saving you time and money and making the process safer and more reliable. Automate your backups with the Robot Backup and Recovery Solution. Key features include:

  • FORTRAManaging messages on your IBM i can be more than a full-time job if you have to do it manually. Messages need a response and resources must be monitored—often over multiple systems and across platforms. How can you be sure you won’t miss important system events? Automate your message center with the Robot Message Management Solution. Key features include:

  • FORTRAThe thought of printing, distributing, and storing iSeries reports manually may reduce you to tears. Paper and labor costs associated with report generation can spiral out of control. Mountains of paper threaten to swamp your files. Robot automates report bursting, distribution, bundling, and archiving, and offers secure, selective online report viewing. Manage your reports with the Robot Report Management Solution. Key features include:

  • FORTRAFor over 30 years, Robot has been a leader in systems management for IBM i. With batch job creation and scheduling at its core, the Robot Job Scheduling Solution reduces the opportunity for human error and helps you maintain service levels, automating even the biggest, most complex runbooks. Manage your job schedule with the Robot Job Scheduling Solution. Key features include:

  • LANSA Business users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.

  • LANSAWhen it comes to creating your business applications, there are hundreds of coding platforms and programming languages to choose from. These options range from very complex traditional programming languages to Low-Code platforms where sometimes no traditional coding experience is needed. Download our whitepaper, The Power of Writing Code in a Low-Code Solution, and:

  • LANSASupply Chain is becoming increasingly complex and unpredictable. From raw materials for manufacturing to food supply chains, the journey from source to production to delivery to consumers is marred with inefficiencies, manual processes, shortages, recalls, counterfeits, and scandals. In this webinar, we discuss how:

  • The MC Resource Centers bring you the widest selection of white papers, trial software, and on-demand webcasts for you to choose from. >> Review the list of White Papers, Trial Software or On-Demand Webcast at the MC Press Resource Center. >> Add the items to yru Cart and complet he checkout process and submit

  • Profound Logic Have you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application.

  • SB Profound WC 5536Join us for this hour-long webcast that will explore:

  • Fortra IT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators with intimate knowledge of the operating system and the applications that run on it is small. This begs the question: How will you manage the platform that supports such a big part of your business? This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn: