Planning for something unprecedented, to foresee the unforeseen is at best tough. Having said that, planning for something like the World Trade Center (WTC) attack must have been relatively less complex, because it did have a precedent. Though none could have foreseen the extent of the damage, the precedent did help in planning ahead and the state of readiness. When the WTC was bombed in 1993, disaster recovery was a fledgling concept with most businesses not yet ready to tackle any disruptions to their computer- and network-centric operations. However, when disaster struck the second time, most of them were ready, armed with some of the most professional backup and recovery plans. And, when the twin towers went down, these disaster recovery plans were already activated, ensuring smooth data flow.
A case in point is Verizon Communications, whose office adjacent to the WTC was extensively damaged by the attacks. The telco operates 2 million phone lines in lower Manhattan alone and fulfills 20 percent of Wall Street's communication needs. Remarkable efforts from the telecommunications company saw The New York Stock Exchange, which was closed for business for four days, resuming operations within the week. The exchange managed 15,000 voice and data backups within five days after the disaster and handled a record volume of 2.37 billion shares on the day it reopened. Verizon had reconstructed, constructed, or rerouted some 4 million voice and data circuits in Manhattan and parts of New York within the first week of the attacks and transmitted a record number of calls each day. The key to its resilience? Planning.
Planning is All
For IT professionals, disasters are an everyday reality. Disasters may come in all sizes and shapes-right from spilling coffee on your computer to a Trojan attack or one of the WTC kinds. Typically, disaster recovery plans are like your insurance-they are of little use until you actually need them one day. But, operating without one of these recovery plans in place could mean business failure, especially so when e-business is gaining widespread acceptance. Implementing a well thought-out disaster recovery plan could be time and resources consuming, but the impact of downtime and data loss could be worse-lost revenue, loss of customers, decline in share value, and poor profitability. And, if bound by contractual obligations or federal regulations, you may be required to deliver the goods no matter what.
Planning for disasters is complex, and requires the time of technical staff, funds, and whole-hearted support from the management. A typical disaster recovery plan would include the following:
A case in point is Verizon Communications, whose office adjacent to the WTC was extensively damaged by the attacks. The telco operates 2 million phone lines in lower Manhattan alone and fulfills 20 percent of Wall Street's communication needs. Remarkable efforts from the telecommunications company saw The New York Stock Exchange, which was closed for business for four days, resuming operations within the week. The exchange managed 15,000 voice and data backups within five days after the disaster and handled a record volume of 2.37 billion shares on the day it reopened. Verizon had reconstructed, constructed, or rerouted some 4 million voice and data circuits in Manhattan and parts of New York within the first week of the attacks and transmitted a record number of calls each day. The key to its resilience? Planning.
Planning is All
For IT professionals, disasters are an everyday reality. Disasters may come in all sizes and shapes-right from spilling coffee on your computer to a Trojan attack or one of the WTC kinds. Typically, disaster recovery plans are like your insurance-they are of little use until you actually need them one day. But, operating without one of these recovery plans in place could mean business failure, especially so when e-business is gaining widespread acceptance. Implementing a well thought-out disaster recovery plan could be time and resources consuming, but the impact of downtime and data loss could be worse-lost revenue, loss of customers, decline in share value, and poor profitability. And, if bound by contractual obligations or federal regulations, you may be required to deliver the goods no matter what.
Planning for disasters is complex, and requires the time of technical staff, funds, and whole-hearted support from the management. A typical disaster recovery plan would include the following:
- A thorough understanding of the kind of risks a business is likely to face and defining the scope of the project
- A study of the existing security systems and assessing their vulnerability
- Determining the enterprise's disaster threshold. For example, rate the risks on a factor of ten and determine the severity of impact, grading them from the least harmful to the most
- Step 3 will help in defining the requirements in terms of hardware, software, and remote support and facilities
- Identify the vendor, upgrade existing systems to ensure compatibility with the disaster recovery plan
- Test, test, and test. Try out a partial recovery. See if the system is in working order. This exercise will also help gauge the timeframe for getting the business up and running in case of a disaster
- Maintenance and frequent upgrades. The latter depends purely on business requirements
The Crack Team
Three names that continuously popped up in the media in the aftermath of the September 11 attacks were IBM, SunGard, and Comdisco. Their disaster recovery services range from providing office space to supplying computers to recreating data.
IBM's Business Continuity and Recovery Services Group achieved miraculous success in helping businesses affected by the attacks by providing backup locations. Most of its customers were back on their feet within 72 hours and critical telecommunication lines were restored as early as 48 hours. The company has already outlined major plans for Project eLiza, which will focus on developing self-managing systems that will reduce the cost and complexity of IT infrastructure. IBM promises that such systems will not just reduce the need for human intervention, but will also improve performance and efficiency dramatically as well as simplify user management.
There were 30 SunGard customers in the WTC and a hundred others located within a mile radius, all of which successfully recovered their data, and resumed their networking and backoffice functions. SunGard got its first SOS just eight minutes after the first plane hit the WTC. By September 14, it had configured 50 workstations with PCs and a WAN connection to an RS/6000 in its Philadelphia MegaCenter for the New York Shipping Association and put the harbor back in action. The company has now tied up with the GSA Federal Computer Acquisition Center (FEDCAC), a federal agency, to offer hot site services, mobile, workgroup and network recovery, electronic vaulting and recovery plan development, and testing services to agencies belonging to the U.S. Government.
After the attack, 47 companies with roughly 3,000 customers declared disasters with Comdisco, which meant their operations had to be shifted to remote locations. A majority of them were banks, insurance companies, investment banks, and brokerages, to whom downtime or data loss could prove nightmarish. The company, which was also supporting one of the exchanges in New York, had 13 of its 23 data recovery centers in the United States operating in full swing at one point of time. And, by the 25th of the month, 20 of its 47 customers had returned to their facilities.
The Cost Factor
Data recovery services range from simple system recovery (usually a tape backup) to complex hosting services (no data loss and a maximum downtime of two hours in case of a major disaster) with uptime guarantee and continuity services. The costs too vary accordingly, from a few thousands to close to a million dollars for continuity services wherein all the client data is mirrored in servers at a remote recovery center. Most stock exchanges as well as a majority of health service providers rely on this service to protect their data.
For companies that had just taken a perfunctory look at disaster recovery so far, the happenings of September 11 have changed everything. The redundancy built in by WTC has taught them a lesson in disaster recovery and planning for contingencies.
Three names that continuously popped up in the media in the aftermath of the September 11 attacks were IBM, SunGard, and Comdisco. Their disaster recovery services range from providing office space to supplying computers to recreating data.
IBM's Business Continuity and Recovery Services Group achieved miraculous success in helping businesses affected by the attacks by providing backup locations. Most of its customers were back on their feet within 72 hours and critical telecommunication lines were restored as early as 48 hours. The company has already outlined major plans for Project eLiza, which will focus on developing self-managing systems that will reduce the cost and complexity of IT infrastructure. IBM promises that such systems will not just reduce the need for human intervention, but will also improve performance and efficiency dramatically as well as simplify user management.
There were 30 SunGard customers in the WTC and a hundred others located within a mile radius, all of which successfully recovered their data, and resumed their networking and backoffice functions. SunGard got its first SOS just eight minutes after the first plane hit the WTC. By September 14, it had configured 50 workstations with PCs and a WAN connection to an RS/6000 in its Philadelphia MegaCenter for the New York Shipping Association and put the harbor back in action. The company has now tied up with the GSA Federal Computer Acquisition Center (FEDCAC), a federal agency, to offer hot site services, mobile, workgroup and network recovery, electronic vaulting and recovery plan development, and testing services to agencies belonging to the U.S. Government.
After the attack, 47 companies with roughly 3,000 customers declared disasters with Comdisco, which meant their operations had to be shifted to remote locations. A majority of them were banks, insurance companies, investment banks, and brokerages, to whom downtime or data loss could prove nightmarish. The company, which was also supporting one of the exchanges in New York, had 13 of its 23 data recovery centers in the United States operating in full swing at one point of time. And, by the 25th of the month, 20 of its 47 customers had returned to their facilities.
The Cost Factor
Data recovery services range from simple system recovery (usually a tape backup) to complex hosting services (no data loss and a maximum downtime of two hours in case of a major disaster) with uptime guarantee and continuity services. The costs too vary accordingly, from a few thousands to close to a million dollars for continuity services wherein all the client data is mirrored in servers at a remote recovery center. Most stock exchanges as well as a majority of health service providers rely on this service to protect their data.
For companies that had just taken a perfunctory look at disaster recovery so far, the happenings of September 11 have changed everything. The redundancy built in by WTC has taught them a lesson in disaster recovery and planning for contingencies.
