In my last article, Priorities of Uninterrupted Data Access, I discussed the IDG survey that reported a sizeable difference in the percentage of executives (50%) and IT managers and directors (90%) who are concerned about uninterrupted access to company data. This spread has left me speculating about what might be behind the different attitudes and concerns.
Articles Tagged with Disaster Recovery
Those of you who know me know that disaster recovery is a topic that is near and dear to my heart. For those of you whom I have not had the pleasure of meeting, I have spent most of my professional career working in Florida; I hope that offers a little insight into my special interest in disaster recovery.
There are three pillars to the software-defined data centre (SDDC): software-defined compute, software-defined storage, and software-defined networking. Without any one of these three, the whole edifice of the data centre falls down. We build all three to be resilient, “designed for failure,” and robust. Each can be built and rebuilt from scripts that are stored in distributed version control systems. But at the bottom of every application stack in our SDDC, there is a database or file store that cannot—by definition—be re-created from scripts. This is the core data that we mine and make profit from. What happens if (or when) the edifice collapses? How is that core data protected, and is traditional backup up to the task?
In my overview of Desktop as a Service (DaaS) delivery models last month, I touched on availability services, an emerging market that shows strong potential for future growth, and on DaaS services specifically tailored to disaster recovery. Now, fresh from witnessing the slightly embarrassing spectacle of San Francisco grinding to a halt after a little light rain, I thought it would be worth taking a closer look at Horizon Air Desktop DR.
During a recent Twitter conversation about disaster recovery and business continuity testing, I began to consider how we communicate during a disaster. We do so not with normal communication methods, but more often than not with an interrupting form of communication—one in which constant requests for updates, criticisms, and outright demands for attention are directed at those who are doing the work of recovering a system. During a disaster recovery effort, communication breaks down. Why? Generally, not enough testing has been performed to document communication issues or any other types of issues. How can we improve this communication, or even get the proper people involved, when six feet of snow, water, or mud surrounds our place of work?