ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzam4_5.4.0.1/rzam4compbckuplastdt.htm

92 lines
5.7 KiB
HTML
Raw Normal View History

2024-04-02 14:02:31 +00:00
<?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 last changed date and time" />
<meta name="abstract" content="Using the CPYOPT command causes the system to write the last changed date and time of an optical backup volume or directory." />
<meta name="description" content="Using the CPYOPT command causes the system to write the last changed date and time of an optical backup volume or directory." />
<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="rzam4compbckuplastdt" />
<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 last changed date and time</title>
</head>
<body id="rzam4compbckuplastdt"><a name="rzam4compbckuplastdt"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Complete backup range last changed date and time</h1>
<div><p>Using the CPYOPT command causes the system to write the last changed
date and time of an optical backup volume or directory.</p>
<p>This includes any time that the system wrote files or directory attributes
to the directory or volume. </p>
<p>The last changed date and time for that directory and volume will always
reflect the date and time of the request. This remains true even if the system
writes a file to a backup directory. </p>
<p><strong>Scenario — OneLast Changed Date and Time: </strong>On 1 July 1999, the user
issues the CPYOPT command for directory /DIR1 by specifying *BEGIN as the
starting date. If the system successfully copies all the eligible files, then
the dates are as follows:</p>
<ul><li>The system sets the complete starting date for backup directory /DIR1
to *BEGIN.</li>
<li>The system sets the complete ending date to 1 July 1999.</li>
</ul>
<p>If the system copied at least one file to /DIR1 as a result of this request,
the last changed date is also 1 July 1999.</p>
<p>The system does not necessarily update the last changed date and time as
the result of a successful copy. If the system did not write any files to
the backup directory, the system may update the complete range, but not the
last changed date.</p>
<p><strong>Scenario Two — Last Changed Date and Time:</strong> In the first scenario,
the backup directory /DIR1 has the following as dates after the request:</p>
<ul><li>A starting date of *BEGIN.</li>
<li>An ending date of 1 July 1999.</li>
<li>The last changed date of 1 July 1999.</li>
</ul>
<p>On 1 October 1999, the user issues the CPYOPT command again for directory
/DIR1. This time the command specifies SLTFILE(*CHANGED) to copy only the
files that have changed since the last CPYOPT request. Assume that no files
have changed since the last backup on 1 July 1999. Since no files are eligible
to copy, the system writes no files to the backup directory /DIR1. Therefore,
the last changed date remains 1 July 1999. However, since no eligible files
failed, the complete range for /DIR1 expands to have an ending date of 1 October
1999.</p>
<p>The last changed date and time becomes most important when it is set beyond
the complete range. This would happen if some files were actually copied but
other eligible files failed to copy for some reason.</p>
<p><strong>Scenario — Three Last Changed Date and Time:</strong> In Scenario Two, the
backup directory /DIR1 has the following dates after the request:</p>
<ul><li>A starting date of *BEGIN.</li>
<li>An ending date of 1 October 1999.</li>
<li>A last changed date of 1 July 1999.</li>
</ul>
<p>On 1 December 1999, the user issues the CPYOPT command again for directory
/DIR1. Assume that 10 files were changed or added to primary directory /DIR1
since the last CPYOPT request on 1 October 1999. Assume that only eight files
successfully copy to /DIR1 and that two of the eligible files failed. Since
the system did not copy all eligible files, the complete range stays the same
with a starting date of *BEGIN and an ending date of 10/1/99. However, since
/DIR1 changed, the last changed date gets updated to 1 December 1999. Since
the last changed date is outside the complete range, a complete copy of /DIR1
from *BEGIN to 1 October 1999 may not exist. A more recent copy by the change
on 1 December 1999 might have replaced one of those files.</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>