ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzam4_5.4.0.1/rzam4disk.htm

102 lines
7.2 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="concept" />
<meta name="DC.Title" content="Disk" />
<meta name="abstract" content="This topic describes how disk storage on the iSeries works and describes how it can be configured and used for different storage purposes." />
<meta name="description" content="This topic describes how disk storage on the iSeries works and describes how it can be configured and used for different storage purposes." />
<meta name="DC.Relation" scheme="URI" content="rzam4overview.htm" />
<meta name="DC.Relation" scheme="URI" content="../rzaly/rzalyaspsovrvw.htm" />
<meta name="DC.Relation" scheme="URI" content="../rzaly/rzalyoptimize.htm" />
<meta name="DC.Relation" scheme="URI" content="../rzaly/rzalyoverview.htm" />
<meta name="DC.Relation" scheme="URI" content="../rzaly/rzalyprtctvsdtalss.htm" />
<meta name="DC.Relation" scheme="URI" content="http://www.ibm.com/servers/eserver/iseries/hsmcomp/index.html" />
<meta name="copyright" content="(C) Copyright IBM Corporation 2004, 2006" />
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2004, 2006" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="rzam4disk" />
<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>Disk</title>
</head>
<body id="rzam4disk"><a name="rzam4disk"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Disk</h1>
<div><p>This topic describes how disk storage on the iSeries™ works
and describes how it can be configured and used for different storage purposes.</p>
<p>Disk storage is the storage that is usually internal to your iSeries server;
however, it can also be attached externally to it. You can group your disk
drives into logical subsets called <dfn class="term">disk pools</dfn> (also known as
auxiliary storage pools or ASPs). One reason to do this is to provide a level
of protection for your data. If one disk unit fails, you only have to recover
the data stored in the disk pool that the failed disk unit was a part of.</p>
<p>Disk pools also enable you to set disk space aside for a particular purpose,
application, or data type. For example, you may create a disk pool for backups
done to save files. You can then move these save files to tape or other media
when it is convenient for you. The following diagram shows a disk pool that
is composed of disk units 1, 4, 5, 7, and 11.</p>
<br /><img src="rzam4502.gif" alt="A disk pool on the iSeries server" /><br /><p>For detailed information about disk pools, disk pool types, and examples
of how to use disk pools for different purposes, see Disk pools. For information
about how to configure disk units and disk pools, see Manage disk pools.</p>
<p><dfn class="term">Independent disk pools</dfn> are disk pools that can be brought
online or taken offline without any dependencies on the rest of the storage
on a system. This is possible because all of the necessary system information
associated with the independent disk pool is contained within the independent
disk pool. Independent disk pools offer a number of availability and performance
advantages in both single and multiple system environments. For detailed information,
see Using independent disk pools.</p>
<p>Besides disk pools, there are a few other ways to protect your disk units
and the data on them. <dfn class="term">Mirrored protection</dfn> protects your data
by keeping a copy of the data on two separate disk units. When a disk-related
component fails, the system may continue to operate without interruption by
using the mirrored copy of the data until the failed component is repaired.
<dfn class="term">Device parity protection</dfn> is a hardware function that enables
your server to reconstruct data in the event of a disk failure. It is important
to remember that these disk protection methods are not a guarantee against
failure or data loss. You still need to have a good backup and recovery strategy
in place in order to truly protect your data. For detailed information about
the disk protection methods described here, see Plan for disk protection.</p>
<p>Compared to tape or optical, disk is a more expensive storage option. However,
the data on disk is more quickly accessible than on tape or optical. It is
important to balance the cost of storing data on disk with the speed and convenience
with which you can access that data. For example, if you have older data that
you access infrequently, you may want to consider storing it on tape or optical,
rather than on disk. Likewise, current information that you access frequently
might be worth the cost of disk storage because you can access it quickly.
This type of storage strategy is called <dfn class="term">hierarchical storage management</dfn>.
The following diagram shows the different layers of hierarchical storage management:</p>
<br /><img src="rzam4503.gif" alt="Hierarchical storage management" /><br /><p>It is not always the same data that resides in the high performance storage
components. Data is moved among the different layers according to the current
system needs. The key to successful and seamless hierarchical storage management
lies in the management and distribution of data across the different layers.
For detailed information, see Hierarchical Storage Management.</p>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzam4overview.htm" title="As your company produces a greater volume of information, and as the value of that information grows, the methods you use to protect and preserve it become vital corporate strategies. Storage has gone from being a feature of a server to being an entity unto itself.">Storage solutions</a></div>
</div>
<div class="relconcepts"><strong>Related concepts</strong><br />
<div><a href="../rzaly/rzalyaspsovrvw.htm">Disk pools</a></div>
<div><a href="../rzaly/rzalyoverview.htm">Using independent disk pools</a></div>
<div><a href="../rzaly/rzalyprtctvsdtalss.htm">Plan for disk protection</a></div>
</div>
<div class="reltasks"><strong>Related tasks</strong><br />
<div><a href="../rzaly/rzalyoptimize.htm">Manage disk pools</a></div>
</div>
<div class="relinfo"><strong>Related information</strong><br />
<div><a href="http://www.ibm.com/servers/eserver/iseries/hsmcomp/index.html" target="_blank">Hierarchical storage management</a></div>
</div>
</div>
</body>
</html>