ibm-information-center/dist/eclipse/plugins/i5OS.ic.ddp_5.4.0.1/rbal1mirrored.htm

55 lines
4.1 KiB
HTML
Raw Normal View History

2024-04-02 14:02:31 +00:00
<?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="reference" />
<meta name="DC.Title" content="Mirrored protection for a distributed relational database" />
<meta name="abstract" content="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." />
<meta name="description" content="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." />
<meta name="DC.subject" content="database recovery, mirrored protection, recovery, disk failure, mirrored protection" />
<meta name="keywords" content="database recovery, mirrored protection, recovery, disk failure, mirrored protection" />
<meta name="DC.Relation" scheme="URI" content="rbal1datarecov.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="rbal1mirrored" />
<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>Mirrored protection for a distributed relational database</title>
</head>
<body id="rbal1mirrored"><a name="rbal1mirrored"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Mirrored protection for a distributed relational database</h1>
<div><p>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.</p>
<div class="section"><p>Different levels of mirrored protection provide different levels
of server availability. For example, if only the disk units on a server are
mirrored, all disk units have disk unit-level protection, so the server is
protected against the failure of a single disk unit. In this situation, if
a controller, I/O processor, or bus failure occurs, the server cannot run
until the failing part is repaired or replaced. All mirrored units on the
server must have identical disk unit-level protection and reside in the same
ASP. The units in an ASP are automatically paired by the server when mirrored
protection is started.</p>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbal1datarecov.htm" title="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.">Data recovery after disk failures for distributed relational databases</a></div>
</div>
</div>
</body>
</html>