What stands between your data and disaster? You do.
IT disasters cost US businesses $1.2 trillion every year. Worldwide, the total is $6.2 trillion. And more of that comes from so-called ‘silent disasters’ software bugs or malware and hardware failures than you’d think. Everyone thinks about preparing for floods or hurricanes, because they’re high-profile and high-impact. Fact is, they’re also low-probability.
And with leaking, hacking and security risks riding front-of-mind for so many, it’s easy to forget that many of the the disasters that put your whole company IT system up on blocks are just that - accidents. It really doesn’t matter, after all, where they come from. What matters is how you respond to them.
1: Plan For Disaster
Anticipate likely problems before they arise. No, you can’t get ready for everything - but you can build data loss templates that reflect the most likely threats you face. Map out two to four of the most likely scenarios and base your preparations on those. Look at the data losses you’ve suffered in the past, or those that affected other enterprises in your business vertical and geographic location, and build on that knowledge to prepare.
2: Make Sure You Have the Right Tools
Ensure that the processes and technology to deal with the treats you’ve identified are in place. Have backup and recovery, snapshot and replication capacity ready for when it;'s needed. A good disaster recovery plan will need all these in place to cover any eventuality. Augment their efficacy and prevent overuse by building in a monitoring tool that’s sensitive and accurate, with a low number of false positives.
3: Test It!
Just like a fire alarm system is only as good as the last fire drill, so a data recovery plan, too, is only as good as its last test. When was the last time you tested yours? If the last time you tested your data recovery plan, the solution involved switching out a blown valve, you need to step up testing. Otherwise you just think you’re ready - when you need your data recovery plan the most, it might let you down.
With a resiliency plan in place, you’ll be equipped to hit the ground running if disaster does strike, as well as being more likely to catch internal problems like ailing hardware or buggy programs in the bud, before they can trigger a disaster.