Three Ways Your Disaster Recovery Falls Flat

By Zerto, on 1 May, 2012

This week’s series of posts is by Steve Thomsen, Zerto’s Director of Central US Sales. Follow Steve on Twitter.

When organizations think about disaster recovery and the associated processes, the term “non-disruptive” usually isn’t one of the first things to come to mind. In fact, it usually doesn’t come to mind at all. But why is that? DR is about protecting the organization from downtime and data loss right?

Sort of.

Rachel Dines, a Sr. Analyst at Forester Research, has a very interesting take on this. She believes instead of disaster recovery and business continuity, organizations should be thinking in terms of service continuity. Funny how one word can totally change your perception of how things are vs. how they should be. Big shout out to Rachel.

What is IT service continuity (or my fave, “non-disruptive DR”)? At Zerto, we see this as always-on continuous recovery that does not disrupt your production environment in any way. There are three main aspects to developing a strategy for service continuity; deployment, day-to-day management, and by far the most critical – the actual recovery (aka failover).

Guess what?  In all three areas, your current DR solution falls flat.

Your DR Falls Flat – Example # 1: Deployment

For most Disaster Recovery solutions, implementation can be very, very ugly. Particularly if you are looking at storage-based replication, the set-up is quite tedious and expensive. If you are switching out vendors get ready to deal with little things like having the replace your multi-pathing SW, LUNs that would seem to be the same size and configuration but aren’t, potential proprietary data formats, etc. Throw in storage virtualization and you have added another abstraction layer. Then there is the process of mapping your VMs down to the storage. And yes, there is even more of this type of stuff. What you get is pretty much a nightmare and a big bill ($$$) from your vendor. REALLY BIG.

With Zerto deployment is simplified; which also means much lower cost. Implementing Zerto Virtual Replication is non-disruptive and requires no downtime (for real!). This applies whether you are deploying the Zerto VMs into the environment or configuring protection for your virtualized applications. You configure and start replication for a live application running in VMware with no impact to the end users. This includes the policy or QoS setting for protection of the application (RPO goals, point-in-time protection history, bandwidth), the target resources to be leveraged (host/cluster, datastore(s), network), and network failover (re-IPing, DNS changes, etc.). Gone are things like having to go on a scavenger hunt to map your VMs down to the storage, etc.

A few years ago, and in a different life, I was part of project to migrate a very large federal agency into a hosted data center. It took months and a few million $$$ to pull it off. With Zerto we could have cut the downtime to almost zero and come in much, much lower in cost. Zerto is true game changer in terms of DR deployment.

Continue with “Three Ways Your DR Falls Flat…Part 2: Day to Day Operations”. Get the RSS feed here.

One comment on “Three Ways Your Disaster Recovery Falls Flat

  1. Pingback: Three Ways Your Disaster Recovery Solution Falls Flat | Technology News - Software - Hardware - Backup Restore | Scoop.it

Leave a Reply

Your email address will not be published. Required fields are marked *


*