The concept of a scratch pool in ACSLS is simply a blank tape. Once a tape has been
mounted in a
permanent
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
library. When talking with an ACSLS tape library, Oracle Secure Backup uses two
daemons
which is responsible for communications with the ACSLS server.
Drive Association
When you install a
requires that you attach the tape drive to a
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
ACSLS always identifies a
associates this barcode with a
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
ACSLS supports virtual tapes that do not have a physical
Note:
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.
tape
drive, its scratch pool identity is removed, and it acquires a
family, identical in functionality to the pre-labeling volumes. Oracle
media
named obacslibd and obacsssid. The obacslibd daemon spawns obacsssid,
tape drive
other than an ACS tape drive, Oracle Secure Backup
volume
volume
media
server, install an appropriate
tape drive
by its barcode. Because Oracle Secure Backup
ID, you can supply either one. If a mapping is
Oracle Secure Backup and ACSLS D-3
Imports and Exports
tape
name.
Need help?
Do you have a question about the Secure Backup and is the answer not in the manual?