Forum Discussion

Vicky_Kodan's avatar
Vicky_Kodan
Level 3
13 years ago

Invalid Drive Number

Hi All,

 

While trying to up the drive using vmoprcmd I am getting the error as "Invalid Drive Number". Please assist me further what could be done next,

 

#-> ./vmoprcmd -d ds -h test.com -up 5
Invalid Drive Number

#-> ./vmoprcmd -d ds -h test.com -up 7
Invalid Drive Number
 

 

7.1.x and Earlier
Backup and Recovery
NetBackup
  • Marianne's avatar
    Marianne
    13 years ago

    To UP a drive will not resolve MISSING PATH.

    Use tpconfig on media server test.com to delete the drives with MISSING_PATH and rerun device wizard.

    Which drive type are you using (scan command will list drive type and firmware)?

    Also double-check tape driver. If IBM, note the following in HCL regarding IBM tape drivers:

    If using the IBM Windows Tape Device Drivers be sure to choose the install_nonexclusive.exe executable. This option permits a tape drive to be accessed by multiple processes on a Media Server, which is a requirement for NetBackup.
    NetBackup requires the IBM Data Path Failover feature to be disabled on the IBM tape device driver. To disable this feature, open the reg folder of the IBM driver
    package, double-click DisableDPF.reg, and reboot the system.
    - IBMTape driver level 6.2.1.7 tested on Windows

    Please also ensure that Persistent Binding is done at HBA level.

    Which Windows and NBU version on this media server?

  • Marianne's avatar
    Marianne
    Level 6
    13 years ago

    Please post output of all of the following:

    tpconfig -l

    vmoprcmd -d

    scan

    PS: have you tried the command without '-d ds'?

    vmoprcmd -h <media-server> -up <drive-index>

  • Vicky_Kodan's avatar
    Vicky_Kodan
    Level 3
    13 years ago

     

    Thanks for the reply, please find the required output as given below. Error is with drive 1,2 and 4

    #-> ./vmoprcmd -h test.com -up 1
    Invalid Drive Number 

    tpconfig -l

    Device Robot Drive       Robot                    Drive              Device
    Type     Num Index  Type DrNum Status  Comment    Name               Path
    robot      0    -    TLD    -       -  -          -                  abc.com
      drive    -    0  hcart   43      UP  -          WINDOWS_SHARED_43  {0,0,0,3}
      drive    -    1  hcart   40    DOWN  -          WINDOWS_SHARED_40  MISSING_PATH:{1,0,1,4}:F0020E80E
      drive    -    2  hcart   48    DOWN  -          WINDOWS_SHARED_48  MISSING_PATH:{1,0,2,4}:F0020E811
      drive    -    3  hcart   44      UP  -          WINDOWS_SHARED_44  {0,0,0,4}
      drive    -    4  hcart   45    DOWN  -          WINDOWS_SHARED_45  MISSING_PATH:{0,0,1,1}:F0020E810
      drive    -    5  hcart   46      UP  -          WINDOWS_SHARED_46  {0,0,1,2}
      drive    -    6  hcart   42      UP  -          WINDOWS_SHARED_42  {1,0,0,2}
      drive    -    7  hcart   39      UP  -          WINDOWS_SHARED_39  {1,0,1,3}

     

    Scan is giving the list of drive as well

  • Marianne's avatar
    Marianne
    Level 6
    13 years ago

    To UP a drive will not resolve MISSING PATH.

    Use tpconfig on media server test.com to delete the drives with MISSING_PATH and rerun device wizard.

    Which drive type are you using (scan command will list drive type and firmware)?

    Also double-check tape driver. If IBM, note the following in HCL regarding IBM tape drivers:

    If using the IBM Windows Tape Device Drivers be sure to choose the install_nonexclusive.exe executable. This option permits a tape drive to be accessed by multiple processes on a Media Server, which is a requirement for NetBackup.
    NetBackup requires the IBM Data Path Failover feature to be disabled on the IBM tape device driver. To disable this feature, open the reg folder of the IBM driver
    package, double-click DisableDPF.reg, and reboot the system.
    - IBMTape driver level 6.2.1.7 tested on Windows

    Please also ensure that Persistent Binding is done at HBA level.

    Which Windows and NBU version on this media server?

  • Vicky_Kodan's avatar
    Vicky_Kodan
    Level 3
    13 years ago

    HARDWARE Windows x86
    VERSION NetBackup 6.5.6
    RELEASEDATE Fri Apr 23 17:08:38 CDT 2010
    BUILDNUMBER 20100423

    Windows 2K3 server

     

    tape drivers are also there ,

     

    Please confirm if there is any other way to resolve this without rerun device configuration. Because the master server does contains the huge amount of client for backup and I cannot make all of them hamper due to this issue.

    As after Device configuration NBU services will get recycled, and due to this many backup will get failed.

    C:\VERITAS\Volmgr\bin>scan
    ************************************************************
    *********************** SDT_TAPE    ************************
    *********************** SDT_CHANGER ************************
    *********************** SDT_OPTICAL ************************
    ************************************************************
    ------------------------------------------------------------
    Device Name  : "Tape2"
    Passthru Name: "Tape2"
    Volume Header: ""
    Port: 0; Bus: 0; Target: 1; LUN: 1
    Inquiry    : "IBM     ULTRIUM-TD4      "
    Vendor ID  : "IBM     "
    Product ID : "ULTRIUM-TD4     "
    Product Rev: " "
    Serial Number: 0
    WWN          : ""
    WWN Id Type  : 0
    Device Identifier: "IBM     ULTRIUM-TD4     0
    Device Type    : SDT_TAPE
    NetBackup Drive Type: 3
    Removable      : Yes
    Device Supports: SCSI-3
    Flags : 0x0
    Reason: 0x0
    ------------------------------------------------------------
    Device Name  : "Tape3"
    Passthru Name: "Tape3"
    Volume Header: ""
    Port: 0; Bus: 0; Target: 1; LUN: 2
    Inquiry    : "IBM     ULTRIUM-TD4      "
    Vendor ID  : "IBM     "
    Product ID : "ULTRIUM-TD4     "
    Product Rev: " "
    Serial Number: 0
    WWN          : ""
    WWN Id Type  : 0
    Device Identifier: "IBM     ULTRIUM-TD4     0
    Device Type    : SDT_TAPE
    NetBackup Drive Type: 3
    Removable      : Yes
    Device Supports: SCSI-3
    Flags : 0x0
    Reason: 0x0
    ------------------------------------------------------------
    Device Name  : "Tape4"
    Passthru Name: "Tape4"
    Volume Header: ""
    Port: 1; Bus: 0; Target: 0; LUN: 1
    Inquiry    : "IBM     ULTRIUM-TD4      "
    Vendor ID  : "IBM     "
    Product ID : "ULTRIUM-TD4     "
    Product Rev: " "
    Serial Number: 0
    WWN          : ""
    WWN Id Type  : 0
    Device Identifier: "IBM     ULTRIUM-TD4     0
    Device Type    : SDT_TAPE
    NetBackup Drive Type: 3
    Removable      : Yes
    Device Supports: SCSI-3
    Flags : 0x0
    Reason: 0x0
     

  • Mark_Solutions's avatar
    Mark_Solutions
    Level 6
    13 years ago

    Unfortunately and device change will require the device manager service to re-start to register the change

    You could try making the changes manually (opening the drive properties and browsing for the correct paths) and then when it asks whether to re-start the service say "no" but it may not actually work until the service gets a re-start

    Try it as that is your only hoe - the device wizard will not give you the option

  • Marianne's avatar
    Marianne
    Level 6
    13 years ago

    If you have enabled Checkpoint Restart in your policies and the backups are not DB agent backups, you will be able to suspend the backups and fix your devices.

    It seems that scan only sees 3 tape drives - according to tpconfig output there should be 8?

    You also need to confirm that the correct IBM tape driver is being used or else the Symantec Tape driver (since your media server is 32-bit OS) and that Persistent Binding is enabled at HBA level.

  • J_H_Is_gone's avatar
    J_H_Is_gone
    Level 6
    13 years ago

    I see this a log on my win 2k3 media server

    start/right click my computer/properties

    hardware tab

    device manager

    expand out the tape drives

    open properties of each tape drive

    you should have the following tabs General/Tape Sym Name/Tape Drive Prarm/Driver/Details

    do this for each drive

    if you only see like 3 tabs - then reapply the driver to the tape drive - you should then be able to go back into NB and fix it ( I use SSO - so I remove the drive for the bad media server only )- then go back and re add it - but you will need to let it restart the device manger on that media server - so that media server should not be doing any other jobs