149 lines
9.2 KiB
HTML
149 lines
9.2 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="Virtual optical media" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiurzaiu102.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../rzam4/rzam4virtual.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../rzam8/rzam8fixinstallimage.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/crtdevopt.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/vrycfg.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/crtimgclg.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/addimgclge.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/lodimgclg.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/inzopt.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/chgatr.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/sav.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="virtualoptical" />
|
||
|
|
<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 optical media</title>
|
||
|
|
</head>
|
||
|
|
<body id="virtualoptical"><a name="virtualoptical"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Virtual optical media</h1>
|
||
|
|
<div><p>You can use virtual optical media to save images 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 optical in your save environment. Virtual optical 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 image catalog to save the
|
||
|
|
intended information, virtual optical will use the autoload feature to create
|
||
|
|
additional images with the same capacity as the last image you loaded, provided
|
||
|
|
the disk storage is available. You must specify automatic load in the reply
|
||
|
|
list, MSGID(OPT149F), to avoid receiving a message that interrupts the unattended
|
||
|
|
save.</p>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Ability to duplicate to physical media</h4><div class="p">When a save
|
||
|
|
is complete to virtual optical, you can transfer it 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 optical save to another system via
|
||
|
|
FTP. If you have multiple servers, your strategy could be to save each system
|
||
|
|
to virtual optical and then FTP the stream files to a single server where
|
||
|
|
the save to physical media could take place. You can save the virtual images
|
||
|
|
to tape in optical format, or you can use the Duplicate Optical (DUPOPT) command
|
||
|
|
to save the image to optical media. <div class="note"><span class="notetitle">Note:</span> In a disaster recovery situation
|
||
|
|
you must have physical media of the Licensed Internal Code and the operating
|
||
|
|
system to begin your recovery. If you are saving to virtual optical as part
|
||
|
|
of your disaster protection strategy, you must then save your Licensed Internal
|
||
|
|
Code and operating system to physical media from the virtual images. You must
|
||
|
|
also have access to all of your user data, either on a remote system or on
|
||
|
|
physical media.</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Save cumulative PTF record</h4><p>If you receive fixes
|
||
|
|
on CD-ROM, you can install your fixes from an image catalog. To maintain a
|
||
|
|
complete record of all of the fixes that you apply, you can save these virtual
|
||
|
|
PTF images to media. Then, in a recovery situation, you can restore all of
|
||
|
|
the cumulative PTF images and automatically install them from the image catalog.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Save to virtual optical</h4><p>Perform the following steps
|
||
|
|
to save data to virtual optical 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 optical device. <pre>CRTDEVOPT DEVD(virtual-device-name)RSRCNAME(*VRT) ONLINE(*YES)+
|
||
|
|
TEXT(<var class="varname">text-description</var>)</pre>
|
||
|
|
</li>
|
||
|
|
<li>Vary on the virtual optical 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">image-description</var>)</pre>
|
||
|
|
</li>
|
||
|
|
<li>Add a new image catalog entry with a size of 48MB to 16GB. If you are
|
||
|
|
performing a SAVSYS, the first volume must be at least 1489 MB to accommodate
|
||
|
|
the Licensed Internal Code. If you plan to save the full operating system,
|
||
|
|
add a new image catalog entry with a size of 4GB. If you plan to duplicate
|
||
|
|
image catalogs to physical media, then ensure you select a virtual image size
|
||
|
|
that matches the size of the media you plan to write to. <pre>ADDIMGCLGE IMGCLG(catalog-name) FROMFILE(*NEW) TOFILE(file-name) +
|
||
|
|
IMGSIZ(*DVD4700) TEXT(<var class="varname">text-description</var>) </pre>
|
||
|
|
<pre>ADDIMGCLGE IMGCLG(catalog-name) FROMFILE(*NEW) TOFILE(file-name) +
|
||
|
|
IMGSIZ(*CD650) TEXT(<var class="varname">catalog-descritpion</var>)</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.</li>
|
||
|
|
<li>Load the image catalog. This step associates the virtual optical device
|
||
|
|
to the image catalog. Only one image catalog at a time can be associated with
|
||
|
|
a specific virtual optical device. <pre>LODIMGCLG IMGCLG(catalog-name) DEV(virtual-device-name) OPTION(*LOAD)</pre>
|
||
|
|
</li>
|
||
|
|
<li>Initialize the new volume. <pre>INZOPT NEWVOL(volume-name) DEV(virtual-device-name) TEXT('volume text')</pre>
|
||
|
|
Repeat
|
||
|
|
this step for the number of new images you want to initialize. Use the WRKIMGCLGE
|
||
|
|
(Work with image catalog entries) command to select the image to be initialized
|
||
|
|
or use the LODIMGCLGE (Load or unload image catalog entry) command to continue
|
||
|
|
to the next volume to be initialized. <pre>LODIMGCLGE IMGCLG(catelog-name) IMGCLGIDX(2) OPTION(*MOUNT)</pre>
|
||
|
|
<pre>LODIMGCLGE IMGCLG(catelog-name) IMGCLGIDX(1) OPTION(*MOUNT)</pre>
|
||
|
|
When you have completed initializing the new volumes, leave the first entry
|
||
|
|
in mounted status. </li>
|
||
|
|
<li>Run the save command for your desired save operation, listing the virtual
|
||
|
|
optical device in the DEV parameter.</li>
|
||
|
|
</ol>
|
||
|
|
<div class="note"><span class="notetitle">Note:</span> After you create virtual optical images, they will automatically
|
||
|
|
be included when you perform a full system save using GO SAVE Option 21. The
|
||
|
|
virtual optical 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('/MYINFO') 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>
|
||
|
|
<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/rzam4virtual.htm">Virtual optical storage</a></div>
|
||
|
|
<div><a href="../rzam8/rzam8fixinstallimage.htm">Install your fixes from an image catalog</a></div>
|
||
|
|
<div><a href="../cl/crtdevopt.htm">CRTDEVOPT</a></div>
|
||
|
|
<div><a href="../cl/vrycfg.htm">VRYCFG</a></div>
|
||
|
|
<div><a href="../cl/crtimgclg.htm">CRTIMGCLG</a></div>
|
||
|
|
<div><a href="../cl/addimgclge.htm">ADDIMGCLGE</a></div>
|
||
|
|
<div><a href="../cl/lodimgclg.htm">LODIMGCLG</a></div>
|
||
|
|
<div><a href="../cl/inzopt.htm">INZOPT</a></div>
|
||
|
|
<div><a href="../cl/chgatr.htm">CHGATR</a></div>
|
||
|
|
<div><a href="../cl/sav.htm">SAV</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|