ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzaly_5.4.0.1/rzalyremote.htm

82 lines
5.0 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="topic" />
<meta name="DC.Title" content="Remote disk unit mirroring support" />
<meta name="DC.Relation" scheme="URI" content="rzalydpconcepts.htm" />
<meta name="DC.Relation" scheme="URI" content="rzalyremoteload.htm" />
<meta name="DC.Relation" scheme="URI" content="rzalyremoteadv.htm" />
<meta name="DC.Relation" scheme="URI" content="rzalyremotedis.htm" />
<meta name="DC.Relation" scheme="URI" content="rzalycompmir.htm" />
<meta name="copyright" content="(C) Copyright IBM Corporation 2002, 2006" />
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2002, 2006" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="hdrremote" />
<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>Remote disk unit mirroring support</title>
</head>
<body id="hdrremote"><a name="hdrremote"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Remote disk unit mirroring support</h1>
<div><p>Standard disk unit mirroring support requires that both disk units of the
load source mirrored pair (unit 1) are attached to load source IOP. This allows
the system to IPL from either load source in the mirrored pair and allows
the system to dump main storage to either load source if the system ends abnormally.
However, since both load sources must be attached to the same
IOP, the best mirroring protection possible for the load source mirrored pair
is IOA-level protection. To provide a higher level of protection for your
system, you can use remote load source mirroring and remote disk unit mirroring.</p>
<p>Remote disk unit mirroring support, when combined with remote load source
mirroring, mirrors the disk unit on local optical buses with the disk unit
on optical buses that terminates at a remote location. In this configuration,
the entire system, including the load source, can be protected from a site
disaster. If the remote site is lost, the system can continue to run on the
disk unit at the local site. If the local disk unit and system unit are lost,
a new system unit can be attached to the set of disk units at the remote site,
and system processing can be resumed.</p>
<p>Remote disk unit mirroring, like standard disk unit mirroring, supports
mixing device-parity-protected disk units in the same disk pool with mirrored
disk units; the device parity disk unit can be located at either the local
or the remote site. However, if a site disaster occurs at the site containing
the device parity disk unit, all data in the disk pools containing the device
parity disk unit is lost.</p>
<p>Remote mirroring support makes it possible to divide the disk units on
your system into a group of local disk units and a group of remote disk units.
The remote disk units are attached to one set of optical buses and the local
disk units to another set of buses. The local and remote disk units can by
physically separated from one another at different sites by extending the
appropriate optical buses to the remote site. The distance between the sites
is restricted by the distance that an optical bus may be extended.</p>
<p>If you decide that remote disk unit mirroring is needed for your system,
you need to <a href="rzalyremoteplan.htm">Prepare your system for remote mirroring</a> and then <a href="rzalyremotestart.htm">Start site-to-site mirroring</a>.</p>
</div>
<div>
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="rzalyremoteload.htm">Remote load source mirroring</a></strong><br />
</li>
<li class="ulchildlink"><strong><a href="rzalyremoteadv.htm">Advantages of remote disk unit mirroring</a></strong><br />
</li>
<li class="ulchildlink"><strong><a href="rzalyremotedis.htm">Disadvantages of remote loadsource disk unit mirroring for primary partitions on an IBM iSeries server</a></strong><br />
</li>
<li class="ulchildlink"><strong><a href="rzalycompmir.htm">Comparison of standard mirroring and remote mirroring</a></strong><br />
</li>
</ul>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzalydpconcepts.htm">Disk protection</a></div>
</div>
</div>
</body>
</html>