While business continuity procedures have been prevalent since the 1970s, most of the early focus was on protecting...
large data centers with dozens of mainframe system components.
For example, some large mainframes were water-cooled, which meant piping that supplied chilled water to the cabinets had to be protected in case of a disruption. We no longer have such worries, as most systems are now air-cooled. Technology has certainly evolved, going from acres of mainframe and minicomputer cabinets to racks of servers with more processing speed than a dozen cabinets with multiprocessors in a fraction of the floor space.
Interestingly, process cooling systems are relatively unchanged from the 1970s. They still occupy large cabinets on the perimeter of a data center, pushing chilled air into the room. Temperature and humidity are still concerns, just as they were in the 1970s.
Business continuity procedures morphed into an actual profession in the early 1980s. Regardless of who claims to have coined the term business continuity (BC), the mission was the same: Protect the organization and its business processes, employees, the technology used by the business processes and the facilities needed to house the business.
Business continuity procedures, such as gap analyses and risk assessments, have been around for a long time, whereas business impact analyses are more recent, first appearing in the early 1980s. The business of protecting and storing valuable business assets, such as data files and vital records, predates disaster recovery (DR) and is today one of the most important preventive measures an organization can implement to remain operational following a disaster.
BC and DR standards are the norm today; in the past, employees simply followed a logical set of procedures and activities in an emergency. About the only early standards were regulations from the Federal Reserve, Comptroller of the Currency, New York Stock Exchange and other financial regulators that required banks and other financial institutions to have documented methods for protecting data and recovering from a disruptive event.
The federal government introduced its first standards concerning business continuity procedures in the 1990s, creating the terms continuity of operations (COOP) and continuity of government. Today, all federal agencies must have COOP programs, and most states have similar requirements.
DR and business continuity procedures have become more structured and process-based, with standards to provide the structure; software products to facilitate the process; and cloud-based products to protect data, recover and relaunch critical applications and databases.
Dig Deeper on Disaster recovery planning - management
Related Q&A from Paul Kirvan
Definitions for business continuity and resilience sometimes clash, but both processes help an organization stay on its feet. A new ISO standard ... Continue Reading
Emergency response planning needs to be specific and varied enough that it will enable an organization to recover in the event of many different ... Continue Reading
Has your organization created a disaster recovery plan and left it on the shelf? You're not alone. Explore what you can do to improve your plan's ... Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.