{"id":3936,"date":"2014-08-27T15:00:22","date_gmt":"2014-08-27T15:00:22","guid":{"rendered":"http:\/\/www.backupassist.com\/blog\/?p=3936"},"modified":"2019-11-07T07:33:51","modified_gmt":"2019-11-07T07:33:51","slug":"dr-strategy-zombie-proof","status":"publish","type":"post","link":"https:\/\/www.backupassist.com\/blog\/dr-strategy-zombie-proof","title":{"rendered":"Is your DR strategy ZOMBIE PROOF?"},"content":{"rendered":"

\"Is<\/a><\/p>\n

So, you\u2019ve survived the zombie apocalypse with your brains intact.  But can you say the same for your systems and data?  In the aftermath of an undead disaster, imagine the advantage your business could leverage by being up and running while your competitors are still clutching shotguns in their basements.  It\u2019s doable.   But you\u2019ll need a darned good disaster recovery strategy<\/a>.If movies have taught us anything, it\u2019s that a zombie uprising is the ultimate disaster.  So if your disaster recovery (DR) strategy can stand up to the flesh-eating dead, a measly hurricane or trivial earthquake should be no trouble at all.<\/p>\n

In this article, we\u2019ll look at how to zombie proof your DR strategy so you can be the first company servicing the post-apocalyptic wastelands.  As for surviving the zombies, you\u2019re on your own \u2013 we\u2019d recommend the CDC\u2019s zombie survival guide<\/a> and this vehicle<\/a> as good places to start.<\/p>\n

Have your servers survived the military?<\/h2>\n

\"DR<\/p>\n

Shuffling corpses probably aren\u2019t going to be interested in your servers. There\u2019s not nearly enough tasty gore involved. Rather, what you\u2019ll need to watch out for is those well-intentioned military types.  We all know how these events go down:<\/p>\n

    \n
  1. Outbreak begins<\/li>\n
  2. Government urges calm<\/li>\n
  3. Everybody panics<\/li>\n
  4. Zombies everywhere<\/li>\n
  5. Government sends in military<\/li>\n
  6. Military overrun<\/li>\n
  7. Whole city napalmed in last-ditch effort<\/li>\n
  8. Zombies unharmed \u2013 your servers obliterated<\/li>\n<\/ol>\n

    Now there\u2019s a cure, civilization\u2019s rebuilding and you\u2019ve got no systems and data to capitalize with! Well, here\u2019s where your DR strategy kicks in.<\/p>\n

    Let\u2019s say you\u2019ve managed to salvage a brand new server from that Dell warehouse that was miraculously untouched. You\u2019ve got your generator fired up and you\u2019re ready to go, but do you have bare-metal recovery capabilities?<\/p>\n

    The ability to restore to bare-metal is a cornerstone of any good DR strategy.  Using BackupAssist\u2019s recovery wizard<\/a>, you\u2019ll be able to perform bare-metal recoveries to same or dissimilar hardware.  Take that, destruction of humanity!<\/p>\n

    Of course, you\u2019ll need your offsite backups intact\u2026<\/p>\n

    Are the undead between you and your offsite backups?<\/h2>\n

    \"DR<\/p>\n

    Having offsite backups is a crucial part of any good DR strategy.  What\u2019s just as important, however, is being able to access these backups when you need them.  It\u2019s no good having your HDDs rotated to a safe in your other office across town if there are 50,000 angry corpses shuffling around between you and your data when it comes time to recover.<\/p>\n

    Your DR strategy should always include a plan for how you\u2019re going to get your offsite backups back onsite in the event of a disaster.  Whether it\u2019s zombies or floods, chances are the roads are going to be blocked, so that’s something you\u2019ll need to take into consideration when plotting out an appropriate RTO (recovery time objective).  There are a lot of considerations that should be taken into account for recovering data in any decent DR planning.<\/p>\n

    Similarly, if you\u2019re relying on the Cloud<\/a> as your DR strategy, what will you do if internet services are down?  Because chances are all the people at your ISP are going to be gnawing on each other\u2019s faces by now\u2026<\/p>\n

    Is your Sys Admin hungry for brains?<\/h2>\n

    \"DR<\/p>\n

    Who\u2019s going to be responsible for implementing your DR strategy? Greg, the Sys Admin, right? Well, unfortunately Greg\u2019s a little busy right now \u2013 he\u2019s disemboweling Terry from HR while the finance team shuffles their way over to join in.<\/p>\n

    Your DR plan should never rest on the shoulders of a single individual.  Because whether that person isn\u2019t present due to the disaster itself or simply because she happens to be taking annual leave sipping cocktails in the Bahamas that week, your RTO is going to be blown out of the water.<\/p>\n

    Have more than one person trained up on how to implement the DR for when the brains hit the fan.<\/p>\n

    Most importantly – Are you sure it\u2019s all going to work?<\/h2>\n

    \"DR<\/p>\n

    You\u2019ve got your salvaged server and your generator humming.  You\u2019ve made it through the groaning masses and back alive with your offsite HDD in hand.  You\u2019ve barricaded the server room and cleared the straggling undead.  You have your documentation in hand explaining how to perform the recovery.  Now you just need to recover your server before the horde breaks in and repaints the room with you.<\/p>\n

    The only problem? You\u2019ve never tested the backups.<\/p>\n

    Perhaps the most important aspect of any solid DR strategy is performing regular test restores and recoveries.  It\u2019s how you make sure that everything else in your plan isn\u2019t a giant waste of time and resources.<\/p>\n

    At the end of the day, if your backups have all failed or won\u2019t recover due to a missing driver at that critical moment, you may as well just season yourself and ring the dinner bell.<\/p>\n

    Further reading on planning a DR strategy, minus the zombies<\/h2>\n

    Okay, we\u2019ve had our fun.  Now it\u2019s time to start getting serious about planning your DR strategy.  Here are some great (and zombieless) articles that will set you off on the right path to secure systems and data.<\/p>\n