SAM-QFS: How tplabel Can Cause Unexpected or Duplicate Catalog Entries
(Doc ID 1557025.1)
Last updated on AUGUST 02, 2019
Applies to:Oracle Hierarchical Storage Manager (HSM) and StorageTek QFS Software - Version 5.0 and later
Information in this document applies to any platform.
Each SAM-QFS tape volume starts with a label, containing some metadata about the tape volume (ex : the Volume Label, date of last (re)label, ...). When SAM-QFS is configured to use barcodes as the label (see note) it is expected that SAM-QFS will label a new tape automatically upon first usage or re-label the tape volume whenever the recycler.sh(1M) script decides that it's safe to do so after a recycler(1M) run. The tplabel(1M) command can be used to manually label or re-label a tape volume and in the process, one can create unexpected results or even duplicate volumes, corrupting the catalog. It's worth knowing that the dump_cat(1M) command and the samcmd v output will show the barcode as the tape label, even when a tape was never labeled before
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