170 lines
11 KiB
HTML
170 lines
11 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 resilience solutions for i5/OS Clusters" />
|
||
<meta name="abstract" content="This topic provides an overview of different data resilience technologies that can be used to with i5/OS Clusters to enhance high availability in multiple system environments." />
|
||
<meta name="description" content="This topic provides an overview of different data resilience technologies that can be used to with i5/OS Clusters to enhance high availability in multiple system environments." />
|
||
<meta name="DC.Relation" scheme="URI" content="rzalwoverview.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="rzalwcompsolutions" />
|
||
<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 resilience solutions for i5/OS Clusters</title>
|
||
</head>
|
||
<body id="rzalwcompsolutions"><a name="rzalwcompsolutions"><!-- --></a>
|
||
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
<h1 class="topictitle1">Data resilience solutions for i5/OS Clusters</h1>
|
||
<div><p>This topic provides an overview of different data
|
||
resilience technologies that can be used to with i5/OS™ Clusters to enhance high availability
|
||
in multiple system environments. </p>
|
||
<p><dfn class="term">Data resilience</dfn> is the ability for the data to remain accessible
|
||
to the application even if the system that originally hosted the data fails.
|
||
Choosing the correct set of data resilience 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 alone or with clusters 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. </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 i5/OS High Availability
|
||
Clusters</a>. The section called "Comparison characteristics" contains
|
||
a detailed comparison of the attributes for each of these technologies. </p>
|
||
<div class="section"><h4 class="sectiontitle">Replication</h4><p>With replication, changes to an object
|
||
are copied to a saved version with near real-time accuracy. Replication is
|
||
one of the most widely used high availability solutions in multiple system
|
||
environments. On the iSeries™, this solution is most often implemented
|
||
through a business partner.</p>
|
||
<div class="p">Consider replication when you have the following
|
||
requirements:<ul><li>You need two or more copies of the data.</li>
|
||
<li>You want concurrent access to the second copy of data. </li>
|
||
<li>You need backup window reduction. </li>
|
||
<li>You need to selectively replicate objects within a library or directory.
|
||
</li>
|
||
<li>Your IT staff can monitor the state of the replication environment. </li>
|
||
<li>You need geographic dispersion between copies, especially if they need
|
||
distances greater than what can be achieved by hardware solutions. </li>
|
||
<li>You already have deployed a solution using logical object replication.
|
||
</li>
|
||
<li>You need a solution that has no special hardware configuration requirements.</li>
|
||
<li> Failover and switchover times should not exceed tens of minutes. </li>
|
||
<li>Transaction level integrity is important for all journaled objects.</li>
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
<div class="section"><h4 class="sectiontitle">Switchable disk pools</h4><p>Switchable disk pools are
|
||
storage devices on the operating system that are independent of a particular
|
||
system. This allows you to "switch" disk pools from one system to another
|
||
without performing a full IPL. The key benefits to switchable disk pools involve
|
||
its simple design and maintenance. One copy of the data is always current
|
||
with no other version to synchronize so there is minimal administration. </p>
|
||
<div class="p">Consider
|
||
switchable disk pools when you have the following requirements:<ul><li>Only one copy of the data with hardware protection satisfies your requirement
|
||
and you have considered or addressed avoiding unplanned outages due to disk
|
||
subsystem failures. </li>
|
||
<li>You need a simple, low cost and low maintenance solution. </li>
|
||
<li>Disaster recovery (DR) is not needed. </li>
|
||
<li>You only need coverage for planned outages and certain types of unplanned
|
||
outages. </li>
|
||
<li>The source and target system are at the same site. </li>
|
||
<li>You want consistent failover and switchover times within minutes and that
|
||
do not depend on transaction volumes. </li>
|
||
<li>Transaction-level integrity is important for all objects. </li>
|
||
<li>You need immediate availability of all object changes with no loss of
|
||
in flight data. </li>
|
||
<li>Objects not within an independent disk pool either do not need to be replicated
|
||
or are handled via some other mechanism. </li>
|
||
<li>You need the highest throughput environment. </li>
|
||
<li>Your environment calls for multiple, independent databases that can be
|
||
moved between systems.</li>
|
||
</ul>
|
||
</div>
|
||
</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.
|
||
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>
|
||
<div class="p">Consider cross-site mirroring when you have the following
|
||
requirements:<ul><li>You want a system-generated second copy of the data (at an IASP level).
|
||
</li>
|
||
<li>You need two copies of data, but do not need concurrent access to a second
|
||
copy. </li>
|
||
<li>A relatively low cost and low maintenance solution is desired, but you
|
||
also need disaster recovery. </li>
|
||
<li>Geographic dispersion between copies is needed, but your distance requirement
|
||
does not adversely impact your acceptable production performance goals. </li>
|
||
<li>You want consistent failover and switchover times within minutes and that
|
||
do not depend on transaction volumes. </li>
|
||
<li>Transaction-level integrity is important for all objects. </li>
|
||
<li>You need immediate availability of all object changes with no loss of
|
||
in flight data. </li>
|
||
<li>Objects not within an independent disk pool either do not need to be replicated
|
||
or are handled via some other mechanism. </li>
|
||
<li>The second copy that is not available during resynchronization fits within
|
||
your service level objectives. </li>
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
<div class="section"><h4 class="sectiontitle">IBM TotalStorage<sup>®</sup> Enterprise Storage Server<sup>®</sup> PPRC
|
||
used with the iSeries Copy Services for ESS toolkit </h4><p>This solution
|
||
involves the replication of data at the storage controller level to a second
|
||
storage system using IBM TotalStorage Enterprise Storage Server (ESS)
|
||
copy services. An independent disk pool is the basic unit of storage for the
|
||
ESS peer-to-peer remote copy (PPRC) function. PPRC generates a second copy
|
||
of the independent disk pool on another ESS. The toolkit comes as part of
|
||
the iSeries Copy Services for ESS services offering. It provides a set of
|
||
functions to combine the PPRC, IASP, and i5/OS cluster services for coordinated
|
||
switchover and failover processing through a cluster resource group.</p>
|
||
<p>This
|
||
solution provides the benefit of the remote copy function and coordinated
|
||
switching operations, which gives you good data resiliency capability if the
|
||
replication is done synchronously. The toolkit enables you to attach the second
|
||
copy to a backup system without an IPL. No load source recovery is involved
|
||
in the operations. You also have the ability to combine this solution with
|
||
other ESS-based copy services functions, such as FlashCopy, for additional
|
||
benefits such as save window reduction. </p>
|
||
<div class="p">Consider IBM TotalStorage Enterprise
|
||
Storage Server (ESS) peer-to-peer remote copy (PPRC) with IASP and Toolkit
|
||
when you have the following requirements: <ul><li>You desire a storage-based solution for DR, especially if multiple platforms
|
||
are involved. </li>
|
||
<li>You do not need complete high availability (HA), but seek to cover Disaster
|
||
recovery and some planned outages for critical application data. </li>
|
||
<li><img src="./delta.gif" alt="Start of change" />You want consistent failover and switchover times within minutes
|
||
and that do not depend on transaction volumes. <img src="./deltaend.gif" alt="End of change" /></li>
|
||
<li>You want two copies of data, but do not need concurrent access to a second
|
||
copy. </li>
|
||
<li>Geographic dispersion between copies is needed, but your distance requirement
|
||
does not adversely impact your acceptable production performance goals. Alternatively,
|
||
consider Peer-to-Peer Remote Copy (PPRC) Global Mirror, which is also known
|
||
as asynchronous PPRC. </li>
|
||
<li>Transaction-level integrity is important for all objects. </li>
|
||
<li>You need availability of all object changes with no loss of in-flight
|
||
data.</li>
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div>
|
||
<div class="familylinks">
|
||
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzalwoverview.htm" title="In today's fast-paced Internet environment, it is crucial that your data and applications be available to you when you need them. If your customers cannot access your Web site because your system is down, they may go to your competitors instead.">Availability roadmap</a></div>
|
||
</div>
|
||
</div>
|
||
</body>
|
||
</html> |