Flowing directly out of contingency policies, the contingency plan details the roles and responsibilities of departments and individuals in keeping technology systems available, as well as the procedures for restoring IT systems during an emergency. Other key elements of contingency planning include resource requirements, training needs, the frequency of training exercises and testing, maintenance schedules, and data-backup schedules.

The phases of a contingency plan include the initial notification and activation when the emergency strikes, restoration and recovery once emergency teams have been mobilized, and finally a return to normal operation - or available to help organizations develop and maintain accurate inventories of IT resources. Vendors offer modules that use software agents to scour the IT infrastructure, storing details about hardware and software assets and their configuration parameters in configuration management databases.

• Ensure that your recovery plan is not attached to any one person.
• Keep your plan portable, and keep it away from you
• Make arrangements in advance with software vendors for license keys to put backup software at the disaster recovery site in operation.
• Contact phone lists should also include vendors.
• Remember the little things, like mice -- companies that develop disaster recovery sites may have all the servers they need, but they sometimes overlook essential hardware peripherals.

Consider this, almost 40% of small businesses that close due to a disaster event never re-open. What would you do if the building your business is located within was damaged or destroyed in a disaster? Where would you go to continue providing your customers with your business services? Would you be prepared and have the correct resources, databases, contact information and other necessary items to adapt to these changes? Having a disaster plan that identifies these important items will help ensure your business is prepared to survive during unexpected and difficult times!

As historic floodwaters start to recede along the Mississippi and other Midwestern rivers, local businesses in affected communities like Cedar Falls, Iowa, are busy assessing the impact on IT equipment and whether disaster recovery plans stood the test.

A maker of computer games in Cedar Falls, may be permanently displaced after Cedar River floodwaters reached 6 feet in its administrative offices and 5.5 feet in an adjoining warehouse. The company sustained about $250,000 in damage to inventory.

The firm's president said all 65 employees are now working temporarily in borrowed offices in three facilities.

As the floodwaters approached on June 9, employees scurried to save 120 PCs, 80 monitors and eight servers. Three high-end printers could not be removed in time.

The company plans to revise his disaster recovery plan. "When a river comes up 6 feet higher than it ever has before, it's tough to have that foresight," they said. "But it is probably going to happen again."

A software development company has plans to deal with tornados and electrical outages, but executives never dreamed they would have to contend with the Cedar River surpassing 500-year-flood levels. "Going through this experience [will] make those plans [more] than just part of an IT checklist," he said.

A key lesson learned was that companies must prepare for employees to miss work to help families and communities after natural disasters.

(Computerword) - The Planet.com Internet Services Inc. hopes to have all 9,000 of its servers in its Houston data center back online later tonight following a blast that shut down the facility on Saturday afternoon.

When firefighters arrived at around 5 p.m., they could see "light smoke" at the Planet data center -- the aftermath of an explosion in a network gear room that produced enough force to move walls. Sprinklers quickly doused whatever flames erupted; the fire was attributed to an electrical problem with a transformer, according to a Houston Fire Department spokeswoman. There were no injuries.

Although the data center says it has power systems that "are designed to run uninterrupted" and a "fully redundant network operations center" with diesel generators, the electrical problem exposed an apparent Achilles' heel in its business continuity planning. Firefighters told data center workers to turn off all the power, according Planet spokeswoman Yvonne Donaldson. That meant the servers, even though they weren't damaged, were offline.

Approximately 6,000 of the affected servers were returned to service early this morning. Another 3,000 were due to return online by tonight, the company said. The Planet staff provided updates on the restoration on its customer forum site, including a message from CEO and Chairman Douglas Erwin, who wrote that some servers will be relying on generator power for a week until normal utility connections are restored.

The Planet operates more than 40,000 servers at multiple data centers and hosts more than 3 million Web sites.

While Planet data center staff worked to restore service, users -- many of them small business owners -- wrote of their frustrations over the outage on forum posts. Questions about the data center's backup capabilities were raised, as well. One person, flynnibus, wrote: "You shouldn't put all your money into one bank -- and you shouldn't put all your servers in one DC [data center] if you want to be truly resilient."

The NOTAM (notice to airmen) system provides notices to airmen, or pilots, regarding airports, equipment and security issues. The system went down late May 22 and was back up at around 7 p.m. on May 23.

Because of the disk failure, information had to be delivered to pilots through local air traffic controllers and alternate systems, including a Web site set up to disseminate the most up-to-date information, said a manager of aeronautical information management for the FAA. However, flight safety was never a problem, the FAA said.

"What happened was the drive in an end-of-life Sun box failed in the middle of updating the information on the hard drive, so it screwed up the database," the FAA said.

That was the beginning of the complications. The FAA team replaced the hardware and the drive which got the system running again.

The FAA already had the equipment to replace in place, they just had not done it yet, and that is why the hardware recovery was quite simple according to the FAA.

But even then, the system was running slowly, or in a deteriorated mode, and it got so bad that his team decided to reopen the problem to see what was going on.

As the technicians were working to fix the database, they decided to go to the backup system. As they did that, they soon realized they had written the error over to the backup system and had corrupted that system as well.

But what good does it do for IT to restore applications and data if there is no one there to run things? It is only half the solution, albeit the first half. The second half is the contact information for the business continuity piece. Recovering from disaster is less a solution than a process. Governments must take control of their own destinies. In the event of a disaster, a core team of people across all departments is typically designated to continue business operations pending the restoration of a normal work environment. These people need accurate information with which to call on IT and on vendors for technical support or to report to work at a temporary site.

A common area of confusion in dealing with replication is the distinction between consistency and synchronicity. Many newcomers to replication tend to focus on synchronization issues when, from a recovery perspective, consistency may be the true requirement from an application perspective.

