110 lines
7.6 KiB
HTML
110 lines
7.6 KiB
HTML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<!DOCTYPE html
|
|
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
|
<html lang="en-us" xml:lang="en-us">
|
|
<head>
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
|
<meta name="security" content="public" />
|
|
<meta name="Robots" content="index,follow" />
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
|
<meta name="DC.Type" content="concept" />
|
|
<meta name="DC.Title" content="Decide what level of availability you need" />
|
|
<meta name="abstract" content="After understanding availability at a basic level, it important to assess your individual availability needs. Higher availability is more costly than a lower level availability. You must balance your needs and services with the overall cost of implementing and maintaining these availability solutions." />
|
|
<meta name="description" content="After understanding availability at a basic level, it important to assess your individual availability needs. Higher availability is more costly than a lower level availability. You must balance your needs and services with the overall cost of implementing and maintaining these availability solutions." />
|
|
<meta name="DC.Relation" scheme="URI" content="rzalwoverview.htm" />
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
|
|
<meta name="DC.Format" content="XHTML" />
|
|
<meta name="DC.Identifier" content="rzalwlevel" />
|
|
<meta name="DC.Language" content="en-us" />
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
|
<!-- US Government Users Restricted Rights -->
|
|
<!-- Use, duplication or disclosure restricted by -->
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
|
<title>Decide what level of availability you need</title>
|
|
</head>
|
|
<body id="rzalwlevel"><a name="rzalwlevel"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Decide what level of availability you need</h1>
|
|
<div><p><span><img src="./delta.gif" alt="Start of change" />After understanding availability at a basic level,
|
|
it important to assess your individual availability needs. Higher availability
|
|
is more costly than a lower level availability. You must balance your needs
|
|
and services with the overall cost of implementing and maintaining these availability
|
|
solutions.<img src="./deltaend.gif" alt="End of change" /></span></p>
|
|
<p>You want to be sure that you have analyzed your business needs thoroughly
|
|
in order to decide what level of availability you can afford to maintain.
|
|
To decide what level of availability you need, consider the following questions:</p>
|
|
<div class="section"><h4 class="sectiontitle">Do you have any applications that require 100% availability?</h4><p>In
|
|
most cases, you can achieve a high level of availability by implementing sound
|
|
processes and systems management practices. The closer you need to be to continuous
|
|
availability, the more of an investment you have to make. Before you make
|
|
that kind of investment, you should be sure that you require that level of
|
|
availability. The following figure shows how different techniques can improve
|
|
availability, but can increase the price you have to pay for it.</p>
|
|
<div class="p"> <div class="fignone"><img src="rzalw501.gif" alt="Determine your level of availability" /></div>
|
|
</div>
|
|
<p><img src="./delta.gif" alt="Start of change" />If your requirements for levels of availability increase,
|
|
you may want to consider multiple system availability solutions, such as clusters.<img src="./deltaend.gif" alt="End of change" /></p>
|
|
</div>
|
|
<div class="section"><h4 class="sectiontitle">How much downtime is acceptable to you?</h4><p>It may help
|
|
you to know what amount of downtime each level of availability represents.
|
|
The following table shows the amount of downtime you should expect for different
|
|
levels of availability.</p>
|
|
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><thead align="left"><tr><th valign="top" id="d0e37">Level of availability</th>
|
|
<th valign="top" id="d0e39">Downtime per year</th>
|
|
</tr>
|
|
</thead>
|
|
<tbody><tr><td valign="top" headers="d0e37 ">90%</td>
|
|
<td valign="top" headers="d0e39 ">36.5 days</td>
|
|
</tr>
|
|
<tr><td valign="top" headers="d0e37 ">95%</td>
|
|
<td valign="top" headers="d0e39 ">18.25 days</td>
|
|
</tr>
|
|
<tr><td valign="top" headers="d0e37 ">99%</td>
|
|
<td valign="top" headers="d0e39 ">3.65 days</td>
|
|
</tr>
|
|
<tr><td valign="top" headers="d0e37 ">99.9%</td>
|
|
<td valign="top" headers="d0e39 ">8.76 hours</td>
|
|
</tr>
|
|
<tr><td valign="top" headers="d0e37 "><img src="./delta.gif" alt="Start of change" />99.99%<img src="./deltaend.gif" alt="End of change" /></td>
|
|
<td valign="top" headers="d0e39 "><img src="./delta.gif" alt="Start of change" />50 minutes<img src="./deltaend.gif" alt="End of change" /></td>
|
|
</tr>
|
|
<tr><td valign="top" headers="d0e37 "><img src="./delta.gif" alt="Start of change" />99.999%<img src="./deltaend.gif" alt="End of change" /></td>
|
|
<td valign="top" headers="d0e39 "><img src="./delta.gif" alt="Start of change" />5 minutes<img src="./deltaend.gif" alt="End of change" /></td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
</div>
|
|
<p>Along with knowing how much downtime is acceptable to you, you
|
|
need to consider how that downtime may occur. For example, you may think that
|
|
99% availability is acceptable if the downtime is a series of shorter outages
|
|
that are distributed over the course of a year. But, you may think differently
|
|
about 99% availability if the downtime were actually a single outage that
|
|
lasts 3 days.</p>
|
|
<p><img src="./delta.gif" alt="Start of change" />You also need to consider when
|
|
a downtime is acceptable and when it is not. For example, your average annual
|
|
downtime goal per year might be 9 hours. If that downtime were to occur during
|
|
critical business hours, it could have an adverse affect on the bottom line
|
|
revenue for your company.<img src="./deltaend.gif" alt="End of change" /></p>
|
|
</div>
|
|
<div class="section"><h4 class="sectiontitle">What level of access do your customers need to your business?</h4><p><img src="./delta.gif" alt="Start of change" />It used to be that customers and business partners accessed your
|
|
business from 9 a.m. to 5 p.m., so it was realistic to expect that your system
|
|
only had to be available during those hours. However, the Internet and a diverse
|
|
global marketplace have changed that expectation; customers and business associates
|
|
may expect to have access to your company's data at any time of the day or
|
|
night. Your working hours may be hours or even days different from your global
|
|
business partner or customer. You have to determine what your customer expectations
|
|
are, and what is realistic with regard to those expectations, as you determine
|
|
what level of availability you will maintain.<img src="./deltaend.gif" alt="End of change" /></p>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzalwoverview.htm" title="In today's fast-paced Internet environment, it is crucial that your data and applications be available to you when you need them. If your customers cannot access your Web site because your system is down, they may go to your competitors instead.">Availability roadmap</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |