AL DíA: Disaster Recovery
Awhile back, I had the chance to facilitate a technology leadership summit at TCEA. This resulted in a brace of blog entries I wrote for TCEA. You can read the first one online at TCEA’s TechNotes blog:
Some of my key takeaways involved emphasizing the importance of the points below. I’ve tried to illustrate them with points taken from my own experience as Director of Technology for a San Antonio school district. I honestly felt like the Hooper in the old Burt Reynolds movie.
- Recognizing the need: “Like Burt Reynolds in the Hooper car chase scene where every building collapses and fires blaze as Reynolds deftly navigates his vehicle through them, I felt like we were replacing obsolete equipment just as it failed,” I said as I shared my equipment replacement tale of adventure. Years of neglect had left servers with critical data ready to die.
- Clarifying the depth of the hole the organization is in: One way to do this was to make a table of failing physical servers and the need to virtualize them
- Presenting a plan to never be in that hole again. The next step involves an equipment replacement plan. And that is then followed by a disaster recovery and business continuity plan.
At the time I was writing this blog entry for TCEA, I had the chance to have a few more conversations with folks. One of them was with Edward Doan from Google.
- Edward Doan (Google) provided his slide deck on Google Cloud Storage, as well as was able to record a short voxercast discussing the topic.
I’ll have to link the second part (which contains the lion’s share of insights) later.
Updated 11/18/17 to include link to Part 2 of When Disaster Strikes
Everything posted on Miguel Guhlin’s blogs/wikis are his personal opinion and do not necessarily represent the views of his employer(s) or its clients. Read Full Disclosure