Disaster Recovery - Just Tick The Box And Move On?
Symantec recently carried out a survey on DR habits and discovered that, on the whole, DR is possibly not as successful as it should be. Seems a bit weird when the same organisations surveyed said that DR has an impact on customers, sales, and revenue. Nearly one-third of organisations reported that DR will impact their customers, while over one-fifth admitted this could also impact their sales and revenue. Hmm, I smell a rat!
OK, it’s pretty simple for me to talk about, but implementing a DR strategy can be difficult. You don’t want to impact the end user or production systems, you also don’t want to make a mess of your infrastructure in the process of putting in the very system that is supposed to save your bacon. As a result approximately half of the organisations surveyed test their DR plans either only once a year or less.
Bottom line: Organisations are not testing frequently enough to improve their plans and are not using adequate tools to reduce the overall business impact.
Ah, well, in that case that’s easy to overcome … unless you have a virtual environment, of course? The Symantec survey reports that only 37% of respondents reported that they back up all of their virtual systems. Currently, native DR tools in virtual environments are immature and don’t provide the top level protection that organisations really need today. While having a DR plan is essential in most organisations, knowing that DR plans work is just as important.
One of the reasons that DR plans fail is because they do have a tendency to become shelf-ware and this is mainly because implementing DR plans is pretty tricky. Well, here’s where you can save yourself some heartache.
Backup Exec System Recovery provides organisations with extended system protection with Scheduled Automated Virtual Conversion - NEW to 8.5 .. what this does is builds on the off-site copy capability. If you have a BESR server at your DR site that can see the duplicated images (FTP’s from the main site) a schedule can be set to convert the images from v2i to either vmdk or vhd formats. Once this process is complete the resulting virtual file can be mounted on a VMware ESX or Microsoft Hyper-V server ready to be booted should disaster occur at the main site - good, hey?