Forum Discussion

ruterjunior's avatar
ruterjunior
Level 4
10 years ago

Netbackup TLD Down everyday

Hi folks, i have a little problem...

Everyday my TLD have status down, and my backups they are not made.

I do not know what to do.

chek this out.

before comand to drive up....


D:\Program Files\Veritas\Volmgr\bin>tpconfig.exe -d
Id  DriveName           Type   Residence
      SCSI coordinates/Path                                            Status
****************************************************************************
0   QUANTUM.ULTRIUM5.000 hcart2 TLD(0)  DRIVE=1
      {3,0,3,0}                                                        UP

Currently defined robotics are:
  TLD(0)     SCSI coordinates = {3,0,3,1}

EMM Server = srv-***-nbkp.***


D:\Program Files\Veritas\Volmgr\bin>

*======================================================================

D:\Program Files\Veritas\Volmgr\bin>vmoprcmd.exe -d

                                PENDING REQUESTS

                                     <NONE>

                                  DRIVE STATUS

Drv Type   Control  User      Label  RecMID  ExtMID  Ready   Wr.Enbl.  ReqId
  0 hcart2   TLD                -                     No       -         0

                             ADDITIONAL DRIVE STATUS

Drv DriveName            Shared    Assigned        Comment
  0 QUANTUM.ULTRIUM5.000  No       -

D:\Program Files\Veritas\Volmgr\bin>

======================================================================


D:\Program Files\Veritas\Volmgr\bin>tpautoconf.exe -t
TPAC60 QUANTUM ULTRIUM 5       3210 HU1305UFMM 3 0 3 0 Tape0 - -

D:\Program Files\Veritas\Volmgr\bin>

*======================================================================


D:\Program Files\Veritas\Volmgr\bin>scan
************************************************************
*********************** SDT_TAPE    ************************
*********************** SDT_CHANGER ************************
************************************************************
------------------------------------------------------------
Device Name  : "Tape0"
Passthru Name: "Tape0"
Volume Header: ""
Port: 3; Bus: 0; Target: 3; LUN: 0
Inquiry    : "QUANTUM ULTRIUM 5       3210"
Vendor ID  : "QUANTUM "
Product ID : "ULTRIUM 5       "
Product Rev: "3210"
Serial Number: "HU1305UFMM"
WWN          : ""
WWN Id Type  : 0
Device Identifier: ""
Device Type    : SDT_TAPE
NetBackup Drive Type: 10
Removable      : Yes
Device Supports: SCSI-6
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name  : "Changer0"
Passthru Name: "Changer0"
Volume Header: ""
Port: 3; Bus: 0; Target: 3; LUN: 1
Inquiry    : "DELL    PV-124T         0091"
Vendor ID  : "DELL    "
Product ID : "PV-124T         "
Product Rev: "0091"
Serial Number: "CC3BH60676"
WWN          : ""
WWN Id Type  : 0
Device Identifier: "DELL    PV-124T         CC3BH60676"
Device Type    : SDT_CHANGER
NetBackup Robot Type: 8
Removable      : Yes
Device Supports: SCSI-2
Number of Drives : 1
Number of Slots  : 8
Number of Media Access Ports: 0
Drive 1 Serial Number      : "HU1305UFMM"
Flags : 0x0
Reason: 0x0

D:\Program Files\Veritas\Volmgr\bin>

*======================================================================


D:\Program Files\Veritas\Volmgr\bin>vmoprcmd.exe -d

                                PENDING REQUESTS

                                     <NONE>

                                  DRIVE STATUS

Drv Type   Control  User      Label  RecMID  ExtMID  Ready   Wr.Enbl.  ReqId
  0 hcart2   TLD                -                     No       -         0

                             ADDITIONAL DRIVE STATUS

Drv DriveName            Shared    Assigned        Comment
  0 QUANTUM.ULTRIUM5.000  No       -

D:\Program Files\Veritas\Volmgr\bin>


*======================================================================


D:\Program Files\Veritas\Volmgr\bin>vmglob.exe -listall
=====================================================================
device type:               robot
device name:               ROBOT0
serial number:             CC3BH60676
hostname:                  srv-***-nbkp.***
volume database hostname:  srv-***-nbkp.***
robot number:              0
robot drive number:        -1
robot type:                TLD
drive type:                -
flags:                     0x0
worldwide name:            -
worldwide name type:       0
inquiry:                   DELL    PV-124T         0090
library name:              -
vendor drive name:         -
robot control host:        -
ACS:                       -1
LSM:                       -1
PANEL:                     -1
DRIVE:                     -1
=====================================================================
device type:               drive
device name:               QUANTUM.ULTRIUM5.000
serial number:             HU1305UFMM
hostname:                  srv-***-nbkp.***
volume database hostname:  srv-***-nbkp.***
robot number:              0
robot drive number:        1
robot type:                TLD
drive type:                hcart2
flags:                     0x0
worldwide name:            -
worldwide name type:       0
inquiry:                   QUANTUM ULTRIUM 5       3210
library name:              -
vendor drive name:         -
robot control host:        -
ACS:                       -1
LSM:                       -1
PANEL:                     -1
DRIVE:                     -1
=====================================================================

D:\Program Files\Veritas\Volmgr\bin>

*=====================================================================


D:\Program Files\Veritas\Volmgr\bin>tpconfig.exe -emm_dev_list
==============================================================================
Robot:                          ROBOT0
Robot Number:                   0
Robot Type:                     TLD(8)
Media Server:                   srv-***-nbkp.***
Port:                           3
Bus:                            0
Target:                         3
Lun:                            1
PartiallyConfigured:            0
Pird:                           0
Host:                           -
Apath:                          -
NDMP Attach Host:               -
VMhost:                         srv-***-nbkp.***
DAhost:                         srv-***-nbkp.***
SN:                             CC3BH60676
Inquiry:                        DELL    PV-124T         0090
WorldWideId:                    -
Old DAhost:                     srv-***-nbkp.***
RSM GUID:                       00000000-0000-0000-0000-000000000000
==============================================================================
==============================================================================
Drive:                          QUANTUM.ULTRIUM5.000
Index:                          0
Drive Type:                     hcart2(10)
Media Server:                   srv-***-nbkp.***
Occupy Index:                   0
Opr Count:                      0
Status:                         2
Saved Mode Bits:                0
Access Mode:                    82
Robot Type:                     TLD(8)
Robot Number:                   0
Loc1:                           1
Loc2:                           -1
Loc3:                           -1
Loc4:                           -1
Loc5:                           0
Port:                           3
Bus:                            0
Target:                         3
Lun:                            0
VH Saved Mode Bits:             0
Flags:                          0
PathFlags:                      0
DeviceFlags:                    0
Time Mounted:                   0
Total Time Mounted:             66
Cleaning Frequency:             0
Last Time Cleaned:              0
Vendor Device Num:              0
Tape Alert 1:                   0
Tape Alert 2:                   0
Last DA Call Time:              0
Application Type:               0
Drive Path:                     -
Volume Header Drive Path:       -
Vendor Drive Name:              -
Current RVSN:                   -
Current EVSN:                   -
Current User:                   -
Operator Comment:               -
SN:                             HU1305UFMM
Inquiry Info:                   QUANTUM ULTRIUM 5       3210
World Wide Id:                  -
NDMP Host:                      -
Scan Host:                      -
Assign Host:                    -
RSM GUID:                       00000000-0000-0000-0000-000000000000
APPL_GUID:                      00000000-0000-0000-0000-000000000000
==============================================================================
==============================================================================
Master Server:                  srv-***-nbkp.***
NetBackup Version:              7.6.1(761000)
Host OperatingSystem:           11
MachineState:                   ACTIVE
==============================================================================
Virtual Machine Host Name:           srv-vcsa-***.***
Virtual Machine Type:                VMware Virtual Center Server
SubType:                             (1)
User Id:                             ***\usr_netbackup
Required Port:                       443
==============================================================================
EMM Server:                     srv-***-nbkp.***

