when i tried to backup on the library, netbackup console shows me " ROBOTHIC LIBRARY IS DOWN ON SERVER"
the master server runs on Red Hat 5.6
The OS detect the path of the library, but Netbackup doesn't detect it.
Please paste the output for the command,
tpautoconf -t and
scan -tape
The screen shot is too small to see. WIth all respect to Gopi, I'm not sure how tpautoconf -t and scan -tape will help, its a robot issue, not a tape issue.
However, I suggest:
Run scan output (not scan -tape) - do you see the library. You should see the library and any tape drives attached.
If the library is there, I would take the path it shows scan contacted the library and received a reply.
I would then delete the librray from NBU and re-run the device wizard. Move the tapes to none-robotic and re-inventory. Alternatively, you could delete the drives as well and just add the whole lot back, which woud be my preference personally. However, if you have many drives shared across many media servers, this is a bit more work.
Persistent binding (set via the HBA utility (eg sansurfer or hnAnywhere depending of if the card is qlogic or Emulex)) should prevent this happening again.
My bad. I was working on a similar issue and posted it.
Thanks for notifying Martin.
Hi Npalma, google for:
Tape backup failures when qlogic HBA feature target reset enabled
please check:
https://www-secure.symantec.com/connect/forums/drives-going-avr-mode-after-zoning-changes-san
Basically you need to get rid of this feature. To do so yo need the hba configuration utility like sansurfer and and unmark the feature.
This technote :https://access.redhat.com/solutions/387783 is similar.
When the feature is activated robotique failures occurs ramdomly like for example when you run the configuration wizard to rescan you config again, you will loose conectivity to your drives, or by using the reset function when a tape is in the library and so on.
Another quote: from http://support.qlogic.com/SupportCenter/Customer_Support_main?id=90680000000CbOPAA0
And this is what i was looking for ( thanks)
best regards,
Cruisen
This is not a library FC, is a ISCSI library,
the output of the command is( tpautoconf -t & scan -tape):
[root@backup6m-bkp ~]# /usr/openv/volmgr/bin/tpautoconf -t
TPAC60 IBM ULT3580-HH5 D2AD 1068017271 -1 -1 -1 -1 /dev/nst2 - -
TPAC60 IBM ULT3580-HH5 D2AD 1068017282 -1 -1 -1 -1 /dev/nst0 - -
TPAC60 IBM ULT3580-HH5 D2AD 1068017282 -1 -1 -1 -1 /dev/nst1 - -
TPAC60 IBM ULT3580-HH5 D2AD 1068017271 -1 -1 -1 -1 /dev/nst3 - -
[root@backup6m-bkp ~]# scan -tape
-bash: scan: command not found
[root@backup6m-bkp ~]# /usr/openv/volmgr/bin/scan -tape
************************************************************
*********************** SDT_TAPE ************************
************************************************************
------------------------------------------------------------
Device Name : "/dev/nst2"
Passthru Name: "/dev/sg4"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry : "IBM ULT3580-HH5 D2AD"
Vendor ID : "IBM "
Product ID : "ULT3580-HH5 "
Product Rev: "D2AD"
Serial Number: "1068017271"
WWN : ""
WWN Id Type : 0
Device Identifier: "IBM ULT3580-HH5 1068017271"
Device Type : SDT_TAPE
NetBackup Drive Type: 10
Removable : Yes
Device Supports: SCSI-6
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name : "/dev/nst0"
Passthru Name: "/dev/sg2"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry : "IBM ULT3580-HH5 D2AD"
Vendor ID : "IBM "
Product ID : "ULT3580-HH5 "
Product Rev: "D2AD"
Serial Number: "1068017282"
WWN : ""
WWN Id Type : 0
Device Identifier: "IBM ULT3580-HH5 1068017282"
Device Type : SDT_TAPE
NetBackup Drive Type: 10
Removable : Yes
Device Supports: SCSI-6
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name : "/dev/nst1"
Passthru Name: "/dev/sg3"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry : "IBM ULT3580-HH5 D2AD"
Vendor ID : "IBM "
Product ID : "ULT3580-HH5 "
Product Rev: "D2AD"
Serial Number: "1068017282"
WWN : ""
WWN Id Type : 0
Device Identifier: "IBM ULT3580-HH5 1068017282"
Device Type : SDT_TAPE
NetBackup Drive Type: 10
Removable : Yes
Device Supports: SCSI-6
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name : "/dev/nst3"
Passthru Name: "/dev/sg5"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry : "IBM ULT3580-HH5 D2AD"
Vendor ID : "IBM "
Product ID : "ULT3580-HH5 "
Product Rev: "D2AD"
Serial Number: "1068017271"
WWN : ""
WWN Id Type : 0
Device Identifier: "IBM ULT3580-HH5 1068017271"
Device Type : SDT_TAPE
NetBackup Drive Type: 10
Removable : Yes
Device Supports: SCSI-6
Flags : 0x0
Reason: 0x0
[root@backup6m-bkp ~]#
I also added (mt -f):
[root@backup6m-bkp ~]# mt -f /dev/nst0 status
SCSI 2 tape drive:
File number=-1, block number=-1, partition=0.
Tape block size 0 bytes. Density code 0x0 (default).
Soft error count since last status=0
General status bits on (50000):
DR_OPEN IM_REP_EN
[root@backup6m-bkp ~]# mt -f /dev/nst1 status
SCSI 2 tape drive:
File number=-1, block number=-1, partition=0.
Tape block size 0 bytes. Density code 0x0 (default).
Soft error count since last status=0
General status bits on (50000):
DR_OPEN IM_REP_EN
[root@backup6m-bkp ~]# mt -f /dev/nst2 status
SCSI 2 tape drive:
File number=-1, block number=-1, partition=0.
Tape block size 0 bytes. Density code 0x0 (default).
Soft error count since last status=0
General status bits on (50000):
DR_OPEN IM_REP_EN
[root@backup6m-bkp ~]# mt -f /dev/nst3 status
SCSI 2 tape drive:
File number=-1, block number=-1, partition=0.
Tape block size 0 bytes. Density code 0x0 (default).
Soft error count since last status=0
General status bits on (50000):
DR_OPEN IM_REP_EN
Thanks Marianne:
The output of the command is
[root@backup6m-bkp ~]# /usr/openv/volmgr/bin/scan -changer
************************************************************
*********************** SDT_CHANGER ************************
************************************************************
[root@backup6m-bkp ~]#
Thanks Marianne: Thans Marianne: Ours was reset by the management console from the library , but it was necessary , a physical reboot . With this + the master server reboot , we have recovered the connection. Best regards.
PROBLEM: When the SCSI bus target (the tape drive) is reset when a backup job is running, the
backup job aborts. Since the tape drive does not receive the rewind and unload commands from
the backup job, it leaves the tape in the drive, causing the drive to be seen as not ready and then
be marked offline in the backup application when the next job tries to use the drive