Enterprises have long had to balance two critical, competing demands when it comes to data protection and disaster recovery: money and time. In attempts to save their budgets, organizations have spent years structuring DR plans around secondary data centers. Built on cheap real estate in remote locations, these sites seemed – at first – to deliver, at least when companies measured value in dollars. Recovery metrics, however, were a different challenge.
More recently, as enterprises moved more workloads to the cloud, those isolated data centers started to present latency challenges (which have a nasty habit of turning into economic challenges). CIOs have found themselves spending unpredictably on replicating, storing and accessing data from the cloud, while migration challenges, unpredictable processes and latency timeframes have made recovery too slow.
When it comes to DR, enterprises must value recovery metrics – specifically, recovery time objective (RTO) and recovery point objective (RPO). What’s the maximum amount of time your critical IT resources can be down before you see significant losses? For many companies, that number is less than one minute. And what about data loss? What’s the cost to the business when the backup data is hours old? Most C-level executives would say that cost is too high, no matter how much they saved on remote real estate prices for their secondary data centers. Today’s desirable RPO is 0.
Getting to RPO 0 and RTO less than a minute should be the enterprise standard, especially when companies can reach those goals while still cutting their DR expenses in half.
Today, moving past on-prem DR and DR as a service (DRaaS), minimal RTO and RPO expectations require a truly hybrid approach that makes data accessible to enterprise users anywhere. This must happen without the expense of redundant architecture or data sitting dormant in multiple locations. Find out how to reach this goal in our latest SlideShare, “How Do You Spell Disaster Recovery Success? RPO: 0, RTO: <1 minute.”