The disaster recovery (DR) vision is a scenario in which all disasters are withstood; using a well-crafted plan,...
By submitting your email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. You can withdraw your consent at any time. Contact TechTarget at 275 Grove Street, Newton, MA.
operations are transferred to a remote facility to get the organization back online within recovery time objective (RTO) and recovery point objective (RPO) targets. But this is pure fantasy for most companies. The reality is that if a disaster should occur, nothing short of Herculean efforts by the IT staff would be required to have the slightest chance of getting back online in any reasonable period of time, much less the targeted RTO.
This webcast checklist provides a DR reality check. In this concise, but informative webcast series, James Damoulakis, CTO, GlassHouse Technologies gives you the top 10 reasons why your DR plan may fail.
Lesson One: Business and IT aren't linked
If there is a disconnect between the business units and IT there may be mistakes in how data is recovered and which applications are brought back first. Lesson one of "10 reasons why your DR plan won't work" covers how to bridge the gap between the business units and IT.
Lesson Two: You don't have a DR plan
If you don't have a DR plan, it's hard to mess it up. But, it's also hard to recovery efficiently. Lesson two covers how to get started with a DR plan if your company is without one.
Lesson Three: How to keep your DR plan current
Do you have the proper change controls for your DR plan? Lesson three covers how to keep your DR plan up-to-date.
Lesson Four: Testing your DR plan
How do you know what can really go wrong unless you have a detailed DR testing plan in place. Lesson four of "10 reasons why your DR plan won't work" helps you figure out the best way to test your well thought out plans.
Lesson Five: Pie-in-the-sky recovery goals
It and the business units should be on the same page when it comes to realistic goals for recovery. This lesson gives you hints on how to plan and set expectations.
Lesson Six: Unclear roles and responsibilities
This lesson discusses the planning process, so you are organized should disaster strike.
Lesson Seven: Chasing the wrong risks
Knowing where the pitfalls are before disaster hits is critical to being able to recover properly and effienctly. This lesson gives you a better understanding of disaster categories so you can effectively map out the right strategy.
Lesson Eight: Bad backup
If your backups are broken, it makes it pretty hard to recover data. Lesson eight of "10 reasons why your DR plan won't work" talks about fixing those bad backups.
Lesson Nine: Alternative recovery services
In a worst case scenario, your staff may not be the ones to recover data. Lesson nine explores alternative options for recovery.
Lesson 10: Cutting DR costs
Let's face it, a thorough DR plan is very expensive. But, many times very necessary. This lesson covers the costs of DR and how to keep them in check.
About James Damoulakis
James Damoulakis is CTO at GlassHouse Technologies. Jim brings 20 years of experience in systems, storage, backup/recovery, and DR, with a strong focus on architecting and implementing highly available enterprise storage solutions. Jim has spoken on storage issues in a number of venues and is a frequent contributor to key industry publications like STORAGE Magazine. Prior to joining GlassHouse, Jim was Director of Implementation Services at CNT/Articulent in Hopkinton, MA, where he managed a team of senior technical consultants focused on SAN design and implementation, enterprise storage management, backup/recovery, and high availability. Previously, Jim was Director of Technical Services at Invincible Technologies Corporation, where he was responsible for technical support and professional services around ITC's highly available, networked attached storage products. Jim has also held a variety of management and technical positions with Digital Equipment Corporation, FTP Software, NEC Technologies, and Apple Computer.