Hello Fazil,
Some tips in raw format :
1) Server and Storage node must run the same networker version
On Each node connected to the san, disable Windows Removable Service.
2) Comparing Server and storage node devices, use inquire
and gather device name based on device serial number and LUN.
3) Look then at library for determining which physical tape
device <-> serial number, in order to determine which physical
device is mapped to lib dev 0 and so on.
4) Build then a map such :
Take care Storage node may discover \\.\tapexxx naming
differently.
Lib Drive Device SN Server device name SN device name
Robotic .......... [email protected] [email protected]
#0 F001B5F001 \\.\tape0 SN:\\.\tape1
[email protected] [email protected]
#1 F001B5F002 \\.\tape3 SN:\\.\tape0
[email protected] [email protected]
...
Believe me, this will a great help when some troubleshooting
has to be done when device name changed.
I suggest you to look at persistent binding to avoid
device presentation to change at each reboot and/or
to SAN Zoning if not all devices have to be presented to
all SAN connected servers.
Then use Jbconfig based on above mattrix.
About your problem, I believe the mapping between physical
tape device (drive order in the lib) does not match the
discovered device order :
from inquire :
[email protected]:IBM ULTRIUM-TD2 53Y2|Tape, \\.\Tape0
[email protected]:IBM ULTRIUM-TD2 53Y2|Tape, \\.\Tape1
[email protected]:IBM ULTRIUM-TD2 53Y2|Tape, \\.\Tape6
[email protected]:IBM ULTRIUM-TD2 53Y2|Tape, \\.\Tape7
[email protected]:IBM ULTRIUM-TD2 53Y2|Tape, \\.\Tape2
[email protected]:IBM ULTRIUM-TD2 53Y2|Tape, \\.\Tape3
[email protected]:IBM ULTRIUM-TD2 53Y2|Tape, \\.\Tape4
[email protected]:IBM ULTRIUM-TD2 53Y2|Tape, \\.\Tape5
>From jbconfig :
Drive 1, element 256
Device path 1 ? \\.\Tape0
Device path 2 ? storagenode1:\\.\Tape0
Drive 2, element 257
Device path 1 ? \\.\Tape1
Device path 2 ? storagenode1:\\.\Tape1
Drive 3, element 258
Device path 1 ? \\.\Tape2
Drive 4, element 259
Device path 1 ? \\.\Tape3
Drive 5, element 260
Device path 1 ? \\.\Tape4
Drive 6, element 261
Device path 1 ? \\.\Tape5
Drive 7, element 262
Device path 1 ? \\.\Tape6
Drive 8, element 263
Device path 1 ? \\.\Tape7
eg : if [email protected] is device #7 in your lib (starting from 0)
Networker is configured for using \\.\Tape7.
Looing at inquire output, \\.\tape7 is assigned to discovered
device at addr 7.0.4.
In this case, Networker will put a tape in physical library
device 7 but \\.\tape7 will report "no media in drive"
and fail to unload the tape because volume is still loaded
into the device.
BTW, it is normal devices to fail back in service mode : when
networker tries and retries and retries to load/eject a tape,
it increases a counter (max consecutive error, from resource device).
When reached the limit (20 by def), it decides the device has a problem
and turn it to service, for safety.
HTH,
TH
Kind regards - Bien cordialement - Vriendelijke groeten,
Thierry FAIDHERBE
HP Services - Storage Division
Tru64 Unix and Legato Enterprise Backup Solutions Consultant
********* ********* HEWLETT - PACKARD
******* h ******* 1 Rue de l'aeronef/Luchtschipstraat
****** h ****** 1140 Bruxelles/Brussel/Brussels
***** hhhh pppp *****
***** h h p p ***** 100/102 Blv de la Woluwe/Woluwedal
***** h h pppp ***** 1200 Bruxelles/Brussel/Brussels
****** p ****** BELGIUM
******* p *******
********* ********* Phone : +32 (0)2 / 729.85.42
Mobile : +32 (0)498/ 94.60.85
Fax : +32 (0)2 / 729.88.30
I N V E N T Email/MSN : thierry.faidherbe(at)hp.com
Internet : http://www.hp.com/
-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]
On Behalf Of Fazil Saiyed
Sent: Tuesday, March 28, 2006 3:43 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] DDS_Storage Node Help
Hello,
I figured out most of the DDS & Storage Node config, however, i am
having
one issue.
Here is output from Master server & SN, i was able to create and
configure
the lib just fine, however, the remote divices are not working right,
they
have read errors, devices in use error and one of the drives went in
service mode, not sure why this is hapenning, all the indication are
that
the divices are loaded right, created right, drivers are fine.what might
cause this, the first two drives on this list are shared out with DDS.
D:\nsr\bin>inquire
Could not start a Removable Storage session (0x00000422).
[email protected]:HL-DT-STCDRW/DVD GCC4244B101|CD-ROM
[email protected]:ADIC Scalar i2000 300A|Autochanger (Jukebox)
S/N: ADIC203101904_LL0
ATNN:ADIC 203101904_LL0
[email protected]:IBM ULTRIUM-TD2 53Y2|Tape, \\.\Tape0
[email protected]:IBM ULTRIUM-TD2 53Y2|Tape, \\.\Tape1
[email protected]:IBM ULTRIUM-TD2 53Y2|Tape, \\.\Tape6
[email protected]:IBM ULTRIUM-TD2 53Y2|Tape, \\.\Tape7
[email protected]:IBM ULTRIUM-TD2 53Y2|Tape, \\.\Tape2
[email protected]:IBM ULTRIUM-TD2 53Y2|Tape, \\.\Tape3
[email protected]:IBM ULTRIUM-TD2 53Y2|Tape, \\.\Tape4
[email protected]:IBM ULTRIUM-TD2 53Y2|Tape, \\.\Tape5
[email protected]:PE/PV 1x5 SCSI BP 1.0 |Processor
[email protected]: RAID DummyDevice 0000|Unknown Device Type
[email protected]:PERC LD 0 PERCRAID |Disk
[email protected]:PERC LD 1 PERCRAID |Disk
+++++++++++++++
D:\nsr\bin>inquire
Could not start a Removable Storage session (0x00000422).
[email protected]:COMPAQ CD-ROM SC-140C cq04|CD-ROM
[email protected]:IBM ULTRIUM-TD2 53Y2|Tape, \\.\Tape0
S/N: F001B5F001
ATNN:IBM ULTRIUM-TD2
F001B5F0
01
WWNN:500308C001B5F001
[email protected]:IBM ULTRIUM-TD2 53Y2|Tape, \\.\Tape1
S/N: F001B5F007
ATNN:IBM ULTRIUM-TD2
F001B5F0
07
WWNN:500308C001B5F007
[email protected]:COMPAQ SCSI COMMUNICATECISS|Unknown Device Type
[email protected]:COMPAQ LOGICAL VOLUME 3.54|Disk, \\.\PHYSICALDRIVE0
WWNN:600508B100105944414E4A4158530003
[email protected]:COMPAQ LOGICAL VOLUME 3.54|Disk, \\.\PHYSICALDRIVE1
WWNN:600508B100105944414E4A4158530004
+++++++++++++
D:\nsr\bin>jbconfig
1) Configure an AlphaStor/SmartMedia Jukebox.
2) Configure an Autodetected SCSI Jukebox.
3) Configure an Autodetected NDMP SCSI Jukebox.
4) Configure an SJI Jukebox.
5) Configure an STL Silo.
6) Configure a Microsoft Removable Storage Jukebox.
What kind of Jukebox are you configuring? [1] 2
Installing 'Standard SCSI Jukebox' jukebox - [email protected].
What name do you want to assign to this jukebox device? ADIC
Turn NetWorker auto-cleaning on (yes / no) [yes]? y
The drives in this jukebox cannot be auto-configured with the available
information. You will need to provide the path for the drives.
Is (any path of) any drive intended for NDMP use? (yes / no) [no] n
Is any drive going to have more than one path defined? (yes / no) [no] y
You will be prompted for multiple paths for each drive.
Pressing <Enter> on a null default advances to the next drive.
Please enter the device path information in one of the following
formats:
\\.\Tape0 --for local path or
host:device-path --for remote node or
host:drive-letter:directory path --for Windows disk file
Drive 1, element 256
Device path 1 ? \\.\Tape0
Device path 2 ? storagenode1:\\.\Tape0
Device path 3 ?
Drive 2, element 257
Device path 1 ? \\.\Tape1
Device path 2 ? storagenode1:\\.\Tape1
Device path 3 ?
Drive 3, element 258
Device path 1 ? \\.\Tape2
Device path 2 ?
Drive 4, element 259
Device path 1 ? \\.\Tape3
Device path 2 ?
Drive 5, element 260
Device path 1 ? \\.\Tape4
Device path 2 ?
Drive 6, element 261
Device path 1 ? \\.\Tape5
Device path 2 ?
Drive 7, element 262
Device path 1 ? \\.\Tape6
Device path 2 ?
Drive 8, element 263
Device path 1 ? \\.\Tape7
Device path 2 ?
Please select the appropriate drive type number:
1) 3480 20) 9490 39) LTO Ultrium-3
2) 3570 21) 9840 40) optical
3) 3590 22) 9840b 41) qic
4) 3592 23) 9840C 42) SAIT-1
5) 4890 24) 9940 43) SD3
6) 4mm 25) 9940B 44) sdlt
7) 4mm 12GB 26) adv_file 45) sdlt320
8) 4mm 20GB 27) dlt 46) sdlt600
9) 4mm 4GB 28) dlt1 47) SLR
10) 4mm 8GB 29) dlt7000 48) tkz90
11) 4mm DAT72 30) dlt8000 49) travan10
12) 8mm 31) dst (NT) 50) tz85
13) 8mm 20GB 32) dtf 51) tz86
14) 8mm 5GB 33) dtf2 52) tz87
15) 8mm AIT 34) file 53) tz88
16) 8mm AIT-2 35) himt 54) tz89
17) 8mm AIT-3 36) logical 55) tz90
18) 8mm AIT-4 37) LTO Ultrium 56) tzs20
19) 8mm Mammoth-2 38) LTO Ultrium-2 57) VXA
Enter the drive type of drive 1? 38
Are all the drives the same model? (yes / no) [yes] y
A Dedicated Storage Node can backup only local data to its devices.
Should storagenode1 be configured as a Dedicated Storage Node? (yes /
no)
[no] n
o
Jukebox has been added successfully
The following configuration options have been set:
> Jukebox description to the control port and model.
> Autochanger control port to the port at which we found it.
> Networker managed tape autocleaning on.
> At least one drive was defined with multiple paths. All such
drives
are
defined with a hardware identification as well as a path value to
avoid
confusion by uniquely identifying the drive. The hardware
identification
for all drives which have one is always 'autochanger_name - Drive
#'
where
"autochanger_name" is the name you gave to the autochanger that was
just defined, and the # symbol is the drive numer.
> Barcode reading to on.
> Volume labels that match the barcodes.
> Slot intended to hold cleaning cartridge to 102. Please insure
that a
cleaning cartridge is in that slot
> Number of times we will use a new cleaning cartridge to 50.
> Cleaning interval for the tape drives to 6 months.
You can review and change the characteristics of the autochanger and its
associated devices using nwadmin.
Would you like to configure another jukebox? (yes/no) [no]
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the
body of the email. Please write to networker-request AT listserv.temple DOT edu
if you have any problems
wit this list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the
body of the email. Please write to networker-request AT listserv.temple DOT edu
if you have any problems
wit this list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|
