07-28-2008 01:36 PM
We do weekly full backup on our filer, but we always get the error.
The drive was up, but it'll go down when tries to backup on NDMP.
I checked all the tpauotconfig, sysconfig, etc.. all showing correct status.
Logs as following;
- awaiting resource titan-hcart-robot-tld-0-netapp - No drives are available
7/26/2008 3:14:44 AM - Error nbjm(pid=6500) NBU status: 800, EMM status: All compatible drive paths are down, but media is available
resource request failed(800)
Event Type: Error
Event Source: NetBackup TLD Daemon
Event Category: None
Event ID: 14021
Date: 7/26/2008
Time: 12:15:24 AM
User: N/A
Computer: Host
Description:
TLD(0) [5668] timed out after waiting 846 seconds for ready, drive 2
Event Type: Error
Event Source: NetBackup Device Manager
Event Category: None
Event ID: 2636
Date: 7/26/2008
Time: 12:19:34 AM
User: N/A
Computer: Host
Description:
Operator/EMM server has DOWN'ed drive HP.ULTRIUM4-SCSI.001 (device 2)
07-29-2008 04:21 PM
Has this worked in the past, and has just stopped working? Or has it never worked?
Physically check the drive and ensure it is operational and there is no tape stuck in it.
What is the output for tpautoconf -probe <filername>? Ensure the path (that shows in the output) is correct when setting up the drive. Remember to stop ltid and restart it if you make any changes in tpconfig.
Hope this helps.
07-29-2008 04:24 PM
Hi run:
vmoprcmd -shmdrive | grep -i <drivename>
vmoprcmd -autoconfig -t
vmglob -listall -b | grep -i <drive serial number>
match the Drive Serial Number, Path and Name between this commands if there is a mistmatch you will need to update the drive info with tpconfig -update if everything is ok, check for drive errors, can be a dirty/bad drive.
regards
07-29-2008 06:07 PM
Here's the output result:
C:\Program Files\Veritas\Volmgr\bin>tpautoconf.exe -probe bull
Host "bull" tape device model "HP Ultrium 4-SCSI ":
Device "rst0l" attributes=(0x5) REWIND RAW
DENSITY=LTO-2(ro)/3 2/400GB
ELECTRICAL_NAME=0c.125
SERIAL_NUMBER=HU18111LCY
WORLD_WIDE_NAME=WWN[5:006:0b0000:b9120e]
ALIAS 0=st0
Device "nrst0l" attributes=(0x4) RAW
DENSITY=LTO-2(ro)/3 2/400GB
ELECTRICAL_NAME=0c.125
SERIAL_NUMBER=HU18111LCY
WORLD_WIDE_NAME=WWN[5:006:0b0000:b9120e]
ALIAS 0=st0
Device "urst0l" attributes=(0x6) UNLOAD RAW
DENSITY=LTO-2(ro)/3 2/400GB
ELECTRICAL_NAME=0c.125
SERIAL_NUMBER=HU18111LCY
WORLD_WIDE_NAME=WWN[5:006:0b0000:b9120e]
ALIAS 0=st0
Device "rst0m" attributes=(0x5) REWIND RAW
DENSITY=LTO-2(ro)/3 4/800GB cmp
ELECTRICAL_NAME=0c.125
SERIAL_NUMBER=HU18111LCY
WORLD_WIDE_NAME=WWN[5:006:0b0000:b9120e]
ALIAS 0=st0
Device "nrst0m" attributes=(0x4) RAW
DENSITY=LTO-2(ro)/3 4/800GB cmp
ELECTRICAL_NAME=0c.125
SERIAL_NUMBER=HU18111LCY
WORLD_WIDE_NAME=WWN[5:006:0b0000:b9120e]
ALIAS 0=st0
Device "urst0m" attributes=(0x6) UNLOAD RAW
DENSITY=LTO-2(ro)/3 4/800GB cmp
ELECTRICAL_NAME=0c.125
SERIAL_NUMBER=HU18111LCY
WORLD_WIDE_NAME=WWN[5:006:0b0000:b9120e]
ALIAS 0=st0
Device "rst0h" attributes=(0x5) REWIND RAW
DENSITY=LTO-4 800GB
ELECTRICAL_NAME=0c.125
SERIAL_NUMBER=HU18111LCY
WORLD_WIDE_NAME=WWN[5:006:0b0000:b9120e]
ALIAS 0=st0
Device "nrst0h" attributes=(0x4) RAW
DENSITY=LTO-4 800GB
ELECTRICAL_NAME=0c.125
SERIAL_NUMBER=HU18111LCY
WORLD_WIDE_NAME=WWN[5:006:0b0000:b9120e]
ALIAS 0=st0
Device "urst0h" attributes=(0x6) UNLOAD RAW
DENSITY=LTO-4 800GB
ELECTRICAL_NAME=0c.125
SERIAL_NUMBER=HU18111LCY
WORLD_WIDE_NAME=WWN[5:006:0b0000:b9120e]
ALIAS 0=st0
Device "rst0a" attributes=(0x5) REWIND RAW
DENSITY=LTO-4 1600GB cmp
ELECTRICAL_NAME=0c.125
SERIAL_NUMBER=HU18111LCY
WORLD_WIDE_NAME=WWN[5:006:0b0000:b9120e]
ALIAS 0=st0
Device "nrst0a" attributes=(0x4) RAW
DENSITY=LTO-4 1600GB cmp
ELECTRICAL_NAME=0c.125
SERIAL_NUMBER=HU18111LCY
WORLD_WIDE_NAME=WWN[5:006:0b0000:b9120e]
ALIAS 0=st0
Device "urst0a" attributes=(0x6) UNLOAD RAW
DENSITY=LTO-4 1600GB cmp
ELECTRICAL_NAME=0c.125
SERIAL_NUMBER=HU18111LCY
WORLD_WIDE_NAME=WWN[5:006:0b0000:b9120e]
ALIAS 0=st0
C:\Program Files\Veritas\Volmgr\bin>vmglob.exe -listall -b
device
type device name serial number host name
------------------------------------------------------------------------
robot ROBOT0 QP0819BDC00549 titan
drive HP.ULTRIUM4-SCSI.001 HU18111LCY titan
drive HP.ULTRIUM4-SCSI.000 HU175213R9 titan
It matches the serial. HP001 is the drive that's used directly for the NDMP through the fiber.
It works when I do the manual backup. The drive goes down when I do schedule backup. The drive seems to be down periodically by itself.
02-09-2009 08:58 PM
Hi mkc
HELP!
I am experiencing the same issue with our NetApp Filer drive (NDMP). It spontaneously will continue to do to DOWN status even when there are no backups scheduled. Did u find a fix for this issue? If so, I would really apprecaite it if you kindly share the resolution.
Thank you
Jayson E.
[Edited: Removed personal information per the community rules and regulations.]
02-09-2009 10:04 PM
We faced the similar problem because of Zoning issue !
Re CHeck the Zoning !!!
02-10-2009 08:47 AM
Hi Karthikeyan,
Thank you for your response. I am not responsible for zoning our drives. Our Storage grp. does. Can you tell me exactly what you did to resolve this issue, by rechecking the zoning?
Thank you