If all sets on the media have exceeded their retention, the overwrite option deletes them and replaces them with the new archive sets. Unlike purge, overwrite deletes the existing sets even if there is enough space on the media for the new sets.
Jobs with overwrite selected fail if either of the following is true:
• | Any of the existing sets are still within the retention period. |
• | Overwriting the existing sets would not create enough space for the job. |
See the following topics for more details about how the overwrite option works:
The figure below illustrates a successful archive job using the overwrite option. The archive media has a capacity of 200 GB, and only 110 GB are occupied by Sets 1 and 2. The current job is writing Set 3 to the media. Set 3 is 40 GB, so there is enough space on the media for the current job without deleting Sets 1 and 2. However, because overwrite has been selected for the job, all existing sets on the media are deleted when Set 3 is written. Unlike the purge option, the overwrite option deletes archive sets even when enough space is available for the current job.
The figure below illustrates a failed attempt to run an archive job with the overwrite option. The archive media has a capacity of 200 GB, and only 110 GB are occupied by Sets 1 and 2. The current job is writing Set 3 to the media. Set 3 is 40 GB, so there is enough space on the media for the current job without deleting Sets 1 and 2. However, the job fails because overwrite has been selected and Set 2 has not exceeded its retention period. There is no impact on the archive media. A job with overwrite selected succeeds only if all sets in the media have exceeded their retention periods.