cancel
Showing results for 
Search instead for 
Did you mean: 

netbackup 7.5 netapp lto6 drive issue

j-iverson
Level 2

setting up a dr netbackup environment at another location.  both environments are similar, linux master/media, netbackup 7.5.0.6, adic/quantum tape library, ibm lto6 tape drives.  at the new site the netapp returns an incorrect "format:" from the "mt" command, says it is lto-4/5 instead of lto6, and i think because of this, the "tpconfig -dev_ping" also fails, and the storage unit cannot be used.  output from commands both local (works) and remote (broken) are:

houston netapp connected to lto6 device, looks good:

# ssh houston6290 sysconfig -t
    Tape drive (houston9148b:1-19.126)  IBM LTO-6 ULTRIUM 
    rst1l  -  rewind device,        format is: LTO-4/5 Native Density 
    nrst1l -  no rewind device,     format is: LTO-4/5 Native Density 
    urst1l -  unload/reload device, format is: LTO-4/5 Native Density 
    rst1m  -  rewind device,        format is: LTO-4/5 Compressed     
    nrst1m -  no rewind device,     format is: LTO-4/5 Compressed     
    urst1m -  unload/reload device, format is: LTO-4/5 Compressed     
    rst1h  -  rewind device,        format is: LTO-6 2.5TB            
    nrst1h -  no rewind device,     format is: LTO-6 2.5TB            
    urst1h -  unload/reload device, format is: LTO-6 2.5TB            
    rst1a  -  rewind device,        format is: LTO-6 6.25TB Compressed
    nrst1a -  no rewind device,     format is: LTO-6 6.25TB Compressed
    urst1a -  unload/reload device, format is: LTO-6 6.25TB Compressed

# ssh houston6290 mt -t nrst1a status
Tape drive: IBM LTO-6 ULTRIUM
    Status: offline
    Format: LTO-6 6.25TB Compressed
    fileno = -1  blockno = -1  resid = 0

# tpconfig -dev_ping -drive -path nrst1a -nh houston6290
Device Inquiry String: IBM     ULTRIUM-TD6     E6R0
Device Serial Number: F001B2B06D
Default Type: 16

dallas:

# ssh dallas8060 sysconfig -t
    Tape drive (dallas9148a:1-13.126)  IBM LTO-6 ULTRIUM 
    rst0l  -  rewind device,        format is: LTO-4/5 Native Density 
    nrst0l -  no rewind device,     format is: LTO-4/5 Native Density 
    urst0l -  unload/reload device, format is: LTO-4/5 Native Density 
    rst0m  -  rewind device,        format is: LTO-4/5 Compressed     
    nrst0m -  no rewind device,     format is: LTO-4/5 Compressed     
    urst0m -  unload/reload device, format is: LTO-4/5 Compressed     
    rst0h  -  rewind device,        format is: LTO-6 2.5TB            
    nrst0h -  no rewind device,     format is: LTO-6 2.5TB            
    urst0h -  unload/reload device, format is: LTO-6 2.5TB            
    rst0a  -  rewind device,        format is: LTO-6 6.25TB Compressed
    nrst0a -  no rewind device,     format is: LTO-6 6.25TB Compressed
    urst0a -  unload/reload device, format is: LTO-6 6.25TB Compressed

# ssh dallas8060 mt -t nrst0a status
Tape drive: IBM LTO-6 ULTRIUM
    Status: offline
    Format: LTO-4/5 Native Density 
    fileno = -1  blockno = -1  resid = 0

# tpconfig -dev_ping -path nrst0a -nh dallas8060
Failed to inquiry the specified device.

both netapps are at the same release: NetApp Release 8.2.2RC2 7-Mode.  we have 10 local netapps at various release levels and i have never had this problem.  both tape_config/IBM_LTO6_ULTRIUM.TCF files are the same are each filer.  options tape.reservations are both "off", i don't think we've ever had to play with these for 7-mode.

i was able to add the netapp to the drive in the device gui, and it saw the correct serial number, had me stop/restart the media manager services as usual.  it looks to be an issue on the netapp, but there is not much more there that i know to look into.  any suggestions?

thanks,

jerald

 

1 ACCEPTED SOLUTION

Accepted Solutions

Yasuhisa_Ishika
Level 6
Partner Accredited Certified

Whichis your actual problem, "tpconfig -dev_ping" failure for dallas8060 or difference in mt output?

It seem that any tape is not mounted when you ran mt, so format can be ignored I think.

For former problem, please try same option for dallas8060. "-drive" option is missed for dallas.

View solution in original post

2 REPLIES 2

Yasuhisa_Ishika
Level 6
Partner Accredited Certified

Whichis your actual problem, "tpconfig -dev_ping" failure for dallas8060 or difference in mt output?

It seem that any tape is not mounted when you ran mt, so format can be ignored I think.

For former problem, please try same option for dallas8060. "-drive" option is missed for dallas.

j-iverson
Level 2

great catch on the missing "-drive" option.  my cut and paste from one terminal to the other must have missed it, and then i kept using command history to re-run it to the 2 netapps i was setting up.  also found a config error made by a fellow worker, so it is working now.  i guess the "format" area from the mt command doesn't matter.

thanks,

jerald