cancel
Showing results for 
Search instead for 
Did you mean: 

NDMP connection is still pointing to old drive serial number

azrula
Level 2

Hi,

We had changed one of our drive (drive 1). Successfully reconfigure back the new drive with NDMP connection

When we run tpautoconf -probe command, it still detected the old serial number. FYI, we do observed that drive 1 NDMP connection frequently down.

Please advise.

 

4 REPLIES 4

Michael_G_Ander
Level 6
Certified

Are the tape drive attached to the filer ?

If yes have you reconfigured the tape drive on the filer ?

This technote https://www.veritas.com/support/en_US/article.000027854 might help you

The standard questions: Have you checked: 1) What has changed. 2) The manual 3) If there are any tech notes or VOX posts regarding the issue

azrula
Level 2

Hi Michael,

Yes. I have configured the tape drive on the filer. I did refer to the same given link when I first setup  the drive.

klsrv04# tpautoconf -report_disc
klsrv04#
 

When i run below, i still pointing to the old serial :-

klsrv04# tpautoconf -probe xkl3090dm1.tim.ti.com

Host "xkl3090dm1.tim.ti.com" SCSI device model "IBM     3576-MTL       6401300000":

  Device "/dev/mc_d2l1" attributes=0x0

    SERIAL_NUMBER=000001320696_LLA

Host "xkl3090dm1.tim.ti.com" tape device model "IBM     ULT3580-TD4    C7Q":

  Device "/dev/mt_d0l0" attributes=(0x4) RAW

    SERIAL_NUMBER=1310263740

  Device "/dev/mt_d0l0r" attributes=(0x5) REWIND RAW

    SERIAL_NUMBER=1310263740

Host "xkl3090dm1.tim.ti.com" tape device model "IBM     ULT3580-TD4    C7Q":

  Device "/dev/mt_d1l0" attributes=(0x4) RAW

    SERIAL_NUMBER=1310263143

  Device "/dev/mt_d1l0r" attributes=(0x5) REWIND RAW

    SERIAL_NUMBER=1310263143

Host "xkl3090dm1.tim.ti.com" tape device model "IBM     ULT3580-TD4    C7Q":

  Device "/dev/mt_d2l0" attributes=(0x4) RAW

    SERIAL_NUMBER=1310262343

  Device "/dev/mt_d2l0r" attributes=(0x5) REWIND RAW

    SERIAL_NUMBER=1310262343

If i run this command, it will show the ucrrent serial number :-

klsrv04# tpautoconf -t

TPAC60 IBM     ULT3580-TD4     C7QH 1310262343 -1 -1 -1 -1 /dev/rmt/1cbn - -

TPAC60 IBM     ULT3580-TD4     C7QH 9311120004 -1 -1 -1 -1 /dev/rmt/0cbn - -

TPAC60 IBM     ULT3580-TD4     C7QH 1310263740 -1 -1 -1 -1 /dev/rmt/2cbn - -

Marc_LHeureux
Level 4
Partner Accredited

The discrepancy report only checks tape drives attached the host its being run from, it does not go out to all the filers and check all their drives.

I think you should examine this problem without considering NetBackup.  Log on to your filer and ask it what drive serial numbers it sees - if that is still wrong, work with your filer vendor and IBM to sort it out.  Once those are in sync then you can come back to NetBackup's tpautoconf -probe.

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified
I agree - check drive serial no on the filer. This is where the issue is. tpautoconf -probe queries the filer while tpautoconf -t queries the local media server.