Azure VM SLA and high availability confusion
Abs07act
Since Microsoft Azure announced Single Instance SLA for
Azure Virtual Machine, people are getting confused if availability sets with
multiple VMs are required or no?
This post is to address various queries I received
regarding Azure VM availability and SLA.
Disclaimer:
All below views are personal. In no way, it represents the company I work for.
SLA stands for Service Level agreement. It is a con07act
between service provider(here, Microsoft Azure) and end user(anyone, any
organization who user Microsoft Azure services); that defines the level of service expected from the
service provider.
If expected level of service is not provided and there
is loss of business for end user then end user may claim for financial recovery
with valid reasons, proofs, evidences etc. If evidences are valid and
justified, then it will be an obligation for service provider to approve the
claim and make payments.
Depending on the SLA provided, availability can be
identified. Many online websites tools available for knowing what uptime of
service you get based on SLA percentage. For example, if SLA offered as 99.90%
means below can be approximate time periods of potential downtime/
unavailability of the service –
- Daily: 1m 26.4s
- Weekly: 10m
4.8s
- Monthly: 43m
49.7s
- Yearly:
8h 45m 57.0s
SLA percentage at 99.9% and above are general and
indus07y accepted standards. Reference link used for calculation is here.
If you want to achieve 99.95% SLA for Azure VM
deployment you should have at-least 2 instances of Azure VM running in
Availability set.
P.S. Azure VMs with availability sets can be provisioned
from the portal.
Irrespective of type of storage disk used for Azure VMs,
SLA 99.95% is valid as long as you are running 2 instances in availability
sets. This means if I want high availability for my crucial workloads under
Azure VM then I should be running at least 2 VMs on azure in availability sets.
2 VMs with no availability sets means no SLA also. 😊
Comments
Post a Comment