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

223 lines
14 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="topic" />
<meta name="DC.Title" content="Configure geographic mirroring with dedicated independent disk pools" />
<meta name="DC.Relation" scheme="URI" content="rzalyconfigure.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="rzalyconfiguregeographic" />
<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>Configure geographic mirroring with dedicated independent disk pools</title>
</head>
<body id="rzalyconfiguregeographic"><a name="rzalyconfiguregeographic"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Configure geographic mirroring with dedicated independent disk pools</h1>
<div><p>To configure geographic mirroring, you must
first configure your cross-site mirroring (XSM) environment and create the
independent disk pool that you want to mirror. This includes defining your
primary and backup nodes within the recovery domain. Before using iSeries™ Navigator,
you should also define at least one and as many as four data port TCP/IP addresses,
which would constitute one or more one-to-one bidirectional routes as part
of the connection between the production copy nodes and the mirror copy nodes.
Geographic mirroring will allow you to maintain an exact copy of the independent
disk pool on a system at a different location for protection and availability
purposes. </p>
<p>The following figure shows an example configuration for geographic mirroring.
Primary Node A in New York City is the source system for the production copy
of the independent disk pool that is dedicated to Node A. Node B is the backup
system in Boston that is the target node for the mirror copy of the independent
disk pool that is dedicated to Node B.</p>
<img src="rzaly508.gif" alt="This is an example shows the configuration for geographic mirroring." /><div class="section"><h4 class="sectiontitle">Configured geographic mirroring</h4><p><a href="rzalycommunications.htm">Communications requirements</a></p>
<p><a href="../rzai2/rzai2custom.htm">Customize TCP/IP
with iSeries Navigator</a></p>
<p>To
configure your geographic mirroring with the iSeries Navigator, follow these steps:</p>
<div class="p"><ol><li>Plan and configure your data port TCP/IP routes.</li>
<li><a href="rzalycreatecluster.htm">Create a cluster</a>. </li>
<li><a href="rzalycreatediskpool.htm">Create the independent
disk pool </a> that you want to mirror.</li>
<li>Create the device cluster resource group, also known as switchable hardware
group, for the independent disk pool that you just created:<ol type="a"><li>In iSeries Navigator,
expand <span class="uicontrol">Management Central</span>. </li>
<li>Expand <span class="uicontrol">Clusters</span>. </li>
<li>Expand the cluster for which you need to add a switchable hardware group.
</li>
<li>Right-click <span class="uicontrol">Switchable Hardware</span>, and select <span class="uicontrol">New
Group</span>. </li>
<li>On the Create new or add existing disk pool dialog box, select <span class="uicontrol">No,
add an existing switchable disk pool to the switchable hardware group</span>.</li>
</ol>
</li>
<li>Define your geographic mirroring sites in the recovery domain:<ol type="a"><li>Right-click the newly created switchable hardware group and select <span class="uicontrol">Properties</span>.</li>
<li>Select the <span class="uicontrol">Recovery Domain</span> tab.</li>
<li>Select the primary node and click <span class="uicontrol">Edit</span>.</li>
<li><img src="./delta.gif" alt="Start of change" />In the site name field, specify the primary site for the
production copy. Since this example contains two nodes, each of the nodes
must have a different site name, with one node per site. In environments
with more that two nodes, the site with more than one node must have an independent
disk pool in either a hardware tower or IOP which can be switched between
nodes within the same site, In this case, nodes within that site would have
the same site name.<div class="note"><span class="notetitle">Note:</span> The site name for the production and
mirror copy can not be the same.</div>
<img src="./deltaend.gif" alt="End of change" /></li>
<li>Click <span class="uicontrol">Add</span> to specify the data port IP addresses
of the primary node.</li>
<li>On the Edit Node dialog, specify the data port IP addresses for the primary
node that you setup in step 1, Plan and configure your TCP/IP, and click <span class="uicontrol">OK</span>. You can configure up to four
data port IP addresses in a one-to-one manner, one port to one port, each
port independent of the other. You should consider configuring multiple communication
lines to allow for redundancy and the highest throughput. The same number
of ports used here should be configured on the mirroring node. </li>
<li>On the General tab, click <span class="uicontrol">OK</span>.</li>
<li>Repeat the previous steps to specify the site name and IP addresses for
the mirror copy node.</li>
</ol>
</li>
<li>After you have completed the XSM prerequisites, follow these steps to
configure geographic mirroring: <ol type="a"><li>In iSeries Navigator,
expand <span class="uicontrol">My Connections</span> (or your active environment).</li>
<li>Expand the primary node on the source iSeries server.</li>
<li>Expand <span class="uicontrol">Configuration and Service</span>&gt;<span class="uicontrol">Hardware</span>&gt;<span class="uicontrol">Disk
Units</span>&gt;<span class="uicontrol">Disk Pools</span>.</li>
<li>If the Geographic Mirroring columns are not
displayed, click the Disk Pool you want to mirror, and select <span class="uicontrol">View</span>&gt;<span class="uicontrol">Customize
this view</span>&gt;<span class="uicontrol">Columns</span>, then select the columns
with the suffix Geographic Mirroring from the <span class="uicontrol">Columns available
to display list</span>.</li>
<li>Right-click the Disk Pool you want to mirror, and select <span class="uicontrol">Geographic
Mirroring&gt; Configure Geographic Mirroring</span>.</li>
<li>Follow the wizard's instructions to configure geographic mirroring.<div class="note"><span class="notetitle">Note:</span> The
disk pools you select to geographically mirror must be in the same switchable
hardware group. If you want to geographically mirror disk pools in more than
one switchable hardware group, you need to complete the wizard one time for
each switchable hardware group.</div>
</li>
</ol>
</li>
<li>You have now configured geographic mirroring. The remaining steps are
required to prepare the independent disk pool for use in this environment.
See <a href="rzalyprintgraphview.htm">Print your disk configuration</a>. Print your
disk configuration to have in case a recovery situation occurs. Also, record
the relationship between the independent disk pool name and number. </li>
</ol>
<ol><li><a href="rzalystartcrg.htm">Start switchable hardware group</a>. Start the switchable
hardware group to enable device resiliency for the switchable hardware group.</li>
<li><a href="rzalymakediskpoolavailable.htm">Make a disk pool available</a>. To
access the disk units in an independent disk pool you must make the disk
pool available (vary on) the disk pool.</li>
<li>Wait for resync to complete. </li>
<li><a href="../rzaig/rzaigmanageperformswitchover.htm">Perform
a test switchover</a>. Before you add data to the disk pool, perform a
test switchover to ensure the backup node can become the primary node and
the primary node can become the backup node. </li>
</ol>
<div class="note"><span class="notetitle">Note:</span> If you remove a node from a device domain after you configure geographic
mirroring, the removed node takes any production copies or mirror copies that
it owns. These nodes are changed to nongeographic mirrored disk pools.</div>
</div>
</div>
<div class="section"><h4 class="sectiontitle">Using CL commands and APIs</h4><p>To configure your geographic
mirroring with the CL commands and APIs, follow these steps:</p>
<div class="p"><blockquote>You
can use CL commands and APIs for creating a switchable independent disk pool,
however there are some tasks that require that you use iSeries Navigator. <ol><li>Plan and configure your data port TCP/IP routes on all nodes in the recommended
manner as follows:<ul><li>Node A should have routes to C and D.</li>
<li>Node B should have routes to C and D.</li>
<li>Node C should have routes to A and B.</li>
<li>Node D should have routes to A and B.</li>
</ul>
</li>
<li><strong>Create the cluster.</strong> Create the cluster with the nodes that you
want using the <a href="../cl/crtclu.htm">CRTCLU
(Create Cluster) command</a>. </li>
<li><span class="uicontrol">Start the nodes that comprise the
cluster.</span> Start the nodes in the cluster using the <a href="../cl/strclunod.htm">STRCLUNOD (Start Cluster Node) command</a></li>
<li><span class="uicontrol">Create the device domain.</span> You must create the device
domain for all nodes involved in switching an independent disk pool using
the <a href="../cl/adddevdmne.htm">ADDDEVDMNE
(Add Device Domain Entry) command</a>.</li>
<li><span class="uicontrol">Create the device descriptions.</span> Device descriptions
must be created on each node that will be in the cluster resource group (CRG).
Use the <a href="../cl/crtdevasp.htm">CRTDEVASP
(Create Device Description (ASP)) command</a>. On the command line in the
character-based interface, enter CRTDEVASP. In the <span class="uicontrol">Resource Name</span> and
the <span class="uicontrol">Device Description</span> fields, enter the name of the
independent disk pool you plan to create. </li>
<li><span class="uicontrol">Create the cluster resource group.</span> Create the device
CRG with the nodes, their roles in the recovery domain, and the independent
disk pool device descriptions. You must also specify a site name and data
port IP addresses for each node in the recovery domain. Use the <a href="../cl/crtcrg.htm">CRTCRG (Create Cluster Resource Group)
command</a>.</li>
<li><a href="rzalycreatediskpool.htm">Create a disk pool</a>. Create the
disk pool on the node that owns the disk units using the New Disk Pool wizard
when the server is fully restarted. Make sure clustering is active before
you start. Name the independent disk pool to match the device description
resource name that you gave in step 3. As you add disk units, it is best
to localize disk units in the same expansion unit or IOP. Also, do not spread
the disk pool across device parity sets <strong>(iSeries Navigator required)</strong>.</li>
<li>Follow these steps to configure geographic mirroring:<ol type="a"><li>In iSeries Navigator,
expand <span class="uicontrol">My Connections</span> (or your active environment).</li>
<li>Expand any iSeries server.</li>
<li>Expand <span class="uicontrol">Configuration and Service</span>.</li>
<li>Expand <span class="uicontrol">Hardware</span>.</li>
<li>Expand <span class="uicontrol">Disk Units</span>.</li>
<li>Expand <span class="uicontrol">Disk Pools</span>.</li>
<li>Right-click the Disk Pool you want to mirror and select <span class="uicontrol">Geographic
Mirroring</span> &gt; C<span class="uicontrol">onfigure Geographic Mirroring</span>.</li>
<li>Follow the wizard's instructions to configure geographic mirroring.<div class="note"><span class="notetitle">Note:</span> The
disk pools you select to geographically mirror must be in the same switchable
hardware group. If you want to geographically mirror disk pools in more than
one switchable hardware group, you will need to complete the wizard one time
for each switchable hardware group.</div>
</li>
</ol>
</li>
<li><span class="uicontrol">Print your disk configuration</span>. Print your disk
configuration to have in case of a recovery situation. See How to display
your disk configuration in <a href="../books/sc415304.pdf">Backup and Recovery</a>. <img src="wbpdf.gif" alt="Link to PDF" /> Also, record the relationship between the independent
disk pool name and number. <p>You have now configured geographic mirroring.
The remaining steps are required to prepare the independent disk pool for
use in this environment. </p>
</li>
</ol>
<p>You have now configured geographic mirroring. The remaining steps
are required to prepare the independent disk pool for use in this environment.</p>
<ol><li><span class="uicontrol">Start the cluster resource group</span>.
Start the cluster resource group to enable device resiliency using the <a href="../cl/strcrg.htm">STRCRG (Start Cluster
Resource Group) command</a>. </li>
<li><span class="uicontrol">Make the disk pool available</span>.
To access the disk units in an independent disk pool you must vary on the
disk pool using the <a href="../cl/vrycfg.htm">VRYCFG
(Vary Configuration) command</a>. Vary on will also reconnect connections,
so that any new route definitions can take effect.</li>
<li><span class="uicontrol">Perform a test switchover</span>. Before you add data
to the disk pool, perform a test switchover to ensure the backup node can
become the primary node and the primary node can become the backup node. Use
the <a href="../cl/chgcrgpri.htm">CHGCRGPRI
(Change CRG Primary)</a> command.</li>
</ol>
</blockquote>
</div>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzalyconfigure.htm">Configure independent disk pools</a></div>
</div>
</div>
</body>
</html>