Completing Backup Range: Last changed date and time
Using the CPYOPT command causes the system to write the last changed date and time of an optical backup volume or directory.
This includes any time that the system wrote files or directory attributes to the directory or volume.
The last changed date and time for that directory and volume always reflects the date and time of the request. This remains true even if the system writes a file to a backup directory.
Scenario 1: Last changed date and time
- The system sets the complete starting date for backup directory /DIR1 to *BEGIN.
- The system sets the complete ending date to 1 July 1999.
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.
Scenario 2: Last changed date and time
- A starting date of *BEGIN
- An ending date of 1 July 1999
- The last changed date of 1 July 1999
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. The last changed date and time becomes most important when it is set beyond the complete range. This happens if some files are actually copied but other eligible files failed to copy for some reason.
Scenario 3: Last changed date and time
- A starting date of *BEGIN
- An ending date of 1 October 1999
- A last changed date of 1 July 1999