156 lines
9.6 KiB
HTML
156 lines
9.6 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="task" />
|
|||
|
|
<meta name="DC.Title" content="Set up virtual tape storage" />
|
|||
|
|
<meta name="abstract" content="This topic provides a high-level overview of the steps used to set up virtual tape storage. This topic also provides links to information that provide specific instructions for setting up virtual tape storage based on what task you want to accomplish." />
|
|||
|
|
<meta name="description" content="This topic provides a high-level overview of the steps used to set up virtual tape storage. This topic also provides links to information that provide specific instructions for setting up virtual tape storage based on what task you want to accomplish." />
|
|||
|
|
<meta name="DC.Relation" scheme="URI" content="rzam4virtualtape.htm" />
|
|||
|
|
<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="rzam4virtualtapeuse" />
|
|||
|
|
<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>Set up virtual tape storage</title>
|
|||
|
|
</head>
|
|||
|
|
<body id="rzam4virtualtapeuse"><a name="rzam4virtualtapeuse"><!-- --></a>
|
|||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|||
|
|
<h1 class="topictitle1">Set up virtual tape storage</h1>
|
|||
|
|
<div><p>This topic provides a high-level overview of the steps used to
|
|||
|
|
set up virtual tape storage. This topic also provides links to information
|
|||
|
|
that provide specific instructions for setting up virtual tape storage based
|
|||
|
|
on what task you want to accomplish.</p>
|
|||
|
|
<div class="section"><p>Here is a high-level overview of how to set up virtual tape storage
|
|||
|
|
for the most common tasks. The exact steps you use to set up virtual tape
|
|||
|
|
storage depend on what task you want to accomplish, such as performing a save
|
|||
|
|
operation or distributing software.</p>
|
|||
|
|
<p>The specific tasks provide links
|
|||
|
|
to instructions for the different tasks that you can perform with virtual
|
|||
|
|
tape storage.</p>
|
|||
|
|
<p>The tasks are as follows:</p>
|
|||
|
|
<ul><li><a href="#createvd">Create virtual devices</a></li>
|
|||
|
|
<li><a href="#create">Create virtual images in an image catalog</a></li>
|
|||
|
|
<li><a href="#use">Use virtual images in an image catalog</a></li>
|
|||
|
|
<li><a href="#specifictasks">Specific tasks</a></li>
|
|||
|
|
</ul>
|
|||
|
|
</div>
|
|||
|
|
</div>
|
|||
|
|
<div>
|
|||
|
|
<div class="familylinks">
|
|||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <img src="./delta.gif" alt="Start of change" /><a href="rzam4virtualtape.htm" title="When you use virtual tape devices, you create virtual tape volumes that exist on your server disk units.">Virtual tape</a><img src="./deltaend.gif" alt="End of change" /></div>
|
|||
|
|
</div>
|
|||
|
|
</div><div class="nested1" xml:lang="en-us" id="createvd"><a name="createvd"><!-- --></a><h2 class="topictitle2">Create virtual devices</h2>
|
|||
|
|
<div><div class="p"><span>If you do not already have a virtual tape device type 63B0, create
|
|||
|
|
one and vary it on: </span> <pre>CRTDEVTAP DEVD(TAPVRT01) RSRCNAME(*VRT)
|
|||
|
|
VRYCFG CFGOBJ(TAPVRT01) CFGTYPE(*DEV) STATUS(*ON)</pre>
|
|||
|
|
<div class="note"><span class="notetitle">Note:</span> You can
|
|||
|
|
create up to 35 virtual tape devices.</div>
|
|||
|
|
</div>
|
|||
|
|
</div>
|
|||
|
|
</div>
|
|||
|
|
<div class="nested1" xml:lang="en-us" id="create"><a name="create"><!-- --></a><h2 class="topictitle2">Create virtual images in an image catalog</h2>
|
|||
|
|
<div><ol><li class="stepexpand"><span>Create the image catalog:</span> <pre>CRTIMGCLG IMGCLG(MYCATALOG) DIR('/MYCATALOGDIRECTORY') TYPE(*TAP)</pre>
|
|||
|
|
</li>
|
|||
|
|
<li class="stepexpand"><span>Add the virtual tape volume from an existing virtual tape file
|
|||
|
|
or create a new virtual tape volume.</span> <ul><li>To add images from an image file: <pre>ADDIMGCLGE IMGCLG(MYCATALOG) FROMFILE(SLIC_N) TOFILE(*fromfile)</pre>
|
|||
|
|
<p>Repeat
|
|||
|
|
this step for each file in your catalog directory. This step assumes your
|
|||
|
|
image is already in the image catalog directory.</p>
|
|||
|
|
</li>
|
|||
|
|
<li>To create new virtual tape volumes:<pre>ADDIMGCLG IMGCLG(MYCATAGLOG) FROMFILE(*NEW)
|
|||
|
|
TOFILE(vo1001) VOLNAME(VOL1001)</pre>
|
|||
|
|
</li>
|
|||
|
|
</ul>
|
|||
|
|
</li>
|
|||
|
|
</ol>
|
|||
|
|
</div>
|
|||
|
|
</div>
|
|||
|
|
<div class="nested1" xml:lang="en-us" id="use"><a name="use"><!-- --></a><h2 class="topictitle2">Use virtual images in an image catalog</h2>
|
|||
|
|
<div><div class="p"><span>Load the image catalog in the virtual device</span> <pre>LODIMGCLG IMGCLG(MYCATALOG) DEV(TAPVRT01)</pre>
|
|||
|
|
</div>
|
|||
|
|
</div>
|
|||
|
|
</div>
|
|||
|
|
<div class="nested1" xml:lang="en-us" id="specifictasks"><a name="specifictasks"><!-- --></a><h2 class="topictitle2">Specific tasks</h2>
|
|||
|
|
<div><div class="section"><p>You can perform save and restore operations with virtual tape
|
|||
|
|
storage.</p>
|
|||
|
|
<dl><dt class="dlterm">Perform a save operation</dt>
|
|||
|
|
<dd>To save to virtual tape storage, see <a href="..//rzaiu/rzaiutapemedia.htm">Consider using virtual tape storage</a> in the <a href="../rzaiu/rzaiuintro.htm">Backup up your server</a> topic.</dd>
|
|||
|
|
<dt class="dlterm">Perform a restore operation</dt>
|
|||
|
|
<dd>To restore from virtual tape storage, see <a href="../books/sc415304.pdf" target="_blank">Backup and Recovery</a> <img src="wbpdf.gif" alt="Link to PDF" />.</dd>
|
|||
|
|
<dt class="dlterm">Duplicating virtual tape to physical media</dt>
|
|||
|
|
<dd>When you plan to duplicate the virtual tape volumes to physical tape devices
|
|||
|
|
you will need to make sure that the virtual tape volumes are created using
|
|||
|
|
a block size that is compatible with your physical tape device. The density
|
|||
|
|
(format) of the virtual tape volumes is used to control the maximum size that
|
|||
|
|
is used for the blocks of data on the virtual tape volume. . If you are
|
|||
|
|
unsure what block size your tape device supports, you can view the supported
|
|||
|
|
block size information by using iSeries™ Navigator to display the properties
|
|||
|
|
of your physical tape device.</dd>
|
|||
|
|
<dt class="dlterm">Using volumes in dependent image catalogs</dt>
|
|||
|
|
<dd>A dependent catalog provides a read-only view of the virtual tape volumes
|
|||
|
|
that are within a reference image catalog. To create dependent image catalogs
|
|||
|
|
use the following command: <pre>CRTIMGCLG IMGCLG(JOEDEP) DIR(*REFIMGCLG) TYPE(*TAP) REFIMGCLG(JOE) </pre>
|
|||
|
|
</dd>
|
|||
|
|
<dd class="ddexpand">All of the volumes in the reference image catalog (JOE) are accessible
|
|||
|
|
when the dependent image catalog (JOEDEP) is mounted in a separate virtual
|
|||
|
|
tape device. The dependent image catalogs are not synchronized with additional
|
|||
|
|
changes that are made to the reference image catalog. </dd>
|
|||
|
|
<dd class="ddexpand">Multiple dependent image catalogs can be created all pointing to the same
|
|||
|
|
reference catalog. The same virtual tape volume can be mounted in several
|
|||
|
|
virtual devices at the same time through the use of dependent image catalogs.
|
|||
|
|
This mounting procedure enables the same virtual tape volume to be used for
|
|||
|
|
input operations by multiple users at the same time.</dd>
|
|||
|
|
<dt class="dlterm">Using virtual tape from other partitions</dt>
|
|||
|
|
<dd><ol><li>Make sure that the virtual tape device description has unload at vary
|
|||
|
|
off with parameters specifying *NO. </li>
|
|||
|
|
<li>Mount the virtual volume you want to use from the other partition using
|
|||
|
|
the image catalog commands.</li>
|
|||
|
|
<li>Vary off the virtual tape device. <div class="note"><span class="notetitle">Note:</span> The virtual volume is still mounted. </div>
|
|||
|
|
</li>
|
|||
|
|
</ol>
|
|||
|
|
<p>The other partition can now use the previously mounted virtual tape
|
|||
|
|
volume through virtual I/O to the virtual tape device.</p>
|
|||
|
|
</dd>
|
|||
|
|
<dt class="dlterm">Using virtual tape volumes in user ASP's</dt>
|
|||
|
|
<dd><ol><li>CRTUDFS '/dev/qaspXX/aspXX.udfs', where XX is the ASP number </li>
|
|||
|
|
<li>MKDIR ‘/your-path’ to make a mount point directory </li>
|
|||
|
|
<li>MOUNT *UDFS ‘/dev/qaspXX/aspXX.udfs’ ‘/mount-point-directory’</li>
|
|||
|
|
<li>Now anything you create in ‘/mountpoint’ is created in the UDFS </li>
|
|||
|
|
<li>Use the CRTIMGCLG command to create an image catalog with the mount point
|
|||
|
|
in the path name</li>
|
|||
|
|
</ol>
|
|||
|
|
<div class="note"><span class="notetitle">Note:</span> You cannot specify the mount-point directory when specifying a
|
|||
|
|
path-name with the CRTIMGCLG command. Only the directory below the mount-point
|
|||
|
|
can be specified.</div>
|
|||
|
|
</dd>
|
|||
|
|
<dt class="dlterm">Using virtual tape volumes in independent ASP's</dt>
|
|||
|
|
<dd>To use a virtual tape volume in an independent ASP specify the ASP device
|
|||
|
|
name as the first part of the IFS path name. The independent ASP must be varied
|
|||
|
|
on before the virtual tape volumes are usable, so certain restore commands,
|
|||
|
|
such as RSTLICPGM can not be used for virtual tape volumes in independent
|
|||
|
|
ASPs. </dd>
|
|||
|
|
<dt class="dlterm">Image files *ALWSAV attributes </dt>
|
|||
|
|
<dd>When the image catalog is in ready status all of the image catalog's
|
|||
|
|
images have a *ALWSAV attribute value of *NO. This does not allow the images
|
|||
|
|
to be saved by the Save Object (SAV) command or the QsrSave API. When the
|
|||
|
|
image catalog is not in ready status all of the image catalog's images have
|
|||
|
|
a *ALWSAV attribute value of *YES. This allows the images to be saved. </dd>
|
|||
|
|
</dl>
|
|||
|
|
</div>
|
|||
|
|
</div>
|
|||
|
|
</div>
|
|||
|
|
|
|||
|
|
</body>
|
|||
|
|
</html>
|