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
Different tools protect different assets at the network and application layers. But both network and application security need to support the larger ... Continue Reading
The WannaCry TCP port 445 exploit returned the spotlight to Microsoft's long-abused networking port. Network security expert Kevin Beaver explains ... Continue Reading
While most mobile platforms provide levels of security from mobile cryptojacking, IT must still be aware of the risks and procedures to address an ... 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.