69 lines
5.4 KiB
HTML
69 lines
5.4 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 recovery after disk failures for distributed relational databases" />
|
|
<meta name="abstract" content="Recovery is not possible for recently entered data if a disk failure occurs and all objects are not saved on tape or disk immediately before the failure. After previously saved objects are restored, the server is operational, but the database is not current." />
|
|
<meta name="description" content="Recovery is not possible for recently entered data if a disk failure occurs and all objects are not saved on tape or disk immediately before the failure. After previously saved objects are restored, the server is operational, but the database is not current." />
|
|
<meta name="DC.subject" content="database recovery, disk failures, recovery" />
|
|
<meta name="keywords" content="database recovery, disk failures, recovery" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1recovsupp.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1auxstore.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1checksum.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1mirrored.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="../rzahg/rzahgbackup.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="rbal1datarecov" />
|
|
<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 recovery after disk failures for distributed relational databases</title>
|
|
</head>
|
|
<body id="rbal1datarecov"><a name="rbal1datarecov"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Data recovery after disk failures for distributed relational databases</h1>
|
|
<div><p>Recovery is not possible for recently entered data if a disk failure
|
|
occurs and all objects are not saved on tape or disk immediately before the
|
|
failure. After previously saved objects are restored, the server is operational,
|
|
but the database is not current.</p>
|
|
<p>Auxiliary storage pools (ASPs), checksum protection, and mirrored protection
|
|
are <span class="keyword">i5/OS™</span> disk recovery
|
|
functions that provide methods to recover recently entered data after a disk-related
|
|
failure. These functions use additional server resources, but provide a high
|
|
level of protection for servers in a distributed relational database. Because
|
|
some servers might be more critical as application servers than others, the
|
|
distributed relational database administrator should review how these disk
|
|
data protection methods can be best used by individual servers
|
|
within the network.</p>
|
|
</div>
|
|
<div>
|
|
<ul class="ullinks">
|
|
<li class="ulchildlink"><strong><a href="rbal1auxstore.htm">Auxiliary storage pools</a></strong><br />
|
|
An auxiliary storage pool (ASP) is one or more physical disk units assigned to the same storage area. ASPs allow you to isolate certain types of objects on specified physical disk units.</li>
|
|
<li class="ulchildlink"><strong><a href="rbal1checksum.htm">Checksum protection in a distributed relational database</a></strong><br />
|
|
Checksum protection guards against data loss on any disk in an auxiliary storage pool (ASP).</li>
|
|
<li class="ulchildlink"><strong><a href="rbal1mirrored.htm">Mirrored protection for a distributed relational database</a></strong><br />
|
|
Mirrored protection increases the availability of a server by duplicating different disk-related hardware components, such as a disk controller, a disk I/O processor, or a bus. The server can remain available after a failure, and service for the failed hardware components can be scheduled at a convenient time.</li>
|
|
</ul>
|
|
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbal1recovsupp.htm" title="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.">Recovery support for a distributed relational database</a></div>
|
|
</div>
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
|
<div><a href="../rzahg/rzahgbackup.htm">Backup and recovery</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |