141 lines
8.9 KiB
HTML
141 lines
8.9 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="Using CPYOPT to Backup a volume" />
|
||
|
|
<meta name="abstract" content="You can use the Copy Optical (CPYOPT) command to do a complete or partial copy of your volume." />
|
||
|
|
<meta name="description" content="You can use the Copy Optical (CPYOPT) command to do a complete or partial copy of your volume." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzam4cpyopt.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="rzam4usingcpyopttobackupavolume" />
|
||
|
|
<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>Using CPYOPT to Backup a volume</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzam4usingcpyopttobackupavolume"><a name="rzam4usingcpyopttobackupavolume"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Using CPYOPT to Backup a volume</h1>
|
||
|
|
<div><p>You can use the Copy Optical (CPYOPT) command to do a complete
|
||
|
|
or partial copy of your volume.</p>
|
||
|
|
<div class="p">The following describes the special processing of the CPYOPT command when
|
||
|
|
the target is a *PRIMARY or *BACKUP volume. Refer to the following list to
|
||
|
|
decide how to best use the command.<ul><li>Copy completely or partially. You can copy a file, a directory, a directory
|
||
|
|
with all of its sub directories, or an entire volume.</li>
|
||
|
|
<li>Copy incrementally. You can copy only what has changed since the previous
|
||
|
|
CPYOPT request.</li>
|
||
|
|
<li>Copy specifying a starting date for selecting files. Only files that are
|
||
|
|
created or changed on or after the specified date are eligible for copying.</li>
|
||
|
|
<li>Replicate the hierarchical structure of the source volume on the target
|
||
|
|
volume.CPYOPT requirements to volume type *PRIMARY When the target volume
|
||
|
|
is type *PRIMARY, the CPYOPT command has the following unique requirements:</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzam4cpyopt.htm" title="This topic discusses the Copy Optical (CPYOPT) CL command and some of the optional parameters which you can specify.">Copy optical (CPYOPT)</a></div>
|
||
|
|
</div>
|
||
|
|
</div><div class="nested1" xml:lang="en-us" id="rzam4cpyoptreqvoltypeprimary"><a name="rzam4cpyoptreqvoltypeprimary"><!-- --></a><h2 class="topictitle2">CPYOPT requirements to volume type *PRIMARY</h2>
|
||
|
|
<div><div class="p">When the target volume is type *PRIMARY, the CPYOPT command has the following
|
||
|
|
unique requirements:<ul><li>The source volume can be either type *PRIMARY or *BACKUP.</li>
|
||
|
|
<li>Because the target volume is *PRIMARY, all API requests and most optical
|
||
|
|
commands and utilities can access the volume.</li>
|
||
|
|
<li>Because utilities and user programs can update the *PRIMARY volume, you
|
||
|
|
need to determine how to protect directories and files from unauthorized change
|
||
|
|
or deletion.</li>
|
||
|
|
<li>The target volume could contain information for one or multiple optical
|
||
|
|
*PRIMARY volumes. An easy way to manage multiple volumes on a single target
|
||
|
|
volume would be to have a new first level directory. That directory name could
|
||
|
|
be the name of the source-primary volume.</li>
|
||
|
|
<li>You need a way of keeping track of when a volume or directory was last
|
||
|
|
backed up. Use the CPYOPT command to do it automatically.</li>
|
||
|
|
<li>The hierarchical structure on the target volume does not need to be identical
|
||
|
|
to that of the optical *PRIMARY volume.</li>
|
||
|
|
<li>The create date and time, and change date and time, of the file on the
|
||
|
|
target volume will be different than their counterparts on the optical primary
|
||
|
|
volume. The file creation data and time on the target volume is the date that
|
||
|
|
the file was written.</li>
|
||
|
|
<li>You can use directories and files on the target *PRIMARY volume directly.
|
||
|
|
You do not have to copy applications back to a *PRIMARY optical volume.</li>
|
||
|
|
<li>You can request that the system copy only new files on the source volume
|
||
|
|
to the target volume. This might be useful if you never changes files on your
|
||
|
|
source volume but only create new ones.</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div class="nested1" xml:lang="en-us" id="rzam4cpyoptreqvoltypebackup"><a name="rzam4cpyoptreqvoltypebackup"><!-- --></a><h2 class="topictitle2">CPYOPT requirements to volume type *BACKUP</h2>
|
||
|
|
<div><div class="p">When the target volume is type *BACKUP, the Copy Optical (CPYOPT) command
|
||
|
|
has the following unique requirements:<ul><li>The source volume must be type *PRIMARY.</li>
|
||
|
|
<li>Only the CPYOPT and CVTOPTBKU commands can write to the target *BACKUP
|
||
|
|
volume. APIs, utilities, and user programs cannot write to an optical *BACKUP
|
||
|
|
volume.</li>
|
||
|
|
<li>An optical *BACKUP volume can contain information for only one optical
|
||
|
|
*PRIMARY volume. This prevents two primary volumes from sharing the same optical
|
||
|
|
backup volume.</li>
|
||
|
|
<li>You cannot delete directories or files from an optical *BACKUP volume.
|
||
|
|
This ensures data integrity of the optical backup volume.</li>
|
||
|
|
<li>The system maintains the file create date and time, and change date and
|
||
|
|
time for the *PRIMARY volume on the optical *BACKUP volume.</li>
|
||
|
|
<li>A user application cannot directly use a file or directory on a *BACKUP
|
||
|
|
volume. First, you must copy the file or directory to an optical *PRIMARY
|
||
|
|
volume by using CPYOPT.</li>
|
||
|
|
<li>If the optical *PRIMARY volume is damaged or lost, you can convert the
|
||
|
|
optical *BACKUP volume to an optical *PRIMARY volume. You can do this by using
|
||
|
|
the Convert Optical Backup (CVTOPTBKU) CL command.</li>
|
||
|
|
<li>To maintain control information about the status of backup requests, optical
|
||
|
|
*BACKUP volumes require additional media usage. Because of this, a *PRIMARY
|
||
|
|
volume that is 100% used may not fit on an optical *BACKUP volume.</li>
|
||
|
|
<li>The system always initializes *BACKUP volumes with a 99% volume threshold.</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div class="nested1" xml:lang="en-us" id="rzam4sugsoncpyoptvoltypetouse"><a name="rzam4sugsoncpyoptvoltypetouse"><!-- --></a><h2 class="topictitle2">Suggestions on which CPYOPT volume type to use</h2>
|
||
|
|
<div><div class="p">Here is a list of items that you can use to determine if you should use
|
||
|
|
a target volume type of *PRIMARY or *BACKUP.<ul><li>In general, the CPYOPT to a type *PRIMARY volume gives you more flexibility,
|
||
|
|
but it requires more management of your backup volumes.</li>
|
||
|
|
<li>The CPYOPT to a type *BACKUP volume provides more management and security
|
||
|
|
for your optical backup volumes, but it is less flexible.</li>
|
||
|
|
<li>Use the CPYOPT command, and specify a type *PRIMARY volume, if you want
|
||
|
|
to copy data from several volumes to a single volume.</li>
|
||
|
|
<li>Use the CPYOPT command, and specify a type *BACKUP volume, if you want
|
||
|
|
better security for your backup volumes. The system cannot write volumes with
|
||
|
|
type *BACKUP to with normal optical commands or user programs.</li>
|
||
|
|
<li>Use the CPYOPT command and specify a type *BACKUP volume to save information
|
||
|
|
such as when the system copied directories and volumes, and the success status
|
||
|
|
of those copies.</li>
|
||
|
|
<li>The biggest advantage of using the CPYOPT to a type *BACKUP volume is
|
||
|
|
that the system stores the backup control information on the backup volume.
|
||
|
|
This information includes the relationship between files on the backup volume
|
||
|
|
and the files on the primary volume. This information can be very useful if
|
||
|
|
you ever need to recover the lost source data is from the backup volume.</li>
|
||
|
|
<li>Use the CPYOPT command, and specify a type *BACKUP volume, if you want
|
||
|
|
the source and target file dates (creation and change) to be identical.</li>
|
||
|
|
<li>One disadvantage in using the CPYOPT command to a type *BACKUP
|
||
|
|
volume is that the system uses extra space on the backup volume to store control
|
||
|
|
information. The amount that is used is approximately 3 times the sector size
|
||
|
|
for each directory. Therefore, if CPYOPT copies 100 directories from a primary
|
||
|
|
volume to a backup volume where the sector size on the backup volume is 2KB,
|
||
|
|
the backup volume uses an additional 600KB of space. In this example 600KB
|
||
|
|
of space is used every time the command is run.</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
|
||
|
|
</body>
|
||
|
|
</html>
|