101 lines
6.4 KiB
HTML
101 lines
6.4 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="Complete backup range" />
|
||
|
|
<meta name="abstract" content="This topic discusses the different types of complete backup ranges." />
|
||
|
|
<meta name="description" content="This topic discusses the different types of complete backup ranges." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzam4voltypbckup.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="rzam4compbckuprnge" />
|
||
|
|
<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>Complete backup range</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzam4compbckuprnge"><a name="rzam4compbckuprnge"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Complete backup range</h1>
|
||
|
|
<div><p>This topic discusses the different types of complete backup ranges.</p>
|
||
|
|
<p>When an optical *PRIMARY volume to copied to an optical *BACKUP volume
|
||
|
|
a special file called a Complete Backup Range is written to the *BACKUP volume.
|
||
|
|
This file indicates the last time a backup was done. The system keeps backup
|
||
|
|
control information for the volume as well as each directory on the volume.
|
||
|
|
If the volume or directory was successfully backed up the Complete Backup
|
||
|
|
Range will contain both a starting and ending date and time. When a range
|
||
|
|
exists for an optical backup volume or directory, it has a specific meaning:
|
||
|
|
The backup directory or volume has a copy of all the created or changed files
|
||
|
|
within the date range that correspond to the primary directory or volume. </p>
|
||
|
|
<p>For example, volume BVOL1 is an optical *BACKUP volume for *PRIMARY volume
|
||
|
|
PVOL1. BVOL1 contains directory /DIR1 that has a Complete Backup Range as
|
||
|
|
follows: </p>
|
||
|
|
<ul class="simple"><li>Start date: 1/1/99</li>
|
||
|
|
<li>Start time: 09:00:00</li>
|
||
|
|
<li>End date: 1/30/99</li>
|
||
|
|
<li>End time: 22:00:00</li>
|
||
|
|
</ul>
|
||
|
|
<p>Start Date: 1/1/99 Start Time: 09:00:00 End Date: 1/30/99 End Time: 22:00:00
|
||
|
|
This means that the system backe up all the changed or created files in /DIR1
|
||
|
|
on PVOL1 since 9:00 a.m. on 1 January 1999. The system backed up files to
|
||
|
|
/DIR1 on BVOL1 at 10:00 p.m. on 30 January 1999. Any files that were created
|
||
|
|
or changed on *PRIMARY volume PVOL1 in directory /DIR1 after 22:00:00 on 1/30/99
|
||
|
|
would not yet have been backed up.</p>
|
||
|
|
<p>This means that the system backe up all the changed or created
|
||
|
|
files in /DIR1 on PVOL1 since 9:00 a.m. on 1 January 1999. The system backed
|
||
|
|
up files to /DIR1 on BVOL1 at 10:00 p.m. on 30 January 1999. Any files that
|
||
|
|
were created or changed on *PRIMARY volume PVOL1 in directory /DIR1 after
|
||
|
|
22:00:00 on 1/30/99 would not yet have been backed up.</p>
|
||
|
|
<p><strong>Complete backup range for directories</strong></p>
|
||
|
|
<p>The Complete Backup Range for a directory does not encompass all subdirectories
|
||
|
|
of the directory. In other words, each directory has its own unique Complete
|
||
|
|
Backup Range. For example, assume that directory /A has a Complete Backup
|
||
|
|
Range of 1 March 1999 through 1 May 1999. This does not necessarily mean that
|
||
|
|
directory /A/B has the same complete range. In fact, /A/B might have no Complete
|
||
|
|
Backup Range at all. The complete range does not reflect a hierarchical range
|
||
|
|
over all directories within that subtree. </p>
|
||
|
|
<p>The system updates the Complete Backup Range for a backup directory after
|
||
|
|
it copies all eligible files in the primary directory. </p>
|
||
|
|
<div class="note"><span class="notetitle">Note:</span> Use the SLTFILE parameter on the CPYOPT command to determine if
|
||
|
|
a file is eligible. If you use *ALL, all files are eligible to copy. If you
|
||
|
|
use *CHANGED, only those files that were created or changed since the last
|
||
|
|
CPYOPT command are eligible. If you specified *NEW, the system copies files
|
||
|
|
only if they do not exist on the target volume. </div>
|
||
|
|
<p>For example, FILE.001 gets copied on 1 March 1999 as a result of a complete
|
||
|
|
backup of directory /DIR1. At this time /DIR1 is given an ending range of
|
||
|
|
1 March 1999. On 1 April 1999, the user has the system back up directory /DIR1
|
||
|
|
again by specifying SLTFILE(*CHANGED). However, the back up affects only the
|
||
|
|
files that have changed. If FILE.001 has not changed since the previous CPYOPT
|
||
|
|
command, this file is not eligible to copy. However, the system updates the
|
||
|
|
ending range for /DIR1 to 1 April 1999 if none of the eligible files fail
|
||
|
|
to copy. </p>
|
||
|
|
<p><strong>Complete Backup Range for Optical Volumes</strong></p>
|
||
|
|
<p> The Complete Backup Range for an optical volume is very similar to that
|
||
|
|
of an optical directory. The complete range for a directory represents the
|
||
|
|
relationship between the files in a backup directory and those in the primary
|
||
|
|
directory. Likewise, the complete range for an optical backup volume represents
|
||
|
|
the relationship between the files on an optical backup volume and those on
|
||
|
|
the primary volume. You must back up all eligible files on a volume to update
|
||
|
|
the complete range of the volume. </p>
|
||
|
|
<p>You can update the complete range for a volume only if the CPYOPT command
|
||
|
|
specifies the FROMPATH(/) and CPYSUBDIR(*YES) variables. This ensures that
|
||
|
|
the system will process all files on the *PRIMARY volume.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzam4voltypbckup.htm" title="This topic discusses the *BACKUP volume type and the unique backup process that are associated with a *BACKUP volume.">Volume type *BACKUP</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|