04-15-2013 09:40 AM
Netbackup version: 7.x
OS: win server 2003
Two drives went down in my environment and all effort to up the drives flag an error "unable to up selected drive: , unknow drive name (297)
Please see attachment. I need help.
Solved! Go to Solution.
04-15-2013 02:02 PM
My recommendation: delete the drives/robots from the NBU setup. Then, especially if you have made any changes to LUN mapping or FC Host changes, be sure to power cycle the i500's I/O blade(s), then let Windows rediscover the devices at the OS level. Once you see all the devices again in Windows, let NetBackup rediscover them.
I've been having a similar issue and it required the Quantum's I/O blades to be power-cycled before all the changes were visible to the media server's OS.
04-15-2013 09:59 AM
Run the following command from the command line:
c:
cd program files\veritas\volmgr\bin
scan
do you see the drives?
04-15-2013 10:37 AM
From the device monitor, i can see the drives. also tpconfig -d command return the two drives as DOWN STATE. I also noticed tapes are stuck in the drives. I initiate robtest test to move the tapes to an empty slots, but the drives are still displaying the presence of ejected tapes on it. Please advice. thank you.
04-15-2013 11:08 AM
Could you answer revaroos question, what does scan show ?
Also, you say the drives are still showing 'ejected tapes' after you try to move them in robtest. I presume you see this in robtest.
If so, it would appear you have an issue physically with the drives. If you cannot move the tapes in robtest, NBU has no chance.
I would recommend you physically check the drives and remove the tapes by hand, put them back into empty slots in the library, and then make the library run an inventory (it will probably do this if you open/ close the door). If you are unsure, a power cycle of the librray usually causes an inventory, or, start one from the library web console if available.
After this, run an inventory in NetBackup, then retest.
If the issue repeats, you have a tape or drive issue and will require hardware support.
But this does not fully explain the message of unknown drive name.
Persoanlly, I would do the above, and then delete the drives from NetBackup and readd using the wizard.
Martin
04-15-2013 12:27 PM
Ravaroos, here is the out put from scan command:
s d
drive 1 (addr 256) access = 1 Contains Cartridge = no
drive 2 (addr 257) access = 1 Contains Cartridge = no
drive 3 (addr 258) access = 1 Contains Cartridge = no
drive 4 (addr 259) access = 0 Contains Cartridge = yes
Source address = 4224 (slot 129)
Barcode = 000676L4
drive 5 (addr 260) access = 1 Contains Cartridge = no
drive 6 (addr 261) access = 1 Contains Cartridge = no
drive 7 (addr 262) access = 1 Contains Cartridge = no
drive 8 (addr 263) access = 1 Contains Cartridge = no
drive 9 (addr 264) access = 1 Contains Cartridge = no
drive 10 (addr 265) access = 1 Contains Cartridge = no
READ_ELEMENT_STATUS complete
C:\Program Files\Veritas\Volmgr\bin>scan
************************************************************
*********************** SDT_TAPE ************************
*********************** SDT_CHANGER ************************
************************************************************
------------------------------------------------------------
Device Name : "Tape5"
Passthru Name: "Tape5"
Volume Header: ""
Port: 2; Bus: 0; Target: 0; LUN: 0
Inquiry : "IBM ULTRIUM-TD4 B7C0"
Vendor ID : "IBM "
Product ID : "ULTRIUM-TD4 "
Product Rev: "B7C0"
Serial Number: "F09D14B094"
WWN : ""
WWN Id Type : 0
Device Identifier: "IBM ULTRIUM-TD4 F09D14B094"
Device Type : SDT_TAPE
NetBackup Drive Type: 3
Removable : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name : "Tape6"
Passthru Name: "Tape6"
Volume Header: ""
Port: 2; Bus: 0; Target: 1; LUN: 0
Inquiry : "IBM ULTRIUM-TD4 B7C0"
Vendor ID : "IBM "
Product ID : "ULTRIUM-TD4 "
Product Rev: "B7C0"
Serial Number: "F09D14B098"
WWN : ""
WWN Id Type : 0
Device Identifier: "IBM ULTRIUM-TD4 F09D14B098"
Device Type : SDT_TAPE
NetBackup Drive Type: 3
Removable : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name : "Changer0"
Passthru Name: "Changer0"
Volume Header: ""
Port: 2; Bus: 0; Target: 2; LUN: 1
Inquiry : "ADIC Scalar i500 590G"
Vendor ID : "ADIC "
Product ID : "Scalar i500 "
Product Rev: "590G"
Serial Number: "ADICA0C0078002_LLA"
WWN : ""
WWN Id Type : 0
Device Identifier: "ADIC A0C0078002_LLA "
Device Type : SDT_CHANGER
NetBackup Robot Type: 8
Removable : Yes
Device Supports: SCSI-3
Number of Drives : 10
Number of Slots : 187
Number of Media Access Ports: 30
Drive 1 Serial Number : "F09D14B090"
Drive 2 Serial Number : "F09D14B094"
Drive 3 Serial Number : "F09D14B098"
Drive 4 Serial Number : "F09D14B09C"
Drive 5 Serial Number : "F09D14B000"
Drive 6 Serial Number : "F09D14B004"
Drive 7 Serial Number : "F09D14B010"
Drive 8 Serial Number : "F09D14B014"
Drive 9 Serial Number : "F09D14B018"
Drive 10 Serial Number : "F09D14B01C"
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name : "Tape8"
Passthru Name: "Tape8"
Volume Header: ""
Port: 2; Bus: 0; Target: 3; LUN: 0
Inquiry : "IBM ULTRIUM-TD4 B7C0"
Vendor ID : "IBM "
Product ID : "ULTRIUM-TD4 "
Product Rev: "B7C0"
Serial Number: "F09D14B010"
WWN : ""
WWN Id Type : 0
Device Identifier: "IBM ULTRIUM-TD4 F09D14B010"
Device Type : SDT_TAPE
NetBackup Drive Type: 3
Removable : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name : "Tape9"
Passthru Name: "Tape9"
Volume Header: ""
Port: 2; Bus: 0; Target: 4; LUN: 0
Inquiry : "IBM ULTRIUM-TD4 B7C0"
Vendor ID : "IBM "
Product ID : "ULTRIUM-TD4 "
Product Rev: "B7C0"
Serial Number: "F09D14B014"
WWN : ""
WWN Id Type : 0
Device Identifier: "IBM ULTRIUM-TD4 F09D14B014"
Device Type : SDT_TAPE
NetBackup Drive Type: 3
Removable : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name : "Tape0"
Passthru Name: "Tape0"
Volume Header: ""
Port: 4; Bus: 0; Target: 0; LUN: 0
Inquiry : "IBM ULTRIUM-TD4 B7C0"
Vendor ID : "IBM "
Product ID : "ULTRIUM-TD4 "
Product Rev: "B7C0"
Serial Number: "F09D14B004"
WWN : ""
WWN Id Type : 0
Device Identifier: "IBM ULTRIUM-TD4 F09D14B004"
Device Type : SDT_TAPE
NetBackup Drive Type: 3
Removable : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name : "Tape1"
Passthru Name: "Tape1"
Volume Header: ""
Port: 4; Bus: 0; Target: 1; LUN: 0
Inquiry : "IBM ULTRIUM-TD4 B7C0"
Vendor ID : "IBM "
Product ID : "ULTRIUM-TD4 "
Product Rev: "B7C0"
Serial Number: "F09D14B000"
WWN : ""
WWN Id Type : 0
Device Identifier: "IBM ULTRIUM-TD4 F09D14B000"
Device Type : SDT_TAPE
NetBackup Drive Type: 3
Removable : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name : "Tape2"
Passthru Name: "Tape2"
Volume Header: ""
Port: 4; Bus: 0; Target: 2; LUN: 0
Inquiry : "IBM ULTRIUM-TD4 B7C0"
Vendor ID : "IBM "
Product ID : "ULTRIUM-TD4 "
Product Rev: "B7C0"
Serial Number: "F09D14B090"
WWN : ""
WWN Id Type : 0
Device Identifier: "IBM ULTRIUM-TD4 F09D14B090"
Device Type : SDT_TAPE
NetBackup Drive Type: 3
Removable : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name : "Tape3"
Passthru Name: "Tape3"
Volume Header: ""
Port: 4; Bus: 0; Target: 3; LUN: 0
Inquiry : "IBM ULTRIUM-TD4 B7C0"
Vendor ID : "IBM "
Product ID : "ULTRIUM-TD4 "
Product Rev: "B7C0"
Serial Number: "F09D14B01C"
WWN : ""
WWN Id Type : 0
Device Identifier: "IBM ULTRIUM-TD4 F09D14B01C"
Device Type : SDT_TAPE
NetBackup Drive Type: 3
Removable : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name : "Tape4"
Passthru Name: "Tape4"
Volume Header: ""
Port: 4; Bus: 0; Target: 4; LUN: 0
Inquiry : "IBM ULTRIUM-TD4 B7C0"
Vendor ID : "IBM "
Product ID : "ULTRIUM-TD4 "
Product Rev: "B7C0"
Serial Number: "F09D14B018"
WWN : ""
WWN Id Type : 0
Device Identifier: "IBM ULTRIUM-TD4 F09D14B018"
Device Type : SDT_TAPE
NetBackup Drive Type: 3
Removable : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
04-15-2013 12:31 PM
C:\Program Files\Veritas\Volmgr\bin>tpconfig -d
Id DriveName Type Residence
SCSI coordinates/Path Status
****************************************************************************
0 IBM.ULTRIUM-TD4.010 hcart TLD(3) DRIVE=2
{2,0,0,0} UP
1 IBM.ULTRIUM-TD4.011 hcart TLD(3) DRIVE=3
{2,0,1,0} UP
2 IBM.ULTRIUM-TD4.012 hcart TLD(3) DRIVE=4
{2,0,2,0} UP
3 IBM.ULTRIUM-TD4.013 hcart TLD(3) DRIVE=7
{2,0,3,0} UP
4 IBM.ULTRIUM-TD4.014 hcart TLD(3) DRIVE=8
{2,0,4,0} UP
5 IBM.ULTRIUM-TD4.015 hcart TLD(3) DRIVE=6
{4,0,0,0} UP
6 IBM.ULTRIUM-TD4.016 hcart TLD(3) DRIVE=5
MISSING_PATH:{4,0,1,0}:F09D14B000 DOWN
7 IBM.ULTRIUM-TD4.017 hcart TLD(3) DRIVE=1
MISSING_PATH:{4,0,2,0}:F09D14B090 DOWN
8 IBM.ULTRIUM-TD4.018 hcart TLD(3) DRIVE=10
{4,0,3,0} UP
9 IBM.ULTRIUM-TD4.019 hcart TLD(3) DRIVE=9
{4,0,4,0} UP
Currently defined robotics are:
TLD(3) SCSI coordinates = {2,0,2,1}
EMM Server = veritas
04-15-2013 01:27 PM
Please review and follow :
https://www-secure.symantec.com/connect/articles/20-steps-analyze-correct-and-troublshoot-device-issues
More than likely, the latest device mappings, delete and reconfig will resolve your issue.
04-15-2013 01:48 PM
Your drives are down because the device paths it references are not available! Check why this is.
Zoning issue?
Drive issue?
HBA persistant binding issue?
One thing I can tell you, it's most likely not a NetBackup issue!
04-15-2013 02:02 PM
My recommendation: delete the drives/robots from the NBU setup. Then, especially if you have made any changes to LUN mapping or FC Host changes, be sure to power cycle the i500's I/O blade(s), then let Windows rediscover the devices at the OS level. Once you see all the devices again in Windows, let NetBackup rediscover them.
I've been having a similar issue and it required the Quantum's I/O blades to be power-cycled before all the changes were visible to the media server's OS.
04-15-2013 08:41 PM
Since Ron has suggested that you delete the drives and let NBU resdiscover them, please mark his post as solution?
Or maybe mph999 who suggested that first?
04-15-2013 08:57 PM
Hello All, This issues has been resolved using all the collections of your contributions.Thank you all. Here are the steps taken:
I confirmed the OS is able to see the 10 drives
1. Use robtest to move the stucks tapes out of the drives into an empty slots
2. suspended all jobs on the affected media server
3. Delete all the 10 drives on the media server
4 initiate the wizard to rediscover the drives
5. use robtest to test each drives and quit out of robtest
6. Resume suspended job and confirm everything is working fine.
04-15-2013 09:00 PM
Ron & matin, my bad. Her excellence Marianne is right. Thank you...:)