ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzahq_5.4.0.1/rzahqstcco.htm

214 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 xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-us">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="dc.language" scheme="rfc1766" 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. -->
<meta name="dc.date" scheme="iso8601" content="2005-09-13" />
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
<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))' />
<title>Disk drives for integrated Windows servers</title>
<link rel="stylesheet" type="text/css" href="ibmidwb.css" />
<link rel="stylesheet" type="text/css" href="ic.css" />
</head>
<body>
<a id="Top_Of_Page" name="Top_Of_Page"></a><!-- Java sync-link -->
<script language = "Javascript" src = "../rzahg/synch.js" type="text/javascript"></script>
<a name="rzahqstcco"></a>
<h3 id="rzahqstcco">Disk drives for integrated Windows servers</h3>
<p>Integrated servers do not have their own disk drives. i5/OS&trade; creates network
server storage spaces within its own file system and integrated servers use
them as if they were normal hard disk drives.</p>
<p><img src="delta.gif" alt="Start of change" />For an integrated Windows server to recognize an integrated
server disk drive (network server storage space) as a hard disk drive, you
must link them together. You must create a disk drive before you can link
it. See <a href="rzahqcstpi.htm#rzahqcstpi">Create an integrated server disk drive</a> and <a href="rzahqlstpi.htm#rzahqlstpi">Link a disk drive to an integrated server</a>. After you
create and link a new integrated server disk drive, it appears as a new hard
disk drive to the integrated server. Then you must format it before you can
use it. See <a href="rzahqfstpi.htm#rzahqfstpi">Format integrated server disk drives</a>.<img src="deltaend.gif" alt="End of change" /></p>
<p>Disk drives can be linked to servers in one of the following ways:</p>
<ol type="1">
<li>Fixed (static) disk drive links allow disk drives to be linked to the
server using user specified link sequence positions. The order that the server
sees the drives is determined by the relative order of the link sequence positions.
The server must be varied off when adding a fixed (static) disk drive link.
<a name="wq281"></a>
<div class="notetitle" id="wq281">Note:</div><img src="delta.gif" alt="Start of change" />
<div class="notebody">Static drive links are not used for iSCSI attached xSeries&reg; servers.</div><img src="deltaend.gif" alt="End of change" /></li>
<li>A cluster quorum resource disk drive link is used to link the cluster
quorum resource disk drive to the servers in the cluster.</li>
<li>Cluster shared disk drive links allow a disk drive to be shared among
clustered integrated servers. A shared drive can only be linked to nodes that
share a common quorum resource drive. Drives of this type are available to
all nodes that are joined together by the links of the cluster quorum resource.
Each node has access to the shared drives under the control of Windows Cluster
services running on each node.
<p><span class="bold">Note:</span> Drives that
are linked as shared should be linked to ALL nodes that are clustered together.</p></li>
<li>Dynamic disk drive links allow additional disk drives to be linked to
an integrated server using dynamically assigned link sequence positions. The
disk link sequence position is assigned dynamically at the time that the disk
drive is linked to an active server. The disk link sequence position can be
specified, but it is not used until the server is restarted. The integrated
server can either be shut down or active when adding a dynamic disk drive
link.</li></ol>
<p><img src="delta.gif" alt="Start of change" />When a non-iSCSI integrated server is started, it sees the disk
drives in the following order:<img src="deltaend.gif" alt="End of change" /></p>
<ol type="1">
<li>Statically linked disk drives.</li>
<li>Cluster quorum resource disk drive.</li>
<li>Cluster shared disk drives.</li>
<li>Dynamically linked disk drives.</li></ol>
<p><img src="delta.gif" alt="Start of change" />For iSCSI attached servers, the cluster quorum disk appears
at the end of the list of disk drives. Dynamically linked disks and cluster
shared disks can be intermixed.<img src="deltaend.gif" alt="End of change" /></p>
<p>Within each of these link type categories, the disks appear in the order
of their user specified link sequence positions. When dynamically linking
a disk drive to an active server, the new disk drive appears following all
other linked disk drives.</p>
<p><img src="delta.gif" alt="Start of change" />The following table shows the iSeries&trade; virtual disk drive features supported
for various types of server network server descriptions (NWSDs) with i5/OS V5R4 or later.<img src="deltaend.gif" alt="End of change" /></p>
<p><img src="delta.gif" alt="Start of change" /><span class="bold">Disk features supported</span><img src="deltaend.gif" alt="End of change" /></p><img src="delta.gif" alt="Start of change" />
<a name="wq283"></a>
<table id="wq283" width="100%" summary="" border="1" frame="border" rules="all" class="singleborder">
<thead valign="bottom">
<tr class="tablemainheaderbar">
<th id="wq284" align="left" valign="top">Feature</th>
<th id="wq285" align="left" valign="top">NWSD type<sup>5</sup> *WINDOWSNT or
*IXSVR
<br />with OS type *WIN32</th>
<th id="wq286" align="left" valign="top">NWSD type<sup>5</sup> *ISCSI
<br />with
OS type *WIN32</th>
</tr>
</thead>
<tbody valign="top">
<tr>
<td align="left" valign="top" headers="wq284">Number of fixed (static) links</td>
<td align="left" valign="top" headers="wq285">16</td>
<td align="left" valign="top" headers="wq286">0</td>
</tr>
<tr>
<td headers="wq284">Number of dynamic links</td>
<td headers="wq285">16</td>
<td headers="wq286">63<sup>1</sup></td>
</tr>
<tr>
<td headers="wq284">Number of cluster quorum links</td>
<td headers="wq285">1</td>
<td headers="wq286">1</td>
</tr>
<tr>
<td headers="wq284">Number of cluster shared links</td>
<td headers="wq285">15</td>
<td headers="wq286">61<sup>1</sup></td>
</tr>
<tr>
<td headers="wq284">Maximum number of virtual disks that can be linked to
the server</td>
<td headers="wq285">48 with clustering<sup>2</sup>; 32
otherwise</td>
<td headers="wq286">64 with clustering<sup>2</sup>; 63
otherwise</td>
</tr>
<tr>
<td headers="wq284">Maximum capacity per virtual disk</td>
<td headers="wq285">1000 GB</td>
<td headers="wq286">1000 GB</td>
</tr>
<tr>
<td headers="wq284">Maximum total virtual disk capacity, assuming 1000 GB
per disk</td>
<td headers="wq285">46.9 TB with clustering<sup>2</sup>;
31.3 TB otherwise</td>
<td headers="wq286">62.5 TB with clustering<sup>2</sup>;
61.5 TB otherwise</td>
</tr>
<tr>
<td headers="wq284">Can link virtual disks while the server is active?</td>
<td headers="wq285">Yes
<br />Exceptions: fixed links</td>
<td headers="wq286">Yes
<br />Exceptions: dynamic links 1-2</td>
</tr>
<tr>
<td headers="wq284">Can unlink virtual disks while the server is active?</td>
<td headers="wq285">Yes
<br /><span><img src="delta.gif" alt="Start of change" />Exceptions: fixed links,
disk can not be part of a volume set, disk can not be a volume mounted in
a directory<img src="deltaend.gif" alt="End of change" /></span></td>
<td headers="wq286">Yes
<br /><span>Exceptions: dynamic links 1-2, disk
can not be part of a volume set, disk can not be a volume mounted in a directory </span></td>
</tr>
<tr>
<td headers="wq284">Virtual disk format types allowed when linking<sup>3</sup></td>
<td headers="wq285">*NTFS, *NTFSQR, *FAT, *FAT32, *OPEN</td>
<td headers="wq286">*NTFS, *NTFSQR, *FAT, *FAT32, *OPEN</td>
</tr>
<tr>
<td headers="wq284">Virtual disk access types allowed when linking</td>
<td headers="wq285">Exclusive update, shared update<sup>4</sup></td>
<td headers="wq286">Exclusive update, shared update<sup>4</sup></td>
</tr>
<tr>
<td headers="wq284">Disk links requiring exclusive update address type</td>
<td headers="wq285">All fixed disk links and all dynamic links</td>
<td headers="wq286">All dynamic links</td>
</tr>
<tr>
<td headers="wq284">Disk links requiring shared update address type</td>
<td headers="wq285">Cluster quorum link and all cluster shared disk links</td>
<td headers="wq286">Cluster quorum link and all cluster shared disk links</td>
</tr>
</tbody>
</table><img src="deltaend.gif" alt="End of change" />
<a name="wq287"></a>
<div class="notelisttitle" id="wq287">Notes:</div>
<ol type="1"><img src="delta.gif" alt="Start of change" />
<li>For iSCSI Windows servers, the dynamic and cluster shared disks use the
same sequence position range and can be intermixed. The combined total number
of dynamic and cluster shared disk links is 63.</li>
<li>Windows server clustering requires use of Microsoft&reg; Cluster Service (MSCS) to control
access to the shared disks in the cluster.</li>
<li>See the Create NWS Storage Space (CRTNWSSTG) command help text for a description
of the format types.</li>
<li>When multiple servers link a disk using shared update, only one server
can actually have write access to the disk at any point in time. For example,
on Windows servers, Microsoft Cluster Service (MSCS) is used
to control which server in the cluster has write access to the disk.</li>
<li>See the Create Network Server Desc (CRTNWSD) command help text for a description
of the NWSD types and the associated operating system (OS) types.</li><img src="deltaend.gif" alt="End of change" />
</ol>
<p>Network server storage spaces can reside in either the i5/OS system disk
pool (ASP 1) or a user disk pool. You can copy one disk drive to another to
move it to a different disk pool.</p>
<p><img src="delta.gif" alt="Start of change" />After a network server storage space has been created and linked
to an integrated server, you must format it from the Windows console. You
can choose from between three types of disk formats. You will probably choose
NTFS since it is the most efficient and secure format. Partitions formatted
with NTFS can be up to 1,024,000 MB. Another format type is FAT-32. Partitions
formatted with FAT-32 can be from 512 &ndash; 32,000 MB. The oldest format
type is FAT. The maximum possible size for a FAT partition is 2,047 MB. The
predefined installation source drive partition (D), which must be in FAT format,
is therefore limited to 2,047 MB.<img src="deltaend.gif" alt="End of change" /></p>
<p>Network server storage spaces are one of the two types of network storage
that integrated servers use. Integrated servers can also access resources
on i5/OS that an administrator has shared with the network by using iSeries NetServer&trade;.</p>
<p>The IBM&reg; iSeries integrated server support installation process creates several
disk drives that are used to install and run integrated Windows servers. See
the topic on <a href="rzahqrstrf.htm#rzahqrstrf">Predefined disk drives for integrated Windows servers</a>.</p>
<p><img src="delta.gif" alt="Start of change" />For information about creating drives, see <a href="rzahqcstpi.htm#rzahqcstpi">Create an integrated server disk drive</a><img src="deltaend.gif" alt="End of change" /></p>
<a id="Bot_Of_Page" name="Bot_Of_Page"></a>
</body>
</html>