Forum Discussion

Mike_3G's avatar
Mike_3G
Level 3
13 years ago

Re-configuring tape drives NBU 7.0.1

Hi, I'm running NBU 7.0.1 on RHEL5. We have a Scalar i2000 tape robot with 12 drives. Last week I completed a hardware / OS refresh and after the Hot Catalog Restore most everything is working OK. But I have one tape drive that is marked "down" and I'd like to reconfigure the drives and verify the paths are correct. None of the drives were changed. This is the 1st time I've experienced this issue so I was wondering if I should just re-run the Drive configuration wizard or if there's another way to accomplish this.

Mike

 

Some more info:

[root@x-bkup-01 ~]# tpautoconf -t
TPAC60 IBM     ULTRIUM-TD3     93GM 1210381803 -1 -1 -1 -1 /dev/nst7 - -
TPAC60 IBM     ULTRIUM-TD4     B7C0 1310113137 -1 -1 -1 -1 /dev/nst10 - -
TPAC60 IBM     ULTRIUM-TD4     B7C0 1310104177 -1 -1 -1 -1 /dev/nst11 - -
TPAC60 IBM     ULTRIUM-TD3     93GM 1210127918 -1 -1 -1 -1 /dev/nst6 - -
TPAC60 IBM     ULTRIUM-TD3     93GM 1210127931 -1 -1 -1 -1 /dev/nst9 - -
TPAC60 IBM     ULTRIUM-TD3     93GM 1210127910 -1 -1 -1 -1 /dev/nst8 - -
TPAC60 IBM     ULTRIUM-TD3     93GM 1210186652 -1 -1 -1 -1 /dev/nst3 - -
TPAC60 IBM     ULTRIUM-TD3     93GM 1210128000 -1 -1 -1 -1 /dev/nst1 - -
TPAC60 IBM     ULTRIUM-TD3     93GM 1210128204 -1 -1 -1 -1 /dev/nst0 - -
TPAC60 IBM     ULTRIUM-TD4     B7C0 1310112738 -1 -1 -1 -1 /dev/nst4 - -
TPAC60 IBM     ULTRIUM-TD3     93GM 1210184448 -1 -1 -1 -1 /dev/nst2 - -
TPAC60 IBM     ULTRIUM-TD4     B7C0 1310113141 -1 -1 -1 -1 /dev/nst5 - -

[root@x-bkup-01 ~]# tpautoconf -r
TPAC60 ADIC    Scalar i2000    607A ADIC203102197_LL0 -1 -1 -1 -1 /dev/sg6 - -

[root@x-bkup-01 ~]# tpautoconf -report_disc
======================= New Device (Drive) =======================
 Inquiry = "IBM     ULTRIUM-TD3     93GM"
 Serial Number = 1210381803
 Drive Path = /dev/nst7
 Found as TLD(0), Drive = 8

7.1.x and Earlier
Backup and Recovery
Configuring
NetBackup
  • Mike_3G's avatar
    Mike_3G
    13 years ago

    Looking at the device serial numbers helped out (# tpconfig -dl). The master server discovered 12 drives & 1 robot, which is correct. One of the media servers (which I didn't touch) showed a new drive marked DOWN (# tpautoconf -report_disc). It's serial number didn't match any of the S/Ns reported by the Master server.

    From the GUI, I deleted the "phantom" drive. Then I re-ran the device configuration wizard. It appears that everything is now OK.

    Thanks for your help.  -Mike

4 Replies

Sort By
  • Will_Restore's avatar
    Will_Restore
    Level 6
    13 years ago

    " I was wondering if I should just re-run the Drive configuration wizard "

     

    Sure, that's what i would do.

  • revarooo's avatar
    revarooo
    Level 6
    13 years ago

    If the drives are all on one system, delete them all and re-add them from scratch.

    It sounds drastic, but its very quick.

    nbemmcmd -deletealldevices -machinename <media_server> -machinetype media

    Then rediscover all devices:

    tpautoconf -a

    restart ltid and that's it.

     

  • nesel's avatar
    nesel
    Level 4
    13 years ago

    If your problem is about tape drive is "down", I may recommend to do the following:

       > On the NBU GUI > Device Monitor > select the down drive > right click > Up Drive > wait for 5-10 secs and refresh window. If this doesn't work, please look into event logs of your master server for hardware troubleshooting

     

       > Check physical hardware for error/amber and contact your hardware vendor for possible hardware troubleshooting or replacement

     

    For reconfiguring or re-run the drive configuration, I usually do this when I encounter "missing path" for my drives, which usually happens when their is a patch update on the host or tape library firmware is outdated.

     

    Hope this will help.

     

     

     

  • Mike_3G's avatar
    Mike_3G
    Level 3
    13 years ago

    Looking at the device serial numbers helped out (# tpconfig -dl). The master server discovered 12 drives & 1 robot, which is correct. One of the media servers (which I didn't touch) showed a new drive marked DOWN (# tpautoconf -report_disc). It's serial number didn't match any of the S/Ns reported by the Master server.

    From the GUI, I deleted the "phantom" drive. Then I re-ran the device configuration wizard. It appears that everything is now OK.

    Thanks for your help.  -Mike