DIY

How to Avoid Hardware/ Software Drift

I’ve been writing about the hidden hazards of do-it-yourself disaster recovery. One of these hazards is hardware/software drift. Since your disaster recovery site represents a working replica of the production environment, it will need to be maintained on an ongoing basis. There are several strategies for how hardware and software are provisioned for your DR site. The strategies you choose will determine the how much maintenance will be needed to keep your DR site running at an optimal level.

There are two main techniques for acquiring hardware for a disaster recovery site, although you may want to use a combination of both. One technique is to replace hardware (i.e. a server) that is no longer covered by warranty with new hardware and use the old hardware for disaster recovery. Another strategy is to buy or lease new equipment to use at the DR site.

The Hidden Hazards of SAN-to-SAN Replication

It might be tempting to create a “do-it-yourself” disaster recovery solution by purchasing additional hardware and installing it in a branch office or colocation facility. But creating an effective disaster recovery solution is a complex project and there are several unplanned costs and other hidden hazards associated with it. I’ll identify some of these hidden hazards over the next few weeks.

I’ll begin with SAN to SAN replication. Any SAN manufacturer with a clear understanding of storage space has some kind of SAN to SAN replication offer, but not all SAN to SAN replication is alike. When creating an effective DR solution, you have to make several architectural considerations for replicating data between production and DR, including virtualization, application specific agents and snapshot storage requirements.