Oracle HSM (SAM-QFS): How To Verify the Drive Order Configuration Is Correct for a Directly Attached Library
Last updated on JUNE 02, 2017
Applies to:Oracle Hierarchical Storage Manager (HSM) and StorageTek QFS Software - Version 3.5 and later
Sun StorageTek Utilization Suite Software - Version 3.5 and later
Many library problems that occur when archiving for the first time are a result of drive ordering. The Sun QFS and Storage Archive Manager (SAM) software and the library must be in synchronization, so care must be taken when defining the drives in the mcf file.
When the drive ordering is not in sync between the SAM software and the library, all kinds of unexpected failures can be seen during both archiving (writing) and staging (reading) to /from the tape media because SAM will instruct the tape robotics to put a VSN into drive "A", thinking it's the drive with index "X"; once the library has mounted that VSN into drive "B" (because the order index is mismatched against what SAM has configured), SAM attempts to read drive "A" (which might or might not have a(nother) tape media loaded).
When the tapelibrary is not direct attached (via SAN, SCSI or direct attached cables) but network attached (using ACSLS software), please consult the following document : How To Verify the Drive Order Configuration Is Correct for an ACSLS-Controlled Library (Doc ID 1005607.1)
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms