Oracle HSM: Archiver Creates Undesired Archive Set Copies
(Doc ID 2113973.1)
Last updated on AUGUST 30, 2017
Applies to:Oracle Hierarchical Storage Manager (HSM) and StorageTek QFS Software - Version 5.4 and later
Information in this document applies to any platform.
In general the customer in this example has archive copies #1 and #2 on tape and archive copy #3 on disk.
For one particular filesystem, "samfs1", they want ONLY the disk copy #3 and NO tape copies (#1 and #2).
For this they tried having this archive set definition entry in their archiver.cmd:
The last line above shows it would create an undesired tape copy #1, in addition to the defined disk copy #3.
Having the archiver define a copy 1, when configured as in the above example, is expected behavior. Any files that don't match archive set specifications will be assigned to the default copy 1 archive set for that file system (samfs1.1).
The solution below explains how we prevent the archiver from creating a disk copy #1 for this file system.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document