IT Storm Watch: NOAA Predicts Near-Record Hurricane Season for 2010

Five years have passed since Hurricane Katrina and seven other named storms struck the Gulf Coast and Southeast in one of the most devastating hurricane seasons on record, but some areas of the Gulf Coast and adjoining states are still repairing the damage.  Now, the National Oceanic and Atmospheric Administration's (NOAA) Climate Prediction Center is warning of a 2010 hurricane season eerily similar to 2005.  Citing all-time high sea surface temperatures in key areas of the Atlantic Ocean, as well as the El Nino cycle, NOAA predicts that the 2010 season will most likely produce 14 to 23 named storms, eight to 14 hurricanes, and three to seven major hurricanes (category 3 or stronger).

Faced with these alarming predictions, and with about 85 percent of Federal civilian employees working outside of the Washington, D.C., area, including hurricane-belt locations (e.g., Texas, Louisiana, and Florida), many Federal government officials may be asking what they can do to keep their agency functioning during a major business disruption such as a hurricane.  A well-managed disaster preparedness plan can help prevent costly downtime and help maintain important citizen services.  Below are the top seven habits of highly resilient organizations that agencies can adopt to best prepare their IT systems for a hurricane or other major disruption*:

1. Assess your current plan.  Conduct a business impact assessment that prioritizes critical processes for the entire organization. For example, processes that need to resume within 24 hours to prevent serious mission impact, such as essential citizen services, could receive an "A" rating.
2. Take steps to protect data.  Agencies should back up data frequently to ensure that data integrity and applications are not jeopardized.  Agencies should also store multiple copies of data off site, at a remote location, a long distance from the primary data center.
3. Review power options.  Agencies should add uninterrupted power supplies (UPS) to keep the most essential applications running.  In addition, cooling systems should be supported by backup generators. Temperature spikes can cause unplanned interruptions when operations are most critical.  
4. Identify and appoint a cross-functional preparedness team.  Create a team to design and test the disaster recovery plan, as well as a recovery team, which will participate in recovery activities after any declared disaster.
5. Document, test and update. The disaster preparedness plan should include logistical details, including travel to backup sites, and even who has spending authority for emergency needs.  The plan should be tested in an environment that simulates an actual emergency.
6. Consider telecommunications alternatives.  Following Hurricane Katrina, many organizations lost access to reliable telecommunications equipment for days.  Alternative communications vehicles, including wireless phones and satellite phones, should be considered.
7. Form tight relationships with vendors.  Hardware, software, network and service vendors can help expedite recovery, can often ensure priority replacement of telecommunications equipment, personal computers, servers, and network hardware in the event of a disaster.

*Source:  CDW Government