L180´s Drives LTO4 are switching up/down
L180´s Drives LTO4 are switching up/down
Hello... My LTO4 drives that ate located at L180 library are changing their status from UP to DOWN.
I have one LTO2 drive in this same library and it is OK.
Take a look at my tpconfig -d above. My L180 is named TLD(0). Could be a Firmware trouble?
My setup is: Backup server: Sun Fire V490, Solaris 10, Netbackup 6.5.6.
-bash-3.00# /usr/openv/volmgr/bin/tpconfig -d
Id DriveName Type Residence
Drive Path Status
****************************************************************************
0 DRV-1 hcart2 TLD(0) DRIVE=1
/dev/rmt/4cbn UP
2 HP.ULTRIUM4-SCSI.000 hcart3 TLD(3) DRIVE=1
/dev/rmt/2cbn UP
3 HP.ULTRIUM4-SCSI.001 hcart3 TLD(0) DRIVE=4
/dev/rmt/1cbn DOWN
4 HP.ULTRIUM4-SCSI.002 hcart3 TLD(0) DRIVE=3
/dev/rmt/0cbn DOWN
5 IBM.ULTRIUM-TD4.000 hcart3 TLD(0) DRIVE=6
/dev/rmt/7cbn DOWN
6 IBM.ULT3580-TD4.000 hcart3 TLD(1) DRIVE=1
/dev/rmt/6cbn UP
7 IBM.ULT3580-TD4.001 hcart3 TLD(1) DRIVE=2
/dev/rmt/5cbn UP
8 IBM.ULTRIUM-TD4.001 hcart3 TLD(0) DRIVE=5
/dev/rmt/8cbn DOWN
Comments
find out why
look at your problem logs or library log - or at the other NB logs and find out why -
can be trying to put a lot02 tape into a lot04 drive for writing ( cannot do that)
not configured right
tapes are bad
I don't have to know how to spell....I work on Unix.
NetBackup 7.0.1 - AIX & Windows
Please do the following: Add
Please do the following:
Add this entry to /usr/openv/volmgr/vm.conf:
VERBOSE
Restart NBU.
UP the DOWN drives again.
Reason for DOWN drives will now be logged in /var/adm/messages.
Please post messages file as attachment next time any of the drives go down.
If I understand your opening post correct, you have one L180 robot, but your config shows 3 robots -
TLD(0)
TLD(1)
TLD(3)
Why is that?
How is your robot and tape drives connected? SCSI or Fibre? If Fibre - have you confirmed that Persistent Binding is in place?
It seems like a good idea to delete all devices and rerun device config. If the device config wizard adds your drives as hcart (which is the default for LTO4), change them back to hcart3 (drive, media and STU densities must match to prevent status 96).
Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows.
Handy NBU links
Use robtest to make sure that
Use robtest to make sure that there aren't tapes in the drives - if there are move them to empty slots
Often happens if tape loading is not done correctly
Also make sure all LTO2 media is set a hcart2 and all LTO4 media is set as hcart3
Authorised Symantec Consultant
Don't forget to give a "Thumbs Up" or mark as "Solution" if someones advice has helped you.
check /var/log/messages
Do you see SCSI sense messages in the syslog ?
Assumption is the mother of all mess ups.
If this post solved you’re questions please send a gratitude by marking it as a solution.
The command "tpautoconf -a"
The command "tpautoconf -a" solved the trouble.
Just as a matter of interest
- where/how did you come across that?
# tpautoconf -Q
UNSUPPORTED OPTIONS
tpautoconf -a | -t | -r | -w [-q | -v | -java]
-a
Attempt to configure all discovered devices and return a list
of all devices configured and unconfigured.
Regards Andy
"It's not too late to panic ..."
Would you like to reply?
Login or Register to post your comment.