194 lines
12 KiB
HTML
194 lines
12 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="Comparison of logical replication, switched disks, and cross-site mirroring" />
|
|
<meta name="abstract" content="This topic provides an overview of different data resilience technologies that can be used with clusters to enhance high availability." />
|
|
<meta name="description" content="This topic provides an overview of different data resilience technologies that can be used with clusters to enhance high availability." />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaigplandataresilience.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="rzaigconceptsreplicationvsswitchable" />
|
|
<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>Comparison of logical replication, switched disks, and cross-site mirroring</title>
|
|
</head>
|
|
<body id="rzaigconceptsreplicationvsswitchable"><a name="rzaigconceptsreplicationvsswitchable"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Comparison of logical replication, switched disks, and cross-site mirroring</h1>
|
|
<div><p><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></p>
|
|
<p><img src="./delta.gif" alt="Start of change" /><dfn class="term">Data resiliency</dfn> allows data to remain available
|
|
to applications and users even though the system that originally hosted the
|
|
data fails. Choosing the correct set of data resiliency technologies in the
|
|
context of your overall business continuity strategy can be complex and difficult.
|
|
It's important to understand the different data resilience solutions that
|
|
can be used to enhance availability in multiple system environments. You can
|
|
either choose a single solution or use a combination of these technologies
|
|
to meet your needs.<img src="./deltaend.gif" alt="End of change" /></p>
|
|
<p>For more details on these solutions, see <a href="http://publib-b.boulder.ibm.com/abstracts/redp0888.html?Open" target="_blank">Data Resilience Solutions for IBM<sup>®</sup> i5/OS™ High Availability Clusters</a>.
|
|
The section called "Data Resilience Solutions for IBM i5/OS High Availability Clusters" contains
|
|
a detailed comparison of the attributes for each of these technologies. </p>
|
|
<div class="section"><h4 class="sectiontitle">Logical replication</h4><p><dfn class="term">Logical replication</dfn> is
|
|
the process of copying objects from one node in a cluster to one or more other
|
|
nodes in the cluster, which makes the objects on all the systems identical. </p>
|
|
<p>A
|
|
replicated resource allows for objects, such as an application and its data,
|
|
to be copied from one node in the cluster to one or more other nodes in the
|
|
cluster. This process keeps the objects on all servers in the resource's recovery
|
|
domain identical. If you make a change to an object on one node in a cluster,
|
|
the change is replicated to other nodes in the cluster. Then, should a failover
|
|
or switchover occur, the backup node can seamlessly take on the role of the
|
|
primary node. The server or servers that act as backups are defined in the
|
|
recovery domain. When an outage occurs on the server defined as the primary
|
|
node in the recovery domain and a switchover or failover is initiated, the
|
|
node designated as the backup in the recovery domain becomes the primary access
|
|
point for the resource.</p>
|
|
<p>Replication requires the use of either a custom-written
|
|
application or a software application written by a cluster middleware business
|
|
partner. See <a href="rzaigplanreplication.htm">Plan
|
|
for logical replication</a> for details.</p>
|
|
</div>
|
|
<div class="section"><h4 class="sectiontitle">Switchable disks</h4><p><dfn class="term">Switchable disks</dfn> enable
|
|
the resources, such as data and applications, residing on an expansion unit
|
|
or on an input-output processor (IOP) on a shared bus or in an I/O Pool for
|
|
a logical partition, to be switched between a cluster's primary node and backup
|
|
node. This allows for a set of disk units to be accessed from a second server,
|
|
a server defined as a backup node in the cluster resource group's recovery
|
|
domain, when the server currently using those disk units experiences an outage
|
|
and a failover or switchover occurs. </p>
|
|
<p>Taking advantage of switchable
|
|
resources in your cluster requires the use of independent disk pools. See <a href="../rzaly/rzalyplan.htm">Plan for independent
|
|
disk pools</a> for more information.</p>
|
|
</div>
|
|
<div class="section"><h4 class="sectiontitle">Cross-site mirroring</h4><p><dfn class="term">Cross-site mirroring</dfn>,
|
|
combined with the geographic mirroring function, enables you to mirror data
|
|
on disks at sites that can be separated by a significant geographic distance.
|
|
This technology can be used to extend the functionality of a device cluster
|
|
resource group (CRG) beyond the limits of physical component connection. Geographic
|
|
mirroring provides the ability to replicate changes made to the production
|
|
copy of an independent disk pool to a mirror copy of that independent disk
|
|
pool. As data is written to the production copy of an independent disk pool,
|
|
the operating system mirrors that data to a second copy of the independent
|
|
disk pool through another system. This process keeps multiple identical copies
|
|
of the data. </p>
|
|
<p>Through the device CRG, should a failover or switchover
|
|
occur, the backup node can seamlessly take on the role of the primary node.
|
|
The server or servers that act as backups are defined in the recovery domain.
|
|
The backup nodes can be at the same or different physical location as the
|
|
primary. When an outage occurs on the server defined as the primary node in
|
|
the recovery domain and a switchover or failover is initiated, the node designated
|
|
as the backup in the recovery domain becomes the primary access point for
|
|
the resource and will then own the production copy of the independent disk
|
|
pool. Thus, you can gain protection from the single point of failure associated
|
|
with switchable resources.</p>
|
|
</div>
|
|
<div class="section">
|
|
<div class="tablenoborder"><img src="./delta.gif" alt="Start of change" /><a name="rzaigconceptsreplicationvsswitchable__table1"><!-- --></a><table cellpadding="4" cellspacing="0" summary="" id="rzaigconceptsreplicationvsswitchable__table1" frame="border" border="1" rules="all"><caption>Table 1. Comparison
|
|
of data resilient technologies that can be used with clusters. Learn
|
|
about characteristics of different data resiliency technologies to help you
|
|
determine the best solution for your cluster.</caption><thead align="left"><tr><th valign="top" class="firstcol" id="d0e88">Factor</th>
|
|
<th valign="top" id="d0e90">Replication</th>
|
|
<th valign="top" id="d0e92">Switchable disks</th>
|
|
<th valign="top" id="d0e94">Cross-site mirroring</th>
|
|
</tr>
|
|
</thead>
|
|
<tbody><tr><th valign="top" class="firstcol" id="d0e98" headers="d0e88 ">Flexibility</th>
|
|
<td valign="top" headers="d0e98 d0e90 ">10s of servers</td>
|
|
<td valign="top" headers="d0e98 d0e92 ">2 servers</td>
|
|
<td valign="top" headers="d0e98 d0e94 ">4 servers</td>
|
|
</tr>
|
|
<tr><th valign="top" class="firstcol" id="d0e107" headers="d0e88 ">Single point of failure</th>
|
|
<td valign="top" headers="d0e107 d0e90 ">None</td>
|
|
<td valign="top" headers="d0e107 d0e92 ">Disk subsystem</td>
|
|
<td valign="top" headers="d0e107 d0e94 ">None</td>
|
|
</tr>
|
|
<tr><th valign="top" class="firstcol" id="d0e116" headers="d0e88 ">Cost</th>
|
|
<td valign="top" headers="d0e116 d0e90 "><ul><li>Additional disk capacity required.</li>
|
|
<li>Business partner replication software.</li>
|
|
<li>Duplicate disks</li>
|
|
</ul>
|
|
</td>
|
|
<td valign="top" headers="d0e116 d0e92 "><ul><li>Switchable I/O expansion tower or IOP </li>
|
|
<li>Option 41</li>
|
|
</ul>
|
|
</td>
|
|
<td valign="top" headers="d0e116 d0e94 "><ul><li>Additional disk for mirror copy of independent disk pool </li>
|
|
<li>Optionally switchable I/O expansion unit </li>
|
|
<li>Option 41</li>
|
|
</ul>
|
|
</td>
|
|
</tr>
|
|
<tr><th valign="top" class="firstcol" id="d0e141" headers="d0e88 ">Performance</th>
|
|
<td valign="top" headers="d0e141 d0e90 ">Replication overhead</td>
|
|
<td valign="top" headers="d0e141 d0e92 ">Little impact</td>
|
|
<td valign="top" headers="d0e141 d0e94 ">Geographic mirroring overhead</td>
|
|
</tr>
|
|
<tr><th valign="top" class="firstcol" id="d0e150" headers="d0e88 ">Real time coverage</th>
|
|
<td valign="top" headers="d0e150 d0e90 ">Journaled objects</td>
|
|
<td valign="top" headers="d0e150 d0e92 ">Objects contained in independent disk pool</td>
|
|
<td valign="top" headers="d0e150 d0e94 ">Objects contained in independent disk pool</td>
|
|
</tr>
|
|
<tr><th valign="top" class="firstcol" id="d0e159" headers="d0e88 ">Geographic dispersion</th>
|
|
<td valign="top" headers="d0e159 d0e90 ">Limited by performance considerations</td>
|
|
<td valign="top" headers="d0e159 d0e92 ">Limited attach distance as servers and expansion units must be attached
|
|
to HSL OptiConnect loop (250 meters maximum)</td>
|
|
<td valign="top" headers="d0e159 d0e94 ">Limited by performance considerations (No limits are imposed by the
|
|
system. However, response time and throughput over selected communications
|
|
lines can dictate some practical limit.)</td>
|
|
</tr>
|
|
<tr><th valign="top" class="firstcol" id="d0e168" headers="d0e88 ">Disaster recovery protection</th>
|
|
<td valign="top" headers="d0e168 d0e90 ">Yes</td>
|
|
<td valign="top" headers="d0e168 d0e92 ">No</td>
|
|
<td valign="top" headers="d0e168 d0e94 ">Yes</td>
|
|
</tr>
|
|
<tr><th valign="top" class="firstcol" id="d0e177" headers="d0e88 ">Concurrent backup</th>
|
|
<td valign="top" headers="d0e177 d0e90 ">Yes</td>
|
|
<td valign="top" headers="d0e177 d0e92 ">No</td>
|
|
<td valign="top" headers="d0e177 d0e94 ">No</td>
|
|
</tr>
|
|
<tr><th valign="top" class="firstcol" id="d0e186" headers="d0e88 ">Setup</th>
|
|
<td valign="top" headers="d0e186 d0e90 "><ul><li>Replication environment. </li>
|
|
<li>Determining what to replicate.</li>
|
|
</ul>
|
|
</td>
|
|
<td valign="top" headers="d0e186 d0e92 "> <ul><li>Independent disk pool environment.</li>
|
|
<li>Populate independent disk pool</li>
|
|
</ul>
|
|
</td>
|
|
<td valign="top" headers="d0e186 d0e94 "> <ul><li>Independent disk pool environment (include setting up geographic mirroring) </li>
|
|
<li>Populate independent disk pool</li>
|
|
</ul>
|
|
</td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
<img src="./deltaend.gif" alt="End of change" /></div>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaigplandataresilience.htm" title="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.">Plan for data resilience</a></div>
|
|
</div>
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
|
<div><a href="rzaigplanreplication.htm" title="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.">Plan for logical replication</a></div>
|
|
<div><a href="rzaigplanswitcheddisks.htm" title="A single copy of the data is maintained on switchable hardware; either an expansion unit (tower) or an IOP in a logical partition environment.">Plan for switchable independent disk pools and cross-site mirroring (XSM)</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |