You’ve heard the story about the frog in hot water, haven’t you? The frog is in a pot of water, which is slowly heating up. But the frog doesn’t notice. The water gets hotter, slowly, and eventually the frog gets boiled.
Just like the frog, many IT managers are in hot water today. I say this because many IT leaders tell me that a disaster recovery plan is “nice to have,” but not necessary. They aren’t doing anything to build a disaster site or do recovery planning and testing. They have become accustomed to a status quo which is, in fact, an unacceptable way to run a business. Everything seems OK until it’s not. Suddenly, when disaster strikes, they’re not prepared.
The surprise for these IT teams is that getting out of the pot is much easier and less expensive than they might have imagined. Let me explain with a story about one company that did just that.
Why Disasters are Disastrous
Recently, I consulted with a law office whose 100 lawyers handle many big corporate clients, helping them go public or conduct mergers and acquisitions. The firm’s four-person IT infrastructure team runs a traditional stack with nightly backups. But, like many smaller companies, they don’t have an offsite disaster recovery location or plan beyond those backups.
We talked about how hyperconverged infrastructure can not only save time and money, but also reduce business risk by reducing recovery time objectives (RTO). In their case, it would cut RTO from 17 hours to 30 minutes. At first, in this IT director’s mind, reducing RTO was in the “nice to have” category until we started to explore what exactly would happen if disaster did strike.
For example, this law office helps take companies public. What happens to all that carefully gathered and customer-critical data? If systems are down, lawyers miss delivery deadlines and customer meetings. He had to agree that the concern for the firm went beyond the loss of productivity. For the senior partners of this law firm, brand and reputation are the paramount concerns. The risk was unacceptable. Viewed this way, the firm moved swiftly to migrate to hyperconverged infrastructure with a full disaster recovery plan. Most importantly, with SimpliVity, the law office saved a significant amount on their IT budget and the disaster recovery feature was a very valuable add on.
Reducing Business Risk with Hyperconverged Infrastructure
Most people who have heard of hyperconvergence know that it replaces traditional compute and storage. But few realize its implications for disaster recovery. Properly architected and deployed across two or more sites, a hyperconverged infrastructure not only reduces capital and operational costs, it also delivers disaster recovery—built-in.
Fully accounting for the value of hyperconvergence, then, you must not only look at capital and operational costs. You need to think about business continuity risk as well.
The surprise for many IT managers, then, is two-fold:
- Senior business executives care about business continuity more than they think.
- The cost of implementing disaster recovery with hyperconverged infrastructure is less than they think.
The gap between the status quo and well-managed disaster recovery solution is, in fact, much smaller than most people think. Hyperconvergence closes that gap – and it’s a good way to keep out of hot water.
For a more in-depth analysis of disaster recovery through hyperconverged infrastructure, take a look at the SimpliVity HyperGuarantee.