D:\Program Files\Veritas\Volmgr\bin>

Backup and Recovery
Configuring
Error messages
NetBackup
Reporting
Troubleshooting
Windows Server (2003-2008)
  • ruterjunior's avatar
    ruterjunior
    9 years ago

    i belive that, suggestion of Dell Support based in shot in the dark.

    But my drivers are too old... 

    i have many another errors, 

     

    may terminate this topic... i open anothers after.

     

    Thanks folks

32 Replies

Sort By
  • sdo's avatar
    sdo
    Moderator
    10 years ago

    See this for how to create Volmgr logs:

    https://www-secure.symantec.com/connect/forums/troubleshoot-drive-down-issue

    ...and add VERBOSE to vm.conf.

    .

    Do you see any system and/or hardware events in Windows event log?

    Is AV running on the server?  AV software has been known to cause NetBackup Device Manager to close/fail/stop.

  • mph999's avatar
    mph999
    Level 6
    10 years ago

    Also get the bptm log from the media server.

    See my signiture for how to set logs.

    If robot logs are needed, you need to set robots log on the roobot control host AND the media server with the drives, if the media server with the drives is a different server than the robot control host.

    I see reference in the above outputs to VMware.  Is this a virtual media server, because if it is, tape is not supported and won't work.  No way around this, it is a VMware limitation, not NetBackup.

  • ruterjunior's avatar
    ruterjunior
    Level 4
    10 years ago

    Hi folks... thanks for you'r help... 


    I created folders for collect of logs, 
    Windows events i see some events the netbackup... tomorrow i show for us

  • mph999's avatar
    mph999
    Level 6
    10 years ago

    Please be sure to post win event logs in txt format, and upload the logs as txt files - thanks.

  • ruterjunior's avatar
    ruterjunior
    Level 4
    10 years ago

    Hello... good morning...

     

    logs attach

     

    every day same drives are down

    drive_down.PNG

    drive_down2.PNG

    down_drive3.PNG

     

    but this patch another error... up drive dont solve... 

    drive_down4.PNG

     

     

  • Michael_G_Ander's avatar
    Michael_G_Ander
    Level 6
    10 years ago

    You need to get the path reenabled in the OS before UP'ing the drive

    Assuming FC connected tape drives, the approach I would use is

    1. Check the tape drive status in the robot interface

    2. Check that the drive are logged in to the Fiber switch

    3. Check that the HBA has the tape drives registered (HBAnyware/Onecommand for Emulex, Sansurfer for Qlogic)

    4. Check that the OS can see the tape drives and have the drivers loaded (Device manager)

    5. Reset and UP drive in Netbackup and maybe do a rescan if the SCSI ID has changed. Persistent binding on the HBA is the cure for that.

    For the original problem check if there something other than netbackup accessing the drive, know that RSM and some monitor software can give that issue. Aslo in some version of windows the driver probe function can cause things like this.

    Hope this helps

     

  • Marianne's avatar
    Marianne
    Level 6
    10 years ago

    Any device-related errors in Windows Event Viewer System log?

    MISSING_PATH seems to indicate device comms issue at OS level.

  • ruterjunior's avatar
    ruterjunior
    Level 4
    10 years ago

    I found possible problem... 

     

    drivers with robots are down ever... is too old...

     

    drivers with robots are up ever... is new drivers...

    Drive old (problem)

    drive_quantum.PNG

    Drive New (no problems)

    drive_quantum_UPdated.PNG

  • Marianne's avatar
    Marianne
    Level 6
    10 years ago

    NBU does not need vendor driver for Medium changer (robot).

    It works 100% fine with the Windows driver that is listed in Device Manager as 'Unknown Medium Changer'.