So what is the difference and why is it important? Synchronization implies complete and continuous fidelity between local and replicated data stores. With true synchronous replication, a write operation is not acknowledged until it has been written to the local storage system and replicated to the remote storage system. This certainly provides a very high degree of consistency, but it also carries with it high costs and significant limitations regarding distance and latency that can impact application performance.

Synchronous replication is found primarily in the domain of the top tier of enterprise storage offerings and is usually reserved for those applications that are characterized by very high transaction rates where the recovery and re-execution of lost transactions would be difficult and costly.

The majority of replication is therefore of the asynchronous variety -- meaning that there is some degree of variance, based on change rate and available bandwidth, between the local and the replicated targets. In other words, by definition, the source and target are inconsistent with one another.

However, consistency still plays a critical role in the recoverability of asynchronously replicated data. The key is in understanding the interdependencies among related data components of a particular business function and ensuring that they are consistent among themselves at any given point in time at the target location. They may lag behind the original, but as long as they are equally behind, the function or application should be recoverable.

Although the notion of consistency groups is well established among enterprise-class storage systems, it may be less so for other forms of replication. Understanding consistency requirements and the ability of replication technologies to meet them should be a high priority consideration in disaster recovery design.

Add to that the processes necessary to support a Business Continuity and Disaster Recovery Plan and enterprises have an ever increasing complex problem.

Data recovery specialists at Kroll Ontrack Inc. painstakingly retrieved 99% of the information stored on the charred 400MB Seagate hard drive's 2.5-in. platters over a two day period after the device was discovered six months after the 2003 shuttle crash. The device was found in a dried up lake bed along the shuttle's debris area.

The successful retrieval of the data was disclosed in the April, 2008, issue of the Physical Review E journal, which published data from tests performed by the shuttle astronauts on the critical viscosity of xenon gas, according to published reports. The results of the tests were stored on the disk and retrieved by Kroll.

The Columbia disintegrated upon re-entry into the atmosphere of Earth on Feb. 1, 2003, killing all seven crew members and scattering debris across Texas and Louisiana.

Designed as a consumer service, Mac Mozy leverages Apples innovative Spotlight Search technology, allowing users to easily select the types of files they want to back up. The service installs quickly and runs quietly in the background. Backup speeds vary from user to user, largely determined by the upload speed of the consumers internet connection.

Mac Mozy offers an added measure of privacy by allowing its users to choose between a Mozy encryption key and a private encryption key. Incremental backups and block level differentials are included, which means subsequent backups complete at a much faster rate than the initial backup. Mozys servers also retain the most recent version of a file as well as 30 days worth of previously modified file versions. Customers may retrieve files or versions of the files via the internet or by requesting a DVD restore with next-day delivery.

The vice president of communications at the university said a vehicle used by Archive America Ltd. to transport the patient data was broken into in downtown Coral Gables, Fla. Thieves removed a transport case carrying the schools computer backup tapes.

For reasons the VP could not explain, Archive America waited 48 hours before finally notifying the university about the break-in and theft. Officials from the transport firm could not be reached.

The university posted an alert about the incident a full month after the backup tapes were stolen. In a statement, the senior vice president for medical affairs and dean of the University of Miami Miller School of Medicine, said, Even though they were confident that the patients data was safe, we felt that it was in the best interest of the physician-patient relationship that the incident should be transparent.

Since the incident, the senior VP said that the university temporarily stopped transporting backup data off-site. At this point, the University is not transporting anything until they conduct their own internal evaluation of the incident and see if there is anything that could have been done differently or better.

Data at rest is growing much faster than network throughput. That makes it difficult to get backups completed on time and on budget – not to mention trying to recover from an IT emergency.

The first is to accomplish backups in a timely yet accurate manner. Given organic data growth, and that each logical data object has between four and eight copies somewhere in the network, even differential backups can be tough to fit into assigned windows. Synchronous or live-to-live data models are even more bandwidth intensive and latency intolerant.

The second challenge is minimizing downtime. In the event of a failure or disaster, how quickly can backed-up data be restored? Considering a differential backup can take 8 hours or more to complete, and only represents 10-20 percent of the total data set, a full restore can be daunting. According to Ziff Davis Research, the average organization has 94TB of managed storage, and getting that data across the network only begins after the systems have been physically restored.

Rather than add more bandwidth, or invest in expensive, dedicated storage networks, WAN optimization can improve IP network performance sufficient to turn recovery into continuity. To help meet the objectives outlined above, a WAN optimization solution must be able to do three separate tasks for true business continuity: restrict bandwidth to backup applications during the allowed window and allocate it to critical applications in the event of a disaster, overcome latency and bandwidth limitations on the wire, and provide acceleration to roaming or displaced users redirected to alternative data sources.

• An objective to get back to a fully functioning data center and business
• Know what data is necessary and what is nice to have
• Validate that you have the data you will need
• Assume that anything critical will fail
• Focus on quick solutions that will minimize outages
• Have sufficient resources available before you start
• Encrypt data but know how to get at it in an emergency
• Focus on Recovery Time Objective (RTO) with a Recovery Point Ojectivie (RPO)

• Team members feeling close to tears much of the time
• Team members finding it hard to concentrate and make decisions
• Team members being short tempered with people at home and at work
• Team members feeling tired most of the time and or sleeping badly
• Team members feeling stretched beyond their limits at the end of the day
• Team members drinking and smoking more to help them get through the day
• Team members feeling that they just can not cope
• Team members eating when they are not hungry
• Team members feeling that they have achieved nothing at the end of the day