113 lines
7.0 KiB
HTML
113 lines
7.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="reference" />
|
||
|
|
<meta name="DC.Title" content="Virtual tape media" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiurzaiu102.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../rzam4/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="virtualtape" />
|
||
|
|
<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>Virtual tape media</title>
|
||
|
|
</head>
|
||
|
|
<body id="virtualtape"><a name="virtualtape"><!-- --></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">Virtual tape media</h1>
|
||
|
|
<div><div class="section"><p>You can use virtual tape devices to save data directly to system
|
||
|
|
disk units for convenience, flexibility, and in some cases improved performance.
|
||
|
|
The following scenarios will give you some examples of ways that you can utilize
|
||
|
|
virtual tape in your save environment. Virtual tape is beneficial for unattended
|
||
|
|
saves because it eliminates media errors that could halt an unattended save.
|
||
|
|
If you do not allocate enough space in the virtual volumes within the image
|
||
|
|
catalog to save the intended information, virtual tape will use the auto-generate
|
||
|
|
feature to create additional virtual tape volumes.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Ability to duplicate to physical media</h4><div class="p">When a save
|
||
|
|
is complete to a virtual tape volume, you can duplicate the data to physical
|
||
|
|
media at any time and not interfere with system operations. You also have
|
||
|
|
the capability to send the stream files from the virtual tape save to another
|
||
|
|
system via FTP SSL. If you have multiple servers, your strategy could be to
|
||
|
|
save each system to virtual tape. Then, FTP the stream files to a single server
|
||
|
|
where the duplication to the physical media could take place. <div class="note"><span class="notetitle">Note:</span> In a
|
||
|
|
disaster recovery situation you must have physical media to perform your recovery.
|
||
|
|
If you are saving to virtual tape as part of your disaster recovery strategy,
|
||
|
|
you must duplicate your virtual saves to physical media. </div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Save to virtual tape</h4><p>Perform the following steps
|
||
|
|
to save data to virtual tape media.</p>
|
||
|
|
<ol><li>Ensure that the server has enough disk space to hold all the virtual images
|
||
|
|
you are going to create for your save operation.</li>
|
||
|
|
<li>Create a virtual tape device. <pre>CRTDEVTAP DEVD(virtual-device-name) RSRCNAME(*VRT) ONLINE(*YES) +
|
||
|
|
TEXT(text-description)</pre>
|
||
|
|
</li>
|
||
|
|
<li>Vary on the virtual tape device. <pre>VRYCFG CFGOBJ(virtual-device-name) CFGTYPE(*DEV) STATUS(*ON)</pre>
|
||
|
|
</li>
|
||
|
|
<li>Create an image catalog for your save operation. <pre>CRTIMGCLG IMGCLG(catalog-name) DIR(catalog-path) CRTDIR(*YES) +
|
||
|
|
TEXT(<var class="varname">catalog-descritpion</var>) TYPE(*TAP)</pre>
|
||
|
|
</li>
|
||
|
|
<li>Add new image catalog entries with a total capacity large enough for the
|
||
|
|
amount of data that you intend to save. If you plan to duplicate image catalogs
|
||
|
|
to physical media, then ensure you select a density that has a compatible
|
||
|
|
block size for the device that will be holding your data. The following command
|
||
|
|
will create a new standard labeled virtual tape volume with a maximum size
|
||
|
|
of 10GB that will be compatible for duplication to a physical tape device
|
||
|
|
that supports a 256KB maximum block size. The full 10GB of storage will be
|
||
|
|
allocated at create time. <pre>ADDIMGCLGE IMGCLG(catalog-name) FROMFILE(*NEW) TOFILE(VOL001) +
|
||
|
|
IMGSIZ(10000) TEXT(<var class="varname">text-description</var>) ALCSTG(*IMGSIZ)
|
||
|
|
VOLNAM(VOL001) VOLTYP(*SL) DENSITY(*VRT256K)</pre>
|
||
|
|
Repeat this step for
|
||
|
|
the number of desired images. You should add the images in the same order
|
||
|
|
as you plan to restore from them. The virtual images provide spanning capability,
|
||
|
|
with sequence numbers continuing from one volume to the next. The image
|
||
|
|
size can be as small as 48MB or as large as 1,000,00MB. If you do not want
|
||
|
|
to pre-allocate the storage you can use ALCSTG(*MIN) and the storage will
|
||
|
|
only be allocated as it is used for the save. </li>
|
||
|
|
<li>Load the image catalog. This step associates the virtual tape device to
|
||
|
|
the image catalog. Only one image catalog at a time can be associated with
|
||
|
|
a specific virtual tape device. <pre>LODIMGCLG IMGCLG(catalog-name) DEV(virtual-device-name) OPTION(*LOAD)</pre>
|
||
|
|
</li>
|
||
|
|
<li>Run a save command listing the virtual tape device in the DEV parameter.
|
||
|
|
Virtual tape devices operate similar to tape media library devices so entering
|
||
|
|
the volume names in the volume parameter automatically mounts the volumes.</li>
|
||
|
|
</ol>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Exclude virtual images from a full save</h4>After you create
|
||
|
|
virtual tape images, they will automatically be included when you perform
|
||
|
|
a full system save using GO SAVE Option 21. The virtual tape images could
|
||
|
|
significantly increase the time it takes to complete the Option 21 save operation,
|
||
|
|
even if the image catalog entries do not contain data. If you want to exclude
|
||
|
|
the virtual images from a full system save, use one of the following strategies: <ul><li>Use the Change Attribute (CHGATR) command to mark the image catalog directory
|
||
|
|
as non-saveable. For example: <pre>CHGATR OBJ('/Catalog-Path') ATR(*ALWSAV) VALUE(*NO) </pre>
|
||
|
|
</li>
|
||
|
|
<li>Use the Load Image Catalog (LODIMGCLG) command to make the image catalog
|
||
|
|
ready. Image catalogs with a ready status will be omitted from the save.</li>
|
||
|
|
<li>In an attended save, you can specify to omit the image catalog directories
|
||
|
|
on the Save Object (SAV) command.</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaiurzaiu102.htm">Choose your save media</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relinfo"><strong>Related information</strong><br />
|
||
|
|
<div><a href="../rzam4/rzam4virtualtape.htm">Virtual Tape</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<img src="./deltaend.gif" alt="End of change" /></body>
|
||
|
|
</html>
|