After Setup Legato Single Server, you can use "inquire" to query devices, and then use "jbconfig" to install them.
C:\PROGRA~1\nsr\bin>inquire
scsidev@0.0.0:LG CD-ROM CRD-8482B1.05|CD-ROM
scsidev@1.0.0:MEGARAID LD 0 RAID 1 1.01|Disk, \\.\PHYSICALDRIVE0
scsidev@1.1.0:MEGARAID LD 1 RAID 5 1.01|Disk, \\.\PHYSICALDRIVE1
scsidev@3.6.0:DELL PERC 2/DC 1.01|Processor
scsidev@3.15.0:Dell |Processor
scsidev@4.0.0:FUJITSU MAJ3182MC 5509|Disk
scsidev@4.6.0:DELL 1x8 U2W SCSI BP 5.43|Processor
scsidev@6.3.0:HP C5713A H107|Tape, \\.\Tape0
scsidev@6.3.1:HP C5713A H107|Autochanger (Jukebox), \\.\Changer0
C:\PROGRA~1\nsr\bin>jbconfig
1) Install a SmartMedia Jukebox.
2) Install an Autodetected SCSI Jukebox.
3) Install an Autodetected NDMP SCSI Jukebox.
4) Install an SJI Jukebox.
5) Install an STL Silo.
6) Install a Microsoft Removable Storage Jukebox.
What kind of Jukebox are you installing? [1] 2
These are the SCSI Jukeboxes currently attached to your system:
1) scsidev@6.3.1: HP C5713A
Which one do you want to install? 1
Installing an 'HP C5713A' jukebox.
Name you would like to assign to the jukebox device? HPC5713A
A brief description of the jukebox device? [scsidev@6.3.1: HP C5713A]
Pathname of the control port for the jukebox device? [scsidev@6.3.1]
Do you want automated device cleaning support enabled? (yes/no) yes
Will media drive 1 be shared by multiple device paths? (yes/no) yes
Since this drive will be shared, you will be asked for a hardware id,
which uniquely identifies the drive. Each device path that shares the
drive will be given the same hardware id value. When a device has a
hardware id value, its messages will contain a number that uniquely
represents the hardware id. This number is visible in administrator
programs, such as nwadmin.
Enter hardware id for media drive 1: ? [HPC5713A drive-1] HP5713A1
You've entered 'HP5713A1'. Continue with this hardware id? (yes/no) yes
Enter hostname that owns device path 1 for media drive 1: ? [svrtest2.nwxy.com]
Enter pathname of device 1 for media drive 1: ? [\\.\Tape0]
using '\\.\Tape0' as device name
Should the drive be configured as a NDMP device? (yes/no) no
This media device has not been configured yet. Please
select a media device type for \\.\Tape0.
1) 3480 23) dst (NT)
2) 3570 24) dtf
3) 3590 25) file
4) 4890 26) filesys
5) 4mm 27) himt
6) 4mm 12GB 28) logical
7) 4mm 20GB 29) LTO Ultrium
8) 4mm 4GB 30) optical
9) 4mm 8GB 31) qic
10) 8mm 32) SD3
11) 8mm 20GB 33) sdlt
12) 8mm 5GB 34) SLR
13) 8mm AIT 35) tkz90
14) 8mm AIT-2 36) travan10
15) 8mm Mammoth-2 37) tz85
16) 9490 38) tz86
17) 9840 39) tz87
18) 9940 40) tz88
19) dlt 41) tz89
20) dlt1 42) tzs20
21) dlt7000 43) VXA
22) dlt8000
Choice? 5
Any more device paths for media drive 1? (yes/no)
Your jukebox has a bar code reader.
Do you want bar code reader support enabled? (yes/no) no
Following are attributes that define cleaning cartridge support
for the jukebox `HPC5713A':
auto clean: Yes
default cleanings: 25
cleaning slots: 6
Cleaning cartridge volumes Slot number
-------------------------- -----------
Cleaning Tape (25 uses left) 6
Make sure that the slots set aside for cleaning cartridges
contain cleaning cartridges. Networker must know the number
of times it can use each cleaning cartridge. You can
control how many times Networker will use each cleaning
cartridge by using the command -
nsrjb -U (number of uses) -S (slot number)
For more details please refer to nsrjb man pages.
Following are attributes that define the cleaning
schedule for each device in the jukebox.
name: \\.\Tape0
date last cleaned:
cleaning interval: 2 weeks
cleaning required: No
Verify that the values for these attributes are appropriate
for your installation. If not check documentation on how to
set up automated cleaning cartridge support.
Jukebox has been added successfully
Would you like to configure another jukebox? (yes/no) no
After Configured , you can use RMAN to test the database backup.
C:\>rman target sys/oracle@ev_old catalog rman/rman@rmandb
Recovery Manager: Release 9.2.0.1.0 - Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
connected to target database: ORATEST (DBID=3155607277)
connected to recovery catalog database
RMAN> run {
2> allocate channel x1 type 'SBT_TAPE';
3> backup tablespace tools;
4> release channel x1;
5> }
allocated channel: x1
channel x1: sid=34 devtype=SBT_TAPE
channel x1: NMO v3.5.0.1
Starting backup at 12-JUN-07
channel x1: starting full datafile backupset
channel x1: specifying datafile(s) in backupset
input datafile fno=00004 name=Y:\ORACLE\ORADATA\ORATEST\TOOLS01.DBF
channel x1: starting piece 1 at 12-JUN-07
channel x1: finished piece 1 at 12-JUN-07
piece handle=0bik3j0e_1_1 comment=API Version 2.0,MMS Version 3.5.0.1
channel x1: backup set complete, elapsed time: 00:19:25
Finished backup at 12-JUN-07
released channel: x1
RMAN>