58 lines
4.3 KiB
HTML
58 lines
4.3 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="Plan for data resilience" />
|
||
|
|
<meta name="abstract" content="Data resilience is achieved when data is always available to an user or application. You can achieve data resilience through the use of logical replication or switchable independent disk pools." />
|
||
|
|
<meta name="description" content="Data resilience is achieved when data is always available to an user or application. You can achieve data resilience through the use of logical replication or switchable independent disk pools." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaigplandesign.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaigplandeterminedatareplication.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaigconceptsreplicationvsswitchable.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaigplanreplication.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaigplanswitcheddisks.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="rzaigplandataresilience" />
|
||
|
|
<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>Plan for data resilience</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaigplandataresilience"><a name="rzaigplandataresilience"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Plan for data resilience</h1>
|
||
|
|
<div><p>Data resilience is achieved when data is always available to an
|
||
|
|
user or application. You can achieve data resilience through the use of
|
||
|
|
logical replication or switchable independent disk pools.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaigplandeterminedatareplication.htm">Determine which data should be made resilient</a></strong><br />
|
||
|
|
Understand what types of data you should consider making resilient.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaigconceptsreplicationvsswitchable.htm">Comparison of logical replication, switched disks, and cross-site mirroring</a></strong><br />
|
||
|
|
<span><img src="./delta.gif" alt="Start of change" />This topic provides an overview of different
|
||
|
|
data resilience technologies that can be used with clusters to enhance high
|
||
|
|
availability.<img src="./deltaend.gif" alt="End of change" /></span></li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaigplanreplication.htm">Plan for logical replication</a></strong><br />
|
||
|
|
Multiple copies of the data are maintained with logical replication. Data is replicated, or copied, from the primary node in the cluster to the backup nodes designated in the recovery domain. When an outage occurs on the primary node, the data remains available as a designated backup node takes over as the primary point of access.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaigplanswitcheddisks.htm">Plan for switchable independent disk pools and cross-site mirroring (XSM)</a></strong><br />
|
||
|
|
A single copy of the data is maintained on switchable hardware; either an expansion unit (tower) or an IOP in a logical partition environment.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaigplandesign.htm" title="Identify your needs to determine how to design your cluster.">Design your cluster</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|