<img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=142534916268940&amp;ev=PageView&amp;noscript=1">

DRaaS’ Deciding Factors: RTO and RPO

Posted by Neil Glazebrook on 12/2/16 9:00 AM

disaster recovery

There are an almost unlimited number of scenarios where you would need a disaster recovery solution. An actual disaster like an earthquake or flood; something a little less serious, like a power outage; or something that’s a complete disaster for your company but doesn’t make the nightly news, such as a user error that cripples your system.

Up until now, there have been limited options for enterprises recovering from disasters. Most organizations built secondary sites, or duplicate storage arrays and apps housed at a location other than the company’s main office. This environment requires management, constant upkeep and high-speed network access to ensure synchronous or asynchronous data replication between the arrays. This process is, obviously, expensive and involved – adding cost in terms of employee time, technology maintenance and physical space.

The time has clearly come to change this model. With the advent of the cloud, disaster recovery as a service (DRaaS) simplifies and improves the backup process. DRaaS allows your company to access all of its data instantly, without having to maintain storage infrastructure – and it can benefit businesses of any size. However, organizations considering a move to DRaaS should particularly consider two important metrics: recovery time objective (RTO) and recovery point objective (RPO).

Recovery time objective

RTO is the maximum amount of time that critical IT resources can be down without creating significant risks or incurring business losses. With most companies, this time is likely very close to zero, right?

Wrong. Conventional, array-based solutions often take a significant amount of time to replicate data and bring it online, leaving RTO much higher than is acceptable. With DRaaS, your data is constantly available at the DR site.

Recovery point objective

RPO is the maximum amount of time that your company’s data can be lost as a result of a major incident – for example, if your data is held in a temporary cache until it can be replicated, RPO concerns your window of time to recover that information. Again, most companies are looking for a time as close to zero as possible, and DRaaS can make this goal a reality. 

When you consider RTO and RPO, then add benefits like cost, scalability and support for a wider hybrid cloud strategy, DRaaS becomes a clear choice for many enterprises. The time has come for traditional disaster recovery and business continuity to go the way of the 3.5-inch floppy disk: an innovation that was great for its time, but was ready to be replaced by something much better.

Learn how to replace (and improve) your disaster recovery plan with DRaaS.

Topics: Enterprise Storage, DRaaS

About the Author

Neil Glazebrook

Neil has served in various senior product management positions, bringing complex networking and video technologies to market. Before joining ClearSky Data, Neil was a product manager in Akamai's media business unit, and then in a channel sales role managing six of Akamai’s largest media channel partners.

Prior to Akamai, Neil held senior product management roles at Cisco Systems over the course of 13 years. During that time, he spearheaded the formation of Cisco’s video networking business unit and was a key member of the integration team that oversaw the Arroyo acquisition. He led early adoption of solid state drives for Cisco’s service provider video product portfolio, helping drive down costs while drastically increasing streaming cache performance and session density.

Neil co-authored an IEEE paper on multicast IPTV distribution and error correction. He recently earned an MBA with Honors from Babson College.

View more posts by Neil Glazebrook.

Follow me: