Forum Discussion

symsonu's avatar
symsonu
Level 6
12 years ago

Netbackup drive going down randomly

Hello

 

In netbackup media server one of the drive is going down after few days randomly

Please suggest how can we troubleshoot this problem

 

 

7.1.x and Earlier
Backup and Recovery
Installing
NetBackup
Recovering
Restore
Troubleshooting
Upgrade
Virtualization
  • Marianne's avatar
    Marianne
    12 years ago

    As per huanglao2002's post above - you need to move all cleaning tapes to the None pool and change media type to Cleaning tapes.  Because your cleaning tapes were added to NBU as normal backup tapes, NBU will try to use them for backups and cause issues like you've been experiencing.

    Please move cleaning tapes as explained above and create a Barcode Rule so that inventory will add any tapes starting with CLN as Cleaning tapes.

    Once you have sorted this out, test again with valid backup tapes.

     

  • Marianne's avatar
    Marianne
    Level 6
    12 years ago

    As per huanglao2002's post above - you need to move all cleaning tapes to the None pool and change media type to Cleaning tapes.  Because your cleaning tapes were added to NBU as normal backup tapes, NBU will try to use them for backups and cause issues like you've been experiencing.

    Please move cleaning tapes as explained above and create a Barcode Rule so that inventory will add any tapes starting with CLN as Cleaning tapes.

    Once you have sorted this out, test again with valid backup tapes.

     

  • mph999's avatar
    mph999
    Level 6
    12 years ago

    Look in the bptm log on  the media server (...netbackup/logs/bptm )

    Look in system messages / event log on the media server

    Look in /usr/openv/netbackup/db/media/errors file on the media server

    Martin

  • Marianne's avatar
    Marianne
    Level 6
    12 years ago

    Please tell us OS on the media server and NBU version.

    Device-level troubleshooting must always start at OS level...

  • symsonu's avatar
    symsonu
    Level 6
    12 years ago

    bptm error log

    2013 Apr 18 22:35:25 hydmas1o-bck tldd[19778]: [ID 104068 daemon.error] TLD(0) [19778] timed out after waiting 850 seconds for ready, drive 1 Apr 18 22:36:10 hydmas1o-bck ltid[27775]: [ID 335503 daemon.error] Operator/EMM server has DOWN'ed drive HP.Ultrium4-SCSI.000 (device 0) Apr 22 15:28:24 hydmas1o-bck bpjava-msvc[1171]: [ID 427199 user.error] pam_dial_auth: terminal-device not specifiedby login, returning Error in underlying service module. Apr 22 15:29:03 hydmas1o-bck ltid[27775]: [ID 174685 daemon.notice] Operator/EMM server has UP'ed drive HP.Ultrium4-SCSI.000 (device 0) Apr 24 16:13:05 hydmas1o-bck bpjava-msvc[13242]: [ID 427199 user.error] pam_dial_auth: terminal-device not specifiedby login, returning Error in underlying service module. Apr 25 08:59:53 hydmas1o-bck bpjava-msvc[16724]: [ID 427199 user.error] pam_dial_auth: terminal-device not specifiedby login, returning Error in underlying service module. May 1 21:07:00 hydmas1o-bck tldd[19674]: [ID 938534 daemon.error] TLD(0) [19674] timed out after waiting 850 seconds for ready, drive 1 May 1 21:07:44 hydmas1o-bck ltid[27775]: [ID 335503 daemon.error] Operator/EMM server has DOWN'ed drive HP.Ultrium4-SCSI.000 (device 0) May 3 08:55:23 hydmas1o-bck ltid[27775]: [ID 174685 daemon.notice] Operator/EMM server has UP'ed drive HP.Ultrium4-SCSI.000 (device 0) May 5 14:11:31 hydmas1o-bck tldd[6754]: [ID 532221 daemon.error] TLD(0) [6754] timed out after waiting 850 seconds for ready, drive 1 May 5 14:12:15 hydmas1o-bck ltid[27775]: [ID 335503 daemon.error] Operator/EMM server has DOWN'ed drive HP.Ultrium4-SCSI.000 (device 0) May 15 12:49:07 hydmas1o-bck ltid[27775]: [ID 174685 daemon.notice] Operator/EMM server has UP'ed drive HP.Ultrium4-SCSI.000 (device 0) May 17 04:13:33 hydmas1o-bck tldd[16733]: [ID 237332 daemon.error] TLD(0) [16733] timed out after waiting 850 seconds for ready, drive 1 May 17 04:14:18 hydmas1o-bck ltid[27775]: [ID 335503 daemon.error] Operator/EMM server has DOWN'ed drive HP.Ultrium4

     

     

     

    There is nothing in /usr/openv/netbackup/db/media/errors not updated since six months

     

  • huanglao2002's avatar
    huanglao2002
    Level 6
    12 years ago

     timed out after waiting 850 seconds for ready

     

    Can you call the tape library vendor to check the device physical status?

  • symsonu's avatar
    symsonu
    Level 6
    12 years ago

    h/w vendor has already checked and saying its fine from h/w point of view.

     

  • revarooo's avatar
    revarooo
    Level 6
    12 years ago

    Add VERBOSE to the /usr/openv/volmgr/vm.conf file, restart MM services.

    Then next time it goes down, check in the /var/adm/messages file to see if anything is logged.

     

  • Marianne's avatar
    Marianne
    Level 6
    12 years ago

    I agree 100% with revaroo.

    You need to enable verbose logging and check /var/adm/messages.

    This message says that there is a comms issue between the device and OS:

     timed out after waiting 850 seconds for ready, drive 1

    When the drive is mounted, the OS needs to recognise the tape mount.

    To test this process outside of NBU, use robtest to mount a tape in this drive.

    Issue this command from another cmd window:

    mt -f /dev/rmt/##cbn status

    Tell what the result is....

    Please bear in mind that 'hardware' is more than just a tape drive - it is every piece of equipment in the data path - hba in the server, the fiber or scsi cable, if SAN, the swith port and GBICs. If SCSI, the cable length, the terminator, etc...