71 lines
5.0 KiB
HTML
71 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="concept" />
|
||
|
|
<meta name="DC.Title" content="Reduce the time to vary on independent disk pool" />
|
||
|
|
<meta name="abstract" content="When unplanned outages occur, data stored within independent disk pools is unavailable until they can be restarted. To ensure that the restart occurs quickly and efficiently, you should use recommended strategies for varying on your independent disk pools." />
|
||
|
|
<meta name="description" content="When unplanned outages occur, data stored within independent disk pools is unavailable until they can be restarted. To ensure that the restart occurs quickly and efficiently, you should use recommended strategies for varying on your independent disk pools." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzalwshorten_unplanned.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="rzalwvaryiasp" />
|
||
|
|
<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>Reduce the time to vary on independent disk pool</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzalwvaryiasp"><a name="rzalwvaryiasp"><!-- --></a>
|
||
|
|
<img src="./delta.gif" alt="Start of change" /><!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Reduce the time to vary on independent disk pool</h1>
|
||
|
|
<div><p>When unplanned outages occur, data stored within independent disk
|
||
|
|
pools is unavailable until they can be restarted. To ensure that the restart
|
||
|
|
occurs quickly and efficiently, you should use recommended strategies for
|
||
|
|
varying on your independent disk pools. </p>
|
||
|
|
<p>These strategies provide a means of reducing the vary on time for independent
|
||
|
|
disk pools.</p>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Synchronize user profile name, UID, and GID</h4></div>
|
||
|
|
<div class="section"><p>In a clustered environment, a user profile is considered to
|
||
|
|
be the same across servers if the profile names are the same. The name is
|
||
|
|
the unique identifier in the cluster. However, a user profile also contains
|
||
|
|
a user identification number (UID) and group identification number (GID).
|
||
|
|
To reduce the amount of internal processing that occurs during a switchover,
|
||
|
|
where the independent disk pool is made unavailable on one server and then
|
||
|
|
made available on a different server, the UID and GID values should be synchronized
|
||
|
|
across the recovery domain for the device CRG.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Use recommended structure for independent disk pools</h4><p>The recommended structure for using independent disk pools is
|
||
|
|
to place the majority of your application data objects into independent disk
|
||
|
|
pools and a minimal number of nonprogram objects in SYSBAS, which is the
|
||
|
|
system disk pool and all configured basic disk pools. The system disk pool
|
||
|
|
and basic user disk pools (SYSBAS) would contain primarily operating system
|
||
|
|
objects, licensed program libraries, and few user libraries. This structure
|
||
|
|
yields the best possible protection and performance. Application data is
|
||
|
|
isolated from unrelated faults and can also be processed independently of
|
||
|
|
other system activity. Vary on and switchover times are optimized with this
|
||
|
|
structure.</p>
|
||
|
|
<p>This recommended structure does not exclude other configurations.
|
||
|
|
For example, you might start by migrating only a small portion of your data
|
||
|
|
to a disk pool group and keeping the bulk of your data in SYSBAS. This is
|
||
|
|
certainly supported. However, you should expect longer vary-on and switchover
|
||
|
|
times with this configuration since additional processing is required to
|
||
|
|
merge database cross-reference information into the disk pool group. </p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzalwshorten_unplanned.htm" title="Unplanned outages do occur, and a key to availability is to ensure that when they do occur you can recover from them as quickly as possible.">Shorten unplanned outages</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<img src="./deltaend.gif" alt="End of change" /></body>
|
||
|
|
</html>
|