Most data centers are reporting a dramatic increase in the number of applications they have to deploy, support and protect. Driving this phenomenon is the improvements in developer tools that created the whole Dev/Ops movement. While most of these apps don’t need to meet a zero downtime service level they do, in the event of a failure, need to return to service quickly. In this StorageShort listen in as Storage Switzerland and NetApp discuss the impact of the “app explosion” on service level objectives.
Two of the key components of a service level driven data protection strategy are recovery point objective (RPO) and recovery time objective (RTO). The higher the expectations on these objectives, the more expensive it becomes to meet the commitment – the epitome being a “zero” RPO/RTO. The good news is most new apps don’t fall into the “zero” category, which is reserved for only mission critical applications. The bad news is most apps do fall into the “important” category which means a sub hour, and in some case as some 15 minute RPO/RTO.
Because of the sheer number of apps that fall into this category, the modern data protection solution has to frequently protect the data, which will require low impact backups with minimal data transfer. It also needs to reposition data quickly in the event of a failure, which we refer to as recovery in place.
We cover these requirements in detail in our on-demand webinar, “The Always-on Enterprise Requires New Service Level Objectives”. Click here to watch it now.