I'm a strong believer of not complicating things if they don't have to be. But I do realize that you absolutely have to have some semblance of structure and preparedness in place if you're going to respond appropriately rather than react inappropriately. So, start by prioritizing your critical systems, documenting specifically what needs to be done, and then test your procedures to validate the process. And be sure to take all of these...
steps in your data backup plan before you actually need them, otherwise you might run into some trouble.
For more on data recovery, disaster recovery and data restoration:
- Read about the top ten reasons disaster recovery plans fail in this tip.
- Read about the top five data backup and recovery tips from 2009.
- And learn how to evaluate your disaster recovery plan's maturity level in this tip.
Dig deeper on Disaster Recovery Planning-Management
Related Q&A from Kevin Beaver
For an enterprise application, assuming our development team does lots of little changes (in two- to three-week iterations), how frequently should we...continue reading
Is the PCI DSS a sufficient guideline for implementing an application security program? Should organizations take steps beyond the mandated PCI ...continue reading
The number of endpoint security vulnerabilities is daunting, but endpoint admins should first focus on updating patches against Windows malware.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.