|Oracle® Secure Backup Installation Guide
Part Number B14235-02
After you have established your administrative domain, you can configure any attached libraries and tape drives. Oracle Secure Backup supports both SCSI and Fibre Channel-connected devices, as well as NAS libraries and tape drives. Names for Oracle Secure Backup devices are user-defined.
In the following example, assume you have a combined administrative server and media server called
BELLA with an attached library named
obl0 and tape drive named
obt0. The example uses
obtool commands for device configuration, although you can also use the Oracle Secure Backup Web tool or Oracle Enterprise Manager to assign Oracle Secure Backup device names.
Note:Disable any system software that scans and opens arbitrary SCSI targets before configuring Oracle Secure Backup tape devices. If Oracle Secure Backup has to contend with other system software (such as monitoring software) for access to tape libraries and drives, then unexpected behavior can result.
If you are already logged on to Oracle Secure Backup, skip to Step 3.
Otherwise, log on to Windows as the Administrator user or as a user that is a member of the Administrators group.
To open Oracle Secure Backup, click the Start button and select Programs, Oracle Secure Backup, and Oracle Secure Backup Command Line Interface.
ob> prompt displays.
Create an Oracle Secure Backup device object and assign it a user-defined name for the tape library. Specify options for the device type and media server. The following example assigns the name
tc-lib to tape library
ob> mkdev --type library --attach BELLA://./obl0 tc-lib
Create an Oracle Secure Backup device object and assign it a user-defined name for the tape drive. The following example assigns the name
tc-tape to tape drive
ob> mkdev --type tape --library tc-lib --dte 1 --attach BELLA://./obt0 tc-tape
Note:Oracle Secure Backup identifies each tape drive within a library by its data transfer element (DTE) number. You must specify a
Check configuration information for both devices. For example:
ob> lsdev -l
In this example, the command displays the following output:
tc-lib: Device type: library Model: [none] In service: yes Debug mode: no Barcode reader: default (hardware-selected) Barcodes required: no Auto clean: no Clean interval: (not set) Clean using emptiest: no UUID: ca196e5e-af6d-4978-9172-3dadb5d50ec7 Attachment 1: Host: BELLA Raw device: //./obl0 tc-tape: Device type: tape Model: [none] In service: yes Library: tc-lib DTE: 1 Automount: yes Error rate: 8 Query frequency: 1207KB (1236976 bytes) (from driver) Debug mode: no Blocking factor: (default) Max blocking factor: (default) Current tape: 2 Use list: all Drive usage: none Cleaning required: no UUID: d367a0dd-549c-4b99-9557-d9fc16d9d2c5 Attachment 1: Host: BELLA Raw device: //./obt0
Note:Device special files for tape libraries are named