111 lines
6.8 KiB
HTML
111 lines
6.8 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 tape storage" />
|
||
|
|
<meta name="abstract" content="Spanning occurs when the volumes have files that continue from one volume to the next." />
|
||
|
|
<meta name="description" content="Spanning occurs when the volumes have files that continue from one volume to the next." />
|
||
|
|
<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="rzam4virtspan" />
|
||
|
|
<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 tape storage</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzam4virtspan"><a name="rzam4virtspan"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Volume spanning for virtual tape storage</h1>
|
||
|
|
<div><p>Spanning occurs when the volumes have files that continue from
|
||
|
|
one volume to the next.</p>
|
||
|
|
<p>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 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. </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. In either case, you should
|
||
|
|
allow for enough volumes to complete the save operation.</p>
|
||
|
|
<p>If *MOUNTED is specified the volume that is mounted will be used. If there
|
||
|
|
are no volumes mounted, the next loaded volume in the image catalog will be
|
||
|
|
mounted automatically. </p>
|
||
|
|
<p>If *MOUNTED is specified for a save, a new volume will be automatically
|
||
|
|
created when the end of the image catalog is reached. </p>
|
||
|
|
<div class="p">If a volume list is specified for a save, message CPA 6798 will be displayed
|
||
|
|
when the volume list is exhausted. You can provide a new volume at this time. <div class="note"><span class="notetitle">Note:</span> If
|
||
|
|
the new volume specified in reply to message CPA6798 does not exist, it will
|
||
|
|
be automatically created.</div>
|
||
|
|
</div>
|
||
|
|
<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>Continues the save</li>
|
||
|
|
</ul>
|
||
|
|
<p>When the server creates a new volume, the server gives the new virtual
|
||
|
|
image a name. The server always inserts the new virtual image in position
|
||
|
|
256 of the image catalog. The size of the new virtual image is set to 1,000,000
|
||
|
|
MB with ALCSTG(*MIN). The previous volume gets moved to an earlier position.</p>
|
||
|
|
<p>The following table shows an example of what happens when the server adds
|
||
|
|
a new volume during a save to an image catalog where Vol001 and Vol002 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="d0e51">Index</th>
|
||
|
|
<th valign="top" width="16.666666666666664%" id="d0e53">Volume Name</th>
|
||
|
|
<th valign="top" width="16.666666666666664%" id="d0e55">Virtual image name</th>
|
||
|
|
<th valign="top" width="16.666666666666664%" id="d0e57">Volume sequence number</th>
|
||
|
|
<th valign="top" width="8.333333333333332%" id="d0e59">Size</th>
|
||
|
|
<th valign="top" width="33.33333333333333%" id="d0e61">Description</th>
|
||
|
|
</tr>
|
||
|
|
</thead>
|
||
|
|
<tbody><tr><td valign="top" width="8.333333333333332%" headers="d0e51 ">1</td>
|
||
|
|
<td valign="top" width="16.666666666666664%" headers="d0e53 ">Vol001</td>
|
||
|
|
<td valign="top" width="16.666666666666664%" headers="d0e55 ">File1</td>
|
||
|
|
<td valign="top" width="16.666666666666664%" headers="d0e57 ">1</td>
|
||
|
|
<td valign="top" width="8.333333333333332%" headers="d0e59 ">1000 MB</td>
|
||
|
|
<td valign="top" width="33.33333333333333%" headers="d0e61 ">My Save 1</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="8.333333333333332%" headers="d0e51 ">2</td>
|
||
|
|
<td valign="top" width="16.666666666666664%" headers="d0e53 ">Vol002</td>
|
||
|
|
<td valign="top" width="16.666666666666664%" headers="d0e55 ">File2</td>
|
||
|
|
<td valign="top" width="16.666666666666664%" headers="d0e57 ">2</td>
|
||
|
|
<td valign="top" width="8.333333333333332%" headers="d0e59 ">1000 MB</td>
|
||
|
|
<td valign="top" width="33.33333333333333%" headers="d0e61 ">My Save 1</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="8.333333333333332%" headers="d0e51 ">256</td>
|
||
|
|
<td valign="top" width="16.666666666666664%" headers="d0e53 ">GEN001</td>
|
||
|
|
<td valign="top" width="16.666666666666664%" headers="d0e55 ">GEN001</td>
|
||
|
|
<td valign="top" width="16.666666666666664%" headers="d0e57 ">3</td>
|
||
|
|
<td valign="top" width="8.333333333333332%" headers="d0e59 ">1,000,000 MB</td>
|
||
|
|
<td valign="top" width="33.33333333333333%" headers="d0e61 ">Created on 12/31/05 15:38:29</td>
|
||
|
|
</tr>
|
||
|
|
</tbody>
|
||
|
|
</table>
|
||
|
|
</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>
|
||
|
|
</body>
|
||
|
|
</html>
|