HSM - Not Staging From "copysel" Defined Order During 'rearch' Process
(Doc ID 2595024.1)
Last updated on JULY 08, 2022
Applies to:
Oracle Hierarchical Storage Manager (HSM) and StorageTek QFS Software - Version 4.0 to 6.1 [Release 4.0 to 6.0]Information in this document applies to any platform.
Goal
Does 'rearch' use the stager.cmd "copysel" setting when selecting the archive copy for staging?
Background:
=========
The site has a stager.cmd file setting that specifies a specific order for file system samFS. The order specified in stager.cmd is 3,1,2,4:
During rearchiving, the rearch process selects copy=2, which is a tape archive copy, instead of copy=3, which is the desired disk archive copy.
At this site, copy 1 and copy 3 are disk archives; copy 2 is tape archive. The customer would like to rearch damaged archive copies and it is faster to stage the copies from disk rather than from tape. He has a program that reads file information about the damaged files and rearchive the files according to parameters specified in the program.
Solution
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
Goal |
Solution |