97 lines
7.5 KiB
HTML
97 lines
7.5 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="Availability roadmap" />
|
|
<meta name="abstract" content="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." />
|
|
<meta name="description" content="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." />
|
|
<meta name="DC.Relation" scheme="URI" content="rzalw_whatsnew.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzalw_print.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzalwconcepts.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzalwvalue.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzalwlevel.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzalwprevent_unplanned.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzalwshorten_unplanned.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzalwshorten_planned.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzalwclusters.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzalwcompsolutions.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzalwrelated.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="rzalwoverview" />
|
|
<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>Availability roadmap</title>
|
|
</head>
|
|
<body id="rzalwoverview"><a name="rzalwoverview"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Availability roadmap</h1>
|
|
<div><p>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.</p>
|
|
<p> <dfn class="term">Availability</dfn> is the measure of how often your data and applications
|
|
are ready for you to access when you need them. Different companies have different
|
|
availability needs. Different systems or different applications within the
|
|
same company may have different availability needs. The purpose of this topic
|
|
is to guide you through the world of iSeries™ availability and help you decide
|
|
which availability tools are right for your business. It is important to note
|
|
that availability requires detailed planning; these availability tools are
|
|
only useful if you have implemented them <span class="uicontrol">before</span> an
|
|
outage occurs.</p>
|
|
<p>Before you can really start to plan for availability on your system, you
|
|
should become familiar with basic availability concepts, understand the costs
|
|
and risk associated with outages, and determine your company's needs for availability.
|
|
Once you have a basic understanding of availability concepts and know what
|
|
level of availability you need, you can start to plan for that level of availability
|
|
on a single system or for multiple systems within a cluster environment.</p>
|
|
</div>
|
|
<div>
|
|
<ul class="ullinks">
|
|
<li class="ulchildlink"><strong><a href="rzalw_whatsnew.htm">What's new for V5R4</a></strong><br />
|
|
Learn about new function that relates to the Availability roadmap.</li>
|
|
<li class="ulchildlink"><strong><a href="rzalw_print.htm">Print this topic</a></strong><br />
|
|
Use this to view and print a PDF of this information.</li>
|
|
<li class="ulchildlink"><strong><a href="rzalwconcepts.htm">Availability concepts</a></strong><br />
|
|
Before you can plan for the availability of your system, it is important for you to understand some of the concepts associated with availability.</li>
|
|
<li class="ulchildlink"><strong><a href="rzalwvalue.htm">Estimate the value of availability</a></strong><br />
|
|
No one would argue the importance of availability. However, when asked to justify the cost of additional hardware to support improved availability, many people do not know how to build a case.</li>
|
|
<li class="ulchildlink"><strong><a href="rzalwlevel.htm">Decide what level of availability you need</a></strong><br />
|
|
<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></li>
|
|
<li class="ulchildlink"><strong><a href="rzalwprevent_unplanned.htm">Prevent unplanned outages</a></strong><br />
|
|
One way to approach availability is to try to prevent unplanned outages. You can use these different methods to ensure that your system experiences as little unplanned downtime as possible.</li>
|
|
<li class="ulchildlink"><strong><a href="rzalwshorten_unplanned.htm">Shorten unplanned outages</a></strong><br />
|
|
Unplanned outages do occur, and a key to availability is to ensure that when they do occur you can recover from them as quickly as possible.</li>
|
|
<li class="ulchildlink"><strong><a href="rzalwshorten_planned.htm">Shorten planned outages</a></strong><br />
|
|
Planned outages are necessary and are expected; however, because they are planned does not mean they are nondisruptive. Planned outages are often related to system maintenance.</li>
|
|
<li class="ulchildlink"><strong><a href="rzalwclusters.htm">Availability for multiple systems: Clusters</a></strong><br />
|
|
For multiple system environments, you can use clusters as a strategy to maintain a high or continuous availability for your systems and applications.</li>
|
|
<li class="ulchildlink"><strong><a href="rzalwcompsolutions.htm">Data resilience solutions for i5/OS Clusters</a></strong><br />
|
|
This topic provides an overview of different data
|
|
resilience technologies that can be used to with i5/OS™ Clusters to enhance high availability
|
|
in multiple system environments. </li>
|
|
<li class="ulchildlink"><strong><a href="rzalwrelated.htm">Related information for Availability roadmap</a></strong><br />
|
|
Several sources relate to Availability roadmap. Use these iSeries manuals, IBM<sup>®</sup> Redbooks™ (in
|
|
PDF format), and Web sites to learn more about high availability, backup and
|
|
recovery, clusters, and other related topics. You can view or print any of
|
|
the PDFs.</li>
|
|
</ul>
|
|
</div>
|
|
</body>
|
|
</html> |