Forum Discussion

zhangchao's avatar
zhangchao
Level 3
11 years ago

Problem to update NBU configs after replacing a robotic tape drive.

Last week, the IBM stuff replaced a tape drive for the IBM 3584 tape library, and it was recognized on OS-level,

I did not realize that there should be some steps to update the NBU config, I just restarted the netbackup processes on Master server and media server.

Now, the backup jobs turn out erros:NBU status: 2009, EMM status: All compatible drive paths are down, but media is available

 

#tpconfig -d
Id  DriveName           Type   Residence
      Drive Path                                                       Status
****************************************************************************
0   IBM.DDSGEN5.000      pcd    Standalone
      /dev/rmt0.1                                                      DISABLED
1   IBM.ULT3580-TD4.000  hcart  TLD(0)  DRIVE=1 
      /dev/rmt1.1                                                      UP
2   IBM.ULT3580-TD4.001  hcart  TLD(0)  DRIVE=2 
      /dev/rmt2.1                                                      UP
3   IBM.ULT3580-TD4.002  hcart  TLD(0)  DRIVE=3 
      /dev/rmt3.1                                                      UP
4   IBM.ULT3580-TD4.003  hcart  TLD(0)  DRIVE=4 
      /dev/rmt4.1                                                      UP
 
Currently defined robotics are:
  TLD(0)     robotic path = /dev/smc0
 
But vmoprcmd shows different drive status:
#vmoprcmd
 
                           HOST STATUS
Host Name                               Version   Host Status
=====================================   =======   ===========
NBUmaster                               710300    ACTIVE
IMP-DB2                                 654000    ACTIVE
IMP-DB1                                 654000    ACTIVE
bus1                                    700000    ACTIVE
bus2                                    700000    ACTIVE
fee2                                    700000    ACTIVE
fee1                                    700000    ACTIVE
 
IBM.ULT3580-TD4.000      No      No                     No        hcart
    NBUmaster                  /dev/rmt1.1                              TLD
    IMP-DB2                 /dev/rmt/c24t11d0BESTnb              DOWN-TLD
    IMP-DB1                 /dev/rmt/c24t11d0BESTnb              SCAN-TLD
    bus1                    /dev/rtape/tape7_BESTnb                 DOWN-TLD
    bus2                    /dev/rtape/tape10_BESTnb               TLD
    fee2                    /dev/rtape/tape6_BESTnb                 TLD
    fee1                    /dev/rtape/tape6_BESTnb                 DOWN-TLD
 
IBM.ULT3580-TD4.001      No      No                     No        hcart-Clean
    NBUmaster                  /dev/rmt2.1                             TLD
    IMP-DB2                 /dev/rmt/c24t12d0BESTnb              SCAN-TLD
    IMP-DB1                 /dev/rmt/c24t12d0BESTnb              TLD
    bus1                    /dev/rtape/tape9_BESTnb              TLD
    bus2                    /dev/rtape/tape8_BESTnb              TLD
    fee2                    /dev/rtape/tape7_BESTnb              TLD
    fee1                    /dev/rtape/tape7_BESTnb              DOWN-TLD
 
IBM.ULT3580-TD4.002      No      No                     No        hcart
    NBUmaster                  /dev/rmt3.1                          TLD
    IMP-DB2                 /dev/rmt/c24t13d0BESTnb              DOWN-TLD
    IMP-DB1                 /dev/rmt/c24t13d0BESTnb              SCAN-TLD
    bus1                    /dev/rtape/tape6_BESTnb              DOWN-TLD
    bus2                    /dev/rtape/tape7_BESTnb              DOWN-TLD
    fee2                    /dev/rtape/tape8_BESTnb              DOWN-TLD
    fee1                    /dev/rtape/tape8_BESTnb              DOWN-TLD
 
IBM.ULT3580-TD4.003      No      No                     No        hcart-Clean
    NBUmaster                  /dev/rmt4.1                          TLD
    IMP-DB2                 /dev/rmt/c24t14d0BESTnb              SCAN-TLD
    IMP-DB1                 /dev/rmt/c24t14d0BESTnb              TLD
    bus1                    /dev/rtape/tape8_BESTnb              TLD
    bus2                    /dev/rtape/tape9_BESTnb              TLD
    fee2                    /dev/rtape/tape9_BESTnb              TLD
    fee1                    /dev/rtape/tape9_BESTnb              DOWN-TLD
============================================================
There are several drive in "DOWN-TLD" state.
when I tried to up the drive:
 
#vmoprcmd -upbyname IBM.ULT3580-TD4.003 -path /dev/rtape/tape9_BESTnb
output: volume does not exist in database
 
volume does not exist in database!
 
The DriveName of the replaced drive is IBM.ULT3580-TD4.002
 
I tried to Synchronize Global Device Database.using GUI admin console, but the option is grey.
I also tried:
#tpautoconf -replace_drive IBM.ULT3580-TD4.002 -path /dev/rmt3.1
Found a matching device in global DB, IBM.ULT3580-TD4.002 on host NBUmaster.
No other outcome.
 
What should I do?
By the way, what is "SCAN-TLD"?

 

  • Delete the drive and re-add it, I always find this to be the easiest option. Then restart ltid once done (or restart NBU on that media server)

3 Replies

  • Delete the drive and re-add it, I always find this to be the easiest option. Then restart ltid once done (or restart NBU on that media server)

  • correct.. when the Drive is shared between the mulitple media servers, reconfiguring though GUI would be the better option..

    and also you can start indetifiying the issue..

    run scan and tpautoconf -t commnad , it will list the identified drive paths in the OS level 

    compare them with the the Drvies paths configured in Netbackup level, you may indetifiy the difference for replaced drive...

    delete the Drive and re-add it.. 

  • Hi,Thanks

    Actually, Becasue media servers are all production systems,I have no root access.

    So the actions I took before I post this thread are all done on master server.

    After I got root access. I just run "vmoprcmd -up" on the media servers.

    #vmoprcmd -upbyname IBM.ULT3580-TD4.003 -path /dev/rtape/tape9_BESTnb

    This command should be executed on the media server.

    Anyhow, "delete the Drive and re-add it" should be the best practice after failing to try "up" the drives on the media server.