By submitting your personal information, you agree to receive emails regarding relevant products and special offers from TechTarget and its partners. You also agree that your personal information may be transferred and processed in the United States, and that you have read and agree to the Terms of Use and the Privacy Policy.

To control costs, companies may conduct several smaller component tests during the year and a full annual test. Others extend the testing cycle across several years. "As part of our business-continuity plan, we are obligated to test each business application at least once every three years," reports Dan Traynor, director of IT infrastructure services at Southern Company, an energy firm in Atlanta.

Is once every three years enough?

This feature from Storage magazine outlines some DR testing challenges. The following action points should be first and foremost on the minds of channel professionals helping customers address DR planning and testing:

Exercise the DR plan to reveal shortcomings and weaknesses. It's not a pass/fail process.

Review and adjust DR plans to reflect changes in the enterprise. DR plans are not static.

Document every recovery step. Seemingly minuscule details can bring the recovery effort to a standstill.

Make sure people in your customer's organization understand their roles in the DR process.

Designate a DR coordinator and an established chain of command. The ability to make fast decisions during a disaster is crucial for a rapid and successful recovery.

E-Handbook

E-Handbook

E-Handbook

0 comments

E-Mail

Username / Password

Password

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy