
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Availability Management and Calculations</title>
<link>https://itsmfuk.site-ym.com/forums/posts.aspx?topic=1803435</link>
<description></description>
<lastBuildDate>Sat, 6 Jun 2026 18:50:32 GMT</lastBuildDate>
<pubDate>Thu, 12 Dec 2024 13:34:09 GMT</pubDate>
<copyright>Copyright &#xA9; 2024 itSMF UK</copyright>
<atom:link href="https://itsmfuk.site-ym.com/forums/topic_rss.asp?id=1803435" rel="self" type="application/rss+xml"></atom:link>
<item>
<title>Availability Management and Calculations</title>
<link>https://itsmfuk.site-ym.com/forums/posts.aspx?topic=1803435</link>
<guid>https://itsmfuk.site-ym.com/forums/posts.aspx?topic=1803435</guid>
<description><![CDATA[<p>As cloud has taken a more prominent role in hosting of applications i am interested in understanding how areas are setting availability targets .&nbsp;</p><p>AWS tend to provide Multi zone and single zone availability and this is for each service they offer . So if you purchase multiple services ( say 5 ) but all are at Multi Region (99.9%) are you setting your application availability based upon standard ITIL practice of Multiplying the 5 targets together so you end up with 99.5% or because the likelihood if failure is small because you have built in multi zone capability you would set the target as 99.9%&nbsp;</p><p>AWS appears to be more about zone availability that on premise hosting where you would base on servers and load balancing&nbsp;</p><p>There are other factors you would add in like Network capability to get to the cloud hosting but am more interested in the cloud approach people are taking</p>]]></description>
<pubDate>Thu, 12 Dec 2024 14:34:09 GMT</pubDate>
</item>
</channel>
</rss>
