• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar
  • Skip to footer
  • Skip to footer navigation
  • +1-(800)-337-6914
  • info@thinksis.com
  • Customer Portal
  • Careers
  • Schedule Briefing
  • Contact Us
  • Facebook
  • LinkedIn
  • Twitter
  • YouTube
SIS,  A Converge Company

SIS, A Converge Company

Cloud and Managed Services

  • Data Center Solutions
    • Server
    • Converged Infrastructure
    • Network
    • Data Protection
    • IT Spend Optimization
    • Security
  • Cloud Solutions
    • TruBACKUP
    • TruCOMPUTE
    • TruMANAGE
    • TruNETWORK
    • TruRESILIENCY
    • TruSTORAGE
  • AWS Storage Solutions
  • SIS Insights
  • About Us
    • Who We Are
    • Senior Leadership
    • Strategic Partners
    • Contact Us
    • Careers
  • Resources
    • Events
    • Blog
    • News

Application RTO and RPO Explained. Part 2: Service Level Agreements

May 14, 2018 by sisllc Leave a Comment

In Part 1 of this series, we defined Recovery Time Objective and Recovery Point Objective.

In Part 2 we will introduce and define the role that Service Level Agreements play in the recovery process. 

An SLA (Service Level Agreement) is a contract between the customer, end user, department, or organization and a service provider (could be internal technical staff or an outsourced entity) describing the availability of an application, infrastructure, or enterprise. Usually, there are mechanisms to ensure SLAs can be met and penalties outlined if they are not.

There are many parts to an SLA (Service Level Agreement) including but not limited to RTO/RPO, user accessibility, technical assistance or management of the application, and rollback or production stand up. For the purposes of this discussion, we will consider how an SLA influences application availability in the event of an unplanned outage.

RTO and RPO Service Level Agreement

Typically, an SLA encompasses both RTO and RPO. In many cases, SLAs reflect only RTO and assume RPO is zero. There might be an RTO component specifically called out in the SLA, but to be thorough, consider SLAs to include both RPO and RTO as shown in the figure below. Assume ‘Now’ indicates the present time, or the time of an outage.

Notice the additional time between the outer boundaries of RTO and RPO, and that they both reside inside the SLA.

SLAs (Service Level Agreements) can be enterprise-wide or application-specific. Sometimes multiple SLAs are determined for applications, departments or collections of applications, enterprises or departments, and so on. Regardless of how many layers of SLAs exist, the shorter the SLA the shorter the RPO and RTO, and the more costly hardware solutions become to ensure the SLA is attainable.

In addition to the above, some organizations employ the idea of an SLO, or Service Level Objective. SLOs usually exist between the collective RTO and RPO time, and that of the SLA. Or. One could argue that the SLO should be less than the RPO and RTO collective time. However you define it, the objective should be more aggressive than the agreement.

Service Level Objective

In Part 3, we will continue our explanation of RTO and RPO by discussing and analyzing an environment discovery process example. 

If you have any questions or comments please feel free to reach out to our technical team today

Reader Interactions

Leave a Reply Cancel reply

You must be logged in to post a comment.

Primary Sidebar

Recent Posts

  • Converge Technology Solutions Acquires Software Information Systems, LLC
  • Do you have challenges with your SAP environment?
  • Ready for Converged Infrastructure? Here are Four Things to Consider
  • Checklist for Cloud Data Management Solutions
  • 10 Questions and Answers about VMware Cloud on AWS

Contact US

Lexington, KY

Charleston, WV

Indianapolis, IN

Louisville, KY

Farmington Hills, MI

  • Facebook
  • LinkedIn
  • Twitter
  • YouTube

Footer

About Us

SIS produces results for growth-oriented companies through SIS Insights, the concentration of 30 years of experience in the minds of a dedicated, knowledgeable, and regional team.

More About Us

Connect with Us

Address: 165 Barr Street  Lexington, KY, 40507
Phone: +1-(859)-977-4SIS
Email: info@thinksis.com

  • Facebook
  • Google+
  • LinkedIn
  • Twitter

Our Newsletter

Subscribe to our newsletter to get the latest updates from our blog. We respect your privacy.

Sign Up Today

Copyright © · SIS · Terms & Conditions · Legal· Privacy Policy

  • Contact Us
  • SIS Insights
  • Careers
We use cookies on our website to give you the most relevant experience by remembering your preferences and repeat visits. By clicking “Accept”, you consent to the use of ALL the cookies. For more information view our Privacy Policy and Cookies Policy(US).
Cookie settingsACCEPT
Privacy & Cookies Policy

Privacy Overview

This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience.
Necessary
Always Enabled

Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.

Non-necessary

Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.