71 lines
5.2 KiB
HTML
71 lines
5.2 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="Data availability and protection" />
|
||
|
|
<meta name="abstract" content="In a distributed relational database environment, data availability not only involves protecting data on an individual server in the network, but also ensuring that users have access to the data across the network." />
|
||
|
|
<meta name="description" content="In a distributed relational database environment, data availability not only involves protecting data on an individual server in the network, but also ensuring that users have access to the data across the network." />
|
||
|
|
<meta name="DC.subject" content="data availability and protection" />
|
||
|
|
<meta name="keywords" content="data availability and protection" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1kickoff.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1recovsupp.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1netredund.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1dataredund.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="rbal1recover" />
|
||
|
|
<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>Data availability and protection</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbal1recover"><a name="rbal1recover"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Data availability and protection</h1>
|
||
|
|
<div><p>In a distributed relational database environment, data availability
|
||
|
|
not only involves protecting data on an individual server in the network,
|
||
|
|
but also ensuring that users have access to the data across the network.</p>
|
||
|
|
<p>The <span class="keyword">iSeries™ server</span> provides the
|
||
|
|
following array of functions to ensure that data on servers in a distributed
|
||
|
|
relational database network is available for use: </p>
|
||
|
|
<ul><li>Save/restore</li>
|
||
|
|
<li>Journal management and access path journaling</li>
|
||
|
|
<li>Commitment control</li>
|
||
|
|
<li>Auxiliary storage pools</li>
|
||
|
|
<li>Checksum protection</li>
|
||
|
|
<li>Mirrored protection and the uninterruptible power supply</li>
|
||
|
|
</ul>
|
||
|
|
<p>While the system operator for each server is typically responsible for
|
||
|
|
backup and recovery of that server's data, you should also consider aspects
|
||
|
|
of network redundancy as well as data redundancy when planning your strategy
|
||
|
|
to ensure the optimum availability of data across your network. The more critical
|
||
|
|
certain data is to your enterprise, the more ways you should have to access
|
||
|
|
that data.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rbal1recovsupp.htm">Recovery support for a distributed relational database</a></strong><br />
|
||
|
|
Failures that can occur on a computer server are a server failure (when the entire server is not operating); a loss of the site due to fire, flood, or similar catastrophe; or the damage or loss of an object. For a distributed relational database, a failure on one server in the network prevents users across the entire network from accessing the relational database on that server.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbal1netredund.htm">Network redundancy considerations for a distributed relational database</a></strong><br />
|
||
|
|
Network redundancy provides different ways for users on the distributed relational database network to access a relational database on the network.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbal1dataredund.htm">Data redundancy in your distributed relational database network</a></strong><br />
|
||
|
|
Data redundancy in a distributed relational database also provides different ways for users on the distributed relational database network to access a database on the network.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbal1kickoff.htm" title="Distributed database programming describes the distributed relational database management portion of the i5/OS licensed program. Distributed relational database management provides applications with access to data that is external to the applications and typically located across a network of computers.">Distributed database programming</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|