148 lines
9.1 KiB
HTML
148 lines
9.1 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="Volume spanning for virtual optical storage" />
|
||
|
|
<meta name="abstract" content="When a save operation spans a volume, it pauses the save process when the current piece of media you are using runs out of space and it continues the save operation on the next piece of media. In the context of backup and recovery, a volume is the media that you are using to save your data. Spanning occurs when the volumes have files that continue from one volume to the next." />
|
||
|
|
<meta name="description" content="When a save operation spans a volume, it pauses the save process when the current piece of media you are using runs out of space and it continues the save operation on the next piece of media. In the context of backup and recovery, a volume is the media that you are using to save your data. Spanning occurs when the volumes have files that continue from one volume to the next." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzam4virtual.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="rzam4vsvo" />
|
||
|
|
<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>Volume spanning for virtual optical storage</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzam4vsvo"><a name="rzam4vsvo"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Volume spanning for virtual optical storage</h1>
|
||
|
|
<div><p>When a save operation <strong>spans</strong> a volume, it pauses the save
|
||
|
|
process when the current piece of media you are using runs out of space and
|
||
|
|
it continues the save operation on the next piece of media. In the context
|
||
|
|
of backup and recovery, a volume is the media that you are using to save your
|
||
|
|
data. Spanning occurs when the volumes have files that continue from one volume
|
||
|
|
to the next.</p>
|
||
|
|
<p>When you perform a save operation and span virtual images, the multivolume
|
||
|
|
set of virtual images behaves just like a multivolume set of any form of actual
|
||
|
|
media.</p>
|
||
|
|
<p>One advantage of using virtual storage for a backup operation is that if
|
||
|
|
you have enough disk space, you can perform unattended backups without the
|
||
|
|
use of a media autoloader or a media library.</p>
|
||
|
|
<p>Similar to actual devices, when you span volumes of virtual images, you
|
||
|
|
can specify a volume list or specify *MOUNTED for the VOL parameter on all
|
||
|
|
of the save commands. If you specify a volume list, the server mounts the
|
||
|
|
volumes of virtual images when they are needed. If you specify *MOUNTED, you
|
||
|
|
must have the virtual images mounted when you start the command. In either
|
||
|
|
case, you must provide enough volumes to complete the save operation.</p>
|
||
|
|
<p>Whether you specify *MOUNTED or a volume list, if you do not provide enough
|
||
|
|
volumes to complete save operation, the server sends you inquiry message OPT149F
|
||
|
|
- Load next volume on optical device &1. Inquiry message OPT149F provides
|
||
|
|
you with three options:</p>
|
||
|
|
<ul><li>Cancel the operation</li>
|
||
|
|
<li>Allow the server to create a new volume for you</li>
|
||
|
|
<li>Pause the operation and create a new volume manually</li>
|
||
|
|
</ul>
|
||
|
|
<p>If you allow the server to create a new volume for you, the server does
|
||
|
|
the following:</p>
|
||
|
|
<ul><li>Adds a *NEW volume and inserts it at position 256 in the
|
||
|
|
image catalog</li>
|
||
|
|
<li>Mounts the volume in the virtual device</li>
|
||
|
|
<li>Initializes the new volume</li>
|
||
|
|
<li>Continues the save</li>
|
||
|
|
</ul>
|
||
|
|
<p>When the server creates a new volume, the server gives the new virtual
|
||
|
|
image a name. The server uses a time stamp for the volume ID. The image name
|
||
|
|
is a combination of volume ID and the volume sequence number. The server inserts
|
||
|
|
the new virtual image in position 256 of the image catalog. The size of the
|
||
|
|
new virtual image is the same as the previous virtual image.</p>
|
||
|
|
<p>The following table shows an example of what happens when the server adds
|
||
|
|
two new volumes during save to an image catalog where Volume 2 existed before
|
||
|
|
starting the save.</p>
|
||
|
|
|
||
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><thead align="left"><tr><th valign="top" width="8.333333333333332%" id="d0e55">Index</th>
|
||
|
|
<th valign="top" width="16.666666666666664%" id="d0e57">Volume ID</th>
|
||
|
|
<th valign="top" width="16.666666666666664%" id="d0e59">Virtual image name</th>
|
||
|
|
<th valign="top" width="16.666666666666664%" id="d0e61">Volume sequence number</th>
|
||
|
|
<th valign="top" width="8.333333333333332%" id="d0e63">Size</th>
|
||
|
|
<th valign="top" width="33.33333333333333%" id="d0e65">Description</th>
|
||
|
|
</tr>
|
||
|
|
</thead>
|
||
|
|
<tbody><tr><td valign="top" width="8.333333333333332%" headers="d0e55 ">1</td>
|
||
|
|
<td valign="top" width="16.666666666666664%" headers="d0e57 ">Volume1</td>
|
||
|
|
<td valign="top" width="16.666666666666664%" headers="d0e59 ">File1</td>
|
||
|
|
<td valign="top" width="16.666666666666664%" headers="d0e61 ">1</td>
|
||
|
|
<td valign="top" width="8.333333333333332%" headers="d0e63 ">1300 MB</td>
|
||
|
|
<td valign="top" width="33.33333333333333%" headers="d0e65 ">My Save 1</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="8.333333333333332%" headers="d0e55 ">2</td>
|
||
|
|
<td valign="top" width="16.666666666666664%" headers="d0e57 ">Volume2</td>
|
||
|
|
<td valign="top" width="16.666666666666664%" headers="d0e59 ">File2</td>
|
||
|
|
<td valign="top" width="16.666666666666664%" headers="d0e61 ">2</td>
|
||
|
|
<td valign="top" width="8.333333333333332%" headers="d0e63 ">650 MB</td>
|
||
|
|
<td valign="top" width="33.33333333333333%" headers="d0e65 ">My Save 1</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="8.333333333333332%" headers="d0e55 ">253</td>
|
||
|
|
<td valign="top" width="16.666666666666664%" headers="d0e57 ">030311124115</td>
|
||
|
|
<td valign="top" width="16.666666666666664%" headers="d0e59 ">0303111241150003</td>
|
||
|
|
<td valign="top" width="16.666666666666664%" headers="d0e61 ">3</td>
|
||
|
|
<td valign="top" width="8.333333333333332%" headers="d0e63 ">650 MB</td>
|
||
|
|
<td valign="top" width="33.33333333333333%" headers="d0e65 "><p>SET ID VOLUME1 SEQ<br />
|
||
|
|
0003</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="8.333333333333332%" headers="d0e55 ">254</td>
|
||
|
|
<td valign="top" width="16.666666666666664%" headers="d0e57 ">030311124330</td>
|
||
|
|
<td valign="top" width="16.666666666666664%" headers="d0e59 ">0303111255320004</td>
|
||
|
|
<td valign="top" width="16.666666666666664%" headers="d0e61 ">4</td>
|
||
|
|
<td valign="top" width="8.333333333333332%" headers="d0e63 ">650 MB</td>
|
||
|
|
<td valign="top" width="33.33333333333333%" headers="d0e65 "><p>SET ID VOLUME1 SEQ<br />
|
||
|
|
0004</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="8.333333333333332%" headers="d0e55 ">255</td>
|
||
|
|
<td valign="top" width="16.666666666666664%" headers="d0e57 ">030311124545</td>
|
||
|
|
<td valign="top" width="16.666666666666664%" headers="d0e59 ">0303111256450005</td>
|
||
|
|
<td valign="top" width="16.666666666666664%" headers="d0e61 ">5</td>
|
||
|
|
<td valign="top" width="8.333333333333332%" headers="d0e63 ">650 MB</td>
|
||
|
|
<td valign="top" width="33.33333333333333%" headers="d0e65 "><p>SET ID VOLUME1 SEQ<br />
|
||
|
|
0005</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="8.333333333333332%" headers="d0e55 ">256</td>
|
||
|
|
<td valign="top" width="16.666666666666664%" headers="d0e57 ">030311124801</td>
|
||
|
|
<td valign="top" width="16.666666666666664%" headers="d0e59 ">0303111248010006</td>
|
||
|
|
<td valign="top" width="16.666666666666664%" headers="d0e61 ">6</td>
|
||
|
|
<td valign="top" width="8.333333333333332%" headers="d0e63 ">650 MB</td>
|
||
|
|
<td valign="top" width="33.33333333333333%" headers="d0e65 "><p>SET ID VOLUME1 SEQ<br />
|
||
|
|
0006</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
</tbody>
|
||
|
|
</table>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Consideration for full backups</h4><p>If you are doing
|
||
|
|
a full backup, with the Save System (SAVSYS) command for example, the first
|
||
|
|
volume must be least 1489 MB. The first volume must be at least 1489 MB because
|
||
|
|
the first volume must be large enough to save the Licensed Internal Code.
|
||
|
|
The remaining volumes can be smaller than 1489 MB.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <img src="./delta.gif" alt="Start of change" /><a href="rzam4virtual.htm" title="When you use virtual optical storage, you create virtual CD or DVD images that exist on your server disk units.">Virtual optical storage</a><img src="./deltaend.gif" alt="End of change" /></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|