Imports and Exports
Oracle Secure Backup and ACSLS D-3
The concept of a scratch pool in ACSLS is simply a blank tape. Once a tape has been
mounted in a tape drive, its scratch pool identity is removed, and it acquires a
permanent media family, identical in functionality to the pre-labeling volumes. Oracle
Secure Backup supports scratch pools through an extension to the media family and
retains this concept through the existing media family functionality. In addition, when
a volume is force unlabeled it is moved back into the scratch pool that is assigned to
the media family.
ACSLS has optional access control mechanisms on commands and volumes. This
optional access control user ID can be defined as part of the mkdev or chdev
commands.
Because an ACSLS system is meant to be shared by multiple clients, tape drive
cleaning is managed and maintained by ACSLS.
Communicating with ACSLS
Oracle Secure Backup uses the obrobotd daemon when talking to a non-ACSLS tape
library. When talking with an ACSLS tape library, Oracle Secure Backup uses two
daemons named obacslibd and obacsssid. The obacslibd daemon spawns obacsssid,
which is responsible for communications with the ACSLS server.
Drive Association
When you install a tape drive other than an ACS tape drive, Oracle Secure Backup
requires that you attach the tape drive to a media server, install an appropriate
operating system driver for the tape drive, create a device within Oracle Secure
Backup, and map the operating system device to the Oracle Secure Backup device. The
same steps are required for ACSLS. But you must also further define the ACSLS
mapping of the tape drive through the mkdev or chdev command. The additional
information required is the acs, lsm, panel, and drive.
Volume Loading and Unloading
Drive identification for mounts and dismounts is by tape drive name.
ACSLS always identifies a volume by its barcode. Because Oracle Secure Backup
associates this barcode with a volume ID, you can supply either one. If a mapping is
not possible, then the request is rejected with appropriate logging.
Imports and Exports
The exportvol command has been modified to conform to ACSLS usage. Individual
ACS cartridge access port (CAP) slots are not addressable, although an entire CAP can
be selected based on CAP name.
Once the request is made to eject the tape, the request does not return until the CAP
has been opened, the cartridge loader emptied, and the cartridge loader reinserted in
Note: ACSLS supports virtual tapes that do not have a physical
barcode attached to them. Oracle Secure Backup does not support
virtual tapes within an ACS system. Oracle Secure Backup requires
that all cartridges within an ACS system have properly affixed and
readable barcodes.
To Next Page
Need help?
General