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.

Total costs vs. marginal costs

An important part of most discussions about clouds is an analysis of costs. People are strongly driven to try to reduce the costs of their burdensome infrastructure, particularly when a large part of it is almost never used (the DR provisions), yet is as costly as the primary in some cases. Most technical people we talk to are impressed with nScaled solutions, but that appreciation is viewed differently when they have to present it to their management team and justify the investment, and so the talk inevitably turns to costs.