First of all, it is very important to always keep “the big picture” in mind. Backup and DR processes must be aligned with the business requirements and the resulting technical requirements.
Furthermore, it is important to understand how hyper-convergent infrastructures change or influence these processes. This can be a complex task in the first phase. However, the better and more detailed the business requirements are pointed out and the more the concept is aligned with the technical requirements, the better the implemented tools and processes will fit.
Below are a few questions about business and technical requirements which need to be addressed and discussed:
RPO/RTO and SLA definitions are very important aspects to consider when planning backup and DR processes. I would like to explain the meaning of these three terms in more detail below:
RTO: The Recovery Time Objective (RTO) is the time that elapses after a computer or application crash or network interruption before the system can resume normal operation and allow access to the data. The RTO value is expressed in a unit of time – in seconds, minutes, hours, or days.
RPO: The Recovery Point Objective (RPO) is the point in time at which an IT system or IT infrastructure can be restored after a failure. It remains directly dependent on the Recovery Time Object (RTO).
SLA: A Service Level Agreement (SLA) is a contract between a service provider and a customer. The contract usually specifies the scope of the service and the quality of service (service level). Many Internet Service Providers (ISP) offer their customers an SLA. IT departments in large companies often also set up service level agreements to make the services more transparent to customers (the users in the company’s departments). These services can be justified, measured and they can be compared with external offers.
SLAs can include the following definitions:
- The percentage availability of services
- The number of users that can be served simultaneously
- Performance benchmarks for regular comparison with current values
- The timeframe for early notification of any service restriction
- The response time of the helpdesk for various classified problems
- The availability of access
- The provision of usage statistics
A backup and DR concept should primarily be aligned with these specifications to support business processes in the best possible way.
A well-developed backup and DR concept is essential to support the availability of core applications in an enterprise. Even in the new “cloud” based world.
The 2nd part of the article series deals with the technical functions and features of the NUTANIX platform and how they can be used within the backup and DR concept.
- For information about Disaster Recovery, visit our IDR solution which provides a stand-alone application that makes it easy to be Disaster Ready. (link)
- For information about ensuring the data quality of your tape library, visit our Tape Audit Tool solution which provides automated auditing on the quality of your backup data and ensure the data can be read when needed. (link)
The original version of this article by Patrick Huber (SVA GmbH) can be found under https://focus.sva.de/next-gen-backup/.