Forum Discussion

Monu_Puri's avatar
Monu_Puri
Level 4
14 years ago

tpautoconf

As we all know that tpautoconf -report_disc Reports discrepancies between detected devices and Global Database. And we can use -replace_drive drive_name -path drive_path and can correct the serial number in the local and Global Databases.

The issue i am facing is that how to identify which missing drive belongs to which new device when we have multiple missing drives and new devices.

So in other words if i want to replace the path how to match the missing drive with new device.

7.1.x and Earlier
Backing Up
Backup and Recovery
NetBackup
  • Marianne's avatar
    Marianne
    14 years ago

    To compare manually, run

    'tpautoconf -t' on media server,
    On acsls server from acssa prompt: display drive *,*,*,* -f type serial_num

    Check NBU config with tpconfig -l

     

    Cleaning up Global Device database in NBU 5.x was extremely messy - best to delete all tape drives, check 'left over' devices in globdb with 'vmglob -listall' and delete with 'vmglob -delete ....'

    NBU 5.1 patches had various improvements to device change/replacement, but even that is EOL... Any particular reason why you are on such an old, unsupported NBU version?

  • Chris_Morris's avatar
    Chris_Morris
    Level 3
    14 years ago

    If you can't tell where it is via the GUI, or by running a tpconfig -emm_dev_list from volmgr\bin, figure out the serial numbers and robotic drive numbers, then match it up to what you physically have within the robot.  Compare and contrast.  You'll be able to tell which drive(s) you're looking for that way.

  • mph999's avatar
    mph999
    Level 6
    14 years ago

    I think Chris is correct, command gives something like this :

     

    ======================= New Device (Tape) ============
    Inquiry = "QUANTUM DLT7000         245F"
    Serial Number = PXA51S3232
    Drive Path = /dev/rmt/21cbn
    Found as TLD(0), Drive = 1
    ===================== Missing Device (Drive) =========
    Drive Name = QUANTUMDLT70001
    Drive Path = /dev/rmt/11cbn
    Inquiry = "QUANTUM DLT7000         245F"
    Serial Number = PXA51S3587
    TLD(0) definition, Drive = 1
    Hosts configured for this device:
    Host = HOSTA
    Host = HOSTB

    Forget the path, this could have changed, but it gives the position, in this example TLD(0), Drive 1 -  so we know the correct pair, to take the <driveame> from the old and the <pah> from the new.

    Another way (which may not be acceptable for you), just delete all the drives and rescan with the device wizard ...

     

    Martin

     

     

     

  • Monu_Puri's avatar
    Monu_Puri
    Level 4
    14 years ago

    We are using Netbackup 5.0 and below is the output from one of the media server:

    [root]\#/usr/openv/volmgr/bin/tpautoconf -report_disc

    ======================= Missing Device (Drive) =======================
     Drive Name = 912
     Drive Path = /dev/rmt/c9t6d0BESTnb
     Inquiry = "-"
     Serial Number =
     ACS(0) definition ACS = 0 LSM = 0 PANEL = 9 DRIVE = 12
     Hosts configured for this device:
      Host =
    ======================= Missing Device (Drive) =======================
     Drive Name = 910
     Drive Path = /dev/rmt/c9t6d0BESTnb
     Inquiry = "-"
     Serial Number =
     ACS(0) definition ACS = 0 LSM = 0 PANEL = 9 DRIVE = 10
     Hosts configured for this device:
      Host =
    ======================= Missing Device (Drive) =======================
     Drive Name = 902
     Drive Path = /dev/rmt/c9t6d0BESTnb
     Inquiry = "-"
     Serial Number =
     ACS(0) definition ACS = 0 LSM = 0 PANEL = 9 DRIVE = 2
     Hosts configured for this device:
      Host =
    ======================= Missing Device (Drive) =======================
     Drive Name = 900
     Drive Path = /dev/rmt/c9t6d0BESTnb
     Inquiry = "-"
     Serial Number =
     ACS(0) definition ACS = 0 LSM = 0 PANEL = 9 DRIVE = 0
     Hosts configured for this device:
      Host =
    ======================= Missing Device (Drive) =======================
     Drive Name = 309
     Drive Path = /dev/rmt/c9t6d0BESTnb
     Inquiry = "-"
     Serial Number =
     ACS(0) definition ACS = 0 LSM = 0 PANEL = 3 DRIVE = 9
     Hosts configured for this device:
      Host =
    ======================= Missing Device (Drive) =======================
     Drive Name = 308
     Drive Path = /dev/rmt/c9t6d0BESTnb
     Inquiry = "-"
     Serial Number =
     ACS(0) definition ACS = 0 LSM = 0 PANEL = 3 DRIVE = 8
     Hosts configured for this device:
      Host =
    ======================= Missing Device (Drive) =======================
     Drive Name = 300
     Drive Path = /dev/rmt/c9t6d0BESTnb
     Inquiry = "-"
     Serial Number =
     ACS(0) definition ACS = 0 LSM = 0 PANEL = 3 DRIVE = 0
     Hosts configured for this device:
      Host =
    ======================= Missing Device (Drive) =======================
     Drive Name = 219
     Drive Path = /dev/rmt/c9t6d0BESTnb
     Inquiry = "-"
     Serial Number =
     ACS(0) definition ACS = 0 LSM = 0 PANEL = 2 DRIVE = 19
     Hosts configured for this device:
      Host =
    ======================= Missing Device (Drive) =======================
     Drive Name = 218
     Drive Path = /dev/rmt/c9t6d0BESTnb
     Inquiry = "-"
     Serial Number =
     ACS(0) definition ACS = 0 LSM = 0 PANEL = 2 DRIVE = 18
     Hosts configured for this device:
      Host =
    =========== Missing Device or no local control path (Robot) ===========
     Defined as robotic ACS(0)
     Inquiry = "-"
     Serial Number =
     Robot Control Host = 
     Hosts configured for this device:
      Host = 
      Host =  
      ======================= New Device (Tape) =======================
     Inquiry = "IBM     ULTRIUM-TD1     4561"
     Serial Number = 6811338951
     Drive Path = /dev/rmt/c19t6d0BESTnb
    [root]\#

  • Marianne's avatar
    Marianne
    Level 6
    14 years ago

    To compare manually, run

    'tpautoconf -t' on media server,
    On acsls server from acssa prompt: display drive *,*,*,* -f type serial_num

    Check NBU config with tpconfig -l

     

    Cleaning up Global Device database in NBU 5.x was extremely messy - best to delete all tape drives, check 'left over' devices in globdb with 'vmglob -listall' and delete with 'vmglob -delete ....'

    NBU 5.1 patches had various improvements to device change/replacement, but even that is EOL... Any particular reason why you are on such an old, unsupported NBU version?

  • Monu_Puri's avatar
    Monu_Puri
    Level 4
    14 years ago

    display drive *,*,*,* -f type serial_num is a very useful command to match manually.

    Thanks a ton ...... Much appreciated !!!!!!

    We are in a  process of upgrading to 6.5 so just few more days.

     Sorry for the late reply!