SLA
SLA
ABOUT
o Our Approach
o Case Studies
o Leadership Team
o Careers
SOLUTIONS
o SAP
Cloud Migration Advisory Services
Hosting
S/4HANA Migrations
Upgrades & Implementations
Managed Services
CxLink Product Family
RISE with SAP
Business Analytics
o Oracle EBS
Hosting
EnterpiseCare® Monitoring
Upgrades & Implementations
Managed Services
Business Analytics
o JD Edwards
Hosting
EnterpriseCare® Monitoring
Upgrades & Implementations
Managed Services
Business Analytics
o Security
MEDR Protection
Azure Sentinel / Office 365 Defense
Vulnerability Protection
o Beyond ERP
Digital Workplace
Digital Workplace Security
Managed Microsoft 365
Modern Collaboration
Modern Device Management
Industrial Internet of Things (IIoT)
Syntax Business Analytics Services
PLATFORMS
o AWS
AWS Well-Architected Program
SAP on AWS
Managed Services in the AWS Cloud
Security Managed Services on AWS
o Azure
o Oracle Cloud Infrastructure
o Syntax Enterprise Cloud®
o Hybrid Cloud
INDUSTRIES
o Manufacturing
Automotive
Life Sciences
Paper and Packaging
o Engineering, Construction and Operations
Building Materials
o Mining and Natural Resources
o Professional Services
INSIGHTS
o SAP
o Oracle EBS
o JD Edwards
o Cloud
o Security
o Beyond ERP
CONTACT
...
o Syntelligence
o iSDM
o Events
o Newsroom
o Blog
GLOBAL REGIONS
o Americas
o Europe
German
English
French
Spanish
o Asia
EN
o FR
Search:
Operational Service Level
Agreements (SLAs): What Seasoned
CIOs Know
February 12, 2020
While all cloud service providers (CSPs) offer some type of operational availability, it’s
important to understand what the provider is actually measuring.
They know there are two types of operational service level agreements (SLAs):
1. Infrastructure availability
2. Application availability
What separates a seasoned CIO from their peers is the ability to understand which one
they’re getting.
Often cloud service providers offer a high availability number such as 99.99 percent.
However, when you dig into it, they’re really only talking about the infrastructure.
Sure, the application relies upon the underlying infrastructure to run, but what good does
it do if the servers are up, but the application is not?
Knowing this then, you’ll want to make sure your CSP is offering an application availability
SLA.
Why?
Because it ensures they have some skin in the game when it comes to what’s important to
your business.
Well, that really depends on the application. Software as a Service (SaaS) applications
like Salesforce.com, Microsoft Office 365, and SAP Concur can achieve very high levels
of availability due to their web scale architecture.
As a result, it’s very difficult/costly to truly architect a 99.999 percent or even a 99.99
percent SLA.
Yes, there are plenty of deployments out there where ERP has never been down, but this is
primarily due to good operational and change management practices rather than the
underlying technical architecture.
Let’s assume you’re like many CIOs out there: SAP ERP is a core business application and
you simply can’t have it go down. After all, if it’s down your production line stops, you
can’t ship product and you can’t process any orders.
Odds are you insist that your provider gives you 99.99 percent availability because your
business processes can probably tolerate four minutes of unplanned downtime a month.
And so, the service provider does exactly what you ask. They double up on everything and
put in every bell and whistle it takes to architect your application and achieve 99.99
percent availability.
This of course costs you more money. A lot more money.
Since most CSPs provide either 99.5 percent (or in the best-case 99.9 percent) availability
for SAP, this becomes a one-off deployment. Which in turn makes this much more difficult
to operate.
Why?
Because rather than having 30 operations people who can fix it when it breaks, you’re
likely down to only one or two information technology (IT) pros who really know how it is
set up.
And in IT, what can go wrong usually does, but never, ever, in the way it was tested to fail.
(Hey, if nothing else, Ol’ Murphy has a sense of humor!)
So now with this 99.9 percent “super-duper” architecture, when something is broken you
have to find one of those two guys who set it up to fix it. Instead of facing an issue that
should have taken 30 minutes to solve, it’s now turned into eight hours of escalations and
headache.
Clearly, you can spend a lot of money architecting traditional applications to promise high
availability, but it comes with an extra cost – that is, the risk adding a lot of operational
complexity.
More often than not, it’s the fat finger that’s at fault rather than the architecture.
As you work with your CSP, your best bet is to ensure they give you an application
availability SLA that fits their standards. You also want them to establish a business
continuity plan for you should bad things happen.
“My business applications are important, and we will put all the components in place
to make sure they are up and running, but if they are down, we have a plan to remedy
the situation.”
A seasoned CIO knows that running business solely on the promise of a cloud service
provider’s SLA is a recipe for disaster.
RETURN TO BLOG
Recent Posts
How Syntax CxLink Backup Delivers Better, Faster and More Cost Effective SAP
Backups
SAP on AWS migration: 5 common mistakes and how to avoid them
Demystifying Data Sharing in Oracle 19c Multitenant Architecture
Disk Space and Journaling Issues on the iSeries Operating System
Identifying E-Business Suite 12.2 CPU Patches and Security Fixes Using the
ECPUC Tool
1-866-705-6385
[email protected]
Youtube
Legal Notices
Terms
Privacy Policy
EU-US-shield
Services Privacy Policy
© Syntax 2023