Invalid Drive Number

Question

Hi All,
&nbsp;
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,
&nbsp;
#-&gt; ./vmoprcmd -d ds -h test.com -up 5
	Invalid Drive Number
#-&gt; ./vmoprcmd -d ds -h test.com -up 7
	Invalid Drive Number
	&nbsp;
&nbsp;

marianne · Accepted Answer

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 · Answer

Please post output of all of the following:
tpconfig -l
vmoprcmd -d
scan
PS: have you tried the command without '-d ds'?
vmoprcmd -h &lt;media-server&gt; -up &lt;drive-index&gt;

vicky_kodan · Answer

&nbsp;
Thanks for the reply, please find the required output as given below. Error is with drive 1,2 and 4
#-&gt; ./vmoprcmd -h test.com -up 1
	Invalid Drive Number&nbsp;
tpconfig -l
Device Robot Drive&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Robot&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Drive&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Device
	Type&nbsp;&nbsp;&nbsp;&nbsp; Num Index&nbsp; Type DrNum Status&nbsp; Comment&nbsp;&nbsp;&nbsp; Name&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Path
	robot&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp; TLD&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; abc.com
	&nbsp; drive&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp; 0&nbsp; hcart&nbsp;&nbsp; 43&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; UP&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; WINDOWS_SHARED_43&nbsp; {0,0,0,3}
	&nbsp; drive&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp; 1&nbsp; hcart&nbsp;&nbsp; 40&nbsp;&nbsp;&nbsp; DOWN&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; WINDOWS_SHARED_40&nbsp; MISSING_PATH:{1,0,1,4}:F0020E80E
	&nbsp; drive&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp; 2&nbsp; hcart&nbsp;&nbsp; 48&nbsp;&nbsp;&nbsp; DOWN&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; WINDOWS_SHARED_48&nbsp; MISSING_PATH:{1,0,2,4}:F0020E811
	&nbsp; drive&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp; 3&nbsp; hcart&nbsp;&nbsp; 44&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; UP&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; WINDOWS_SHARED_44&nbsp; {0,0,0,4}
	&nbsp; drive&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp; 4&nbsp; hcart&nbsp;&nbsp; 45&nbsp;&nbsp;&nbsp; DOWN&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; WINDOWS_SHARED_45&nbsp; MISSING_PATH:{0,0,1,1}:F0020E810
	&nbsp; drive&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp; 5&nbsp; hcart&nbsp;&nbsp; 46&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; UP&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; WINDOWS_SHARED_46&nbsp; {0,0,1,2}
	&nbsp; drive&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp; 6&nbsp; hcart&nbsp;&nbsp; 42&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; UP&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; WINDOWS_SHARED_42&nbsp; {1,0,0,2}
	&nbsp; drive&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp; 7&nbsp; hcart&nbsp;&nbsp; 39&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; UP&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; WINDOWS_SHARED_39&nbsp; {1,0,1,3}
&nbsp;
Scan is giving the list of drive as well

vicky_kodan · Answer

HARDWARE Windows x86
	VERSION NetBackup 6.5.6
	RELEASEDATE Fri Apr 23 17:08:38 CDT 2010
	BUILDNUMBER 20100423
Windows 2K3 server
&nbsp;
tape drivers are also there ,
&nbsp;
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&gt;scan
	************************************************************
	*********************** SDT_TAPE&nbsp;&nbsp;&nbsp; ************************
	*********************** SDT_CHANGER ************************
	*********************** SDT_OPTICAL ************************
	************************************************************
	------------------------------------------------------------
	Device Name&nbsp; : "Tape2"
	Passthru Name: "Tape2"
	Volume Header: ""
	Port: 0; Bus: 0; Target: 1; LUN: 1
	Inquiry&nbsp;&nbsp;&nbsp; : "IBM&nbsp;&nbsp;&nbsp;&nbsp; ULTRIUM-TD4&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "
	Vendor ID&nbsp; : "IBM&nbsp;&nbsp;&nbsp;&nbsp; "
	Product ID : "ULTRIUM-TD4&nbsp;&nbsp;&nbsp;&nbsp; "
	Product Rev: " "
	Serial Number: 0
	WWN&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : ""
	WWN Id Type&nbsp; : 0
	Device Identifier: "IBM&nbsp;&nbsp;&nbsp;&nbsp; ULTRIUM-TD4&nbsp;&nbsp;&nbsp;&nbsp; 0
	Device Type&nbsp;&nbsp;&nbsp; : SDT_TAPE
	NetBackup Drive Type: 3
	Removable&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : Yes
	Device Supports: SCSI-3
	Flags : 0x0
	Reason: 0x0
	------------------------------------------------------------
	Device Name&nbsp; : "Tape3"
	Passthru Name: "Tape3"
	Volume Header: ""
	Port: 0; Bus: 0; Target: 1; LUN: 2
	Inquiry&nbsp;&nbsp;&nbsp; : "IBM&nbsp;&nbsp;&nbsp;&nbsp; ULTRIUM-TD4&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "
	Vendor ID&nbsp; : "IBM&nbsp;&nbsp;&nbsp;&nbsp; "
	Product ID : "ULTRIUM-TD4&nbsp;&nbsp;&nbsp;&nbsp; "
	Product Rev: " "
	Serial Number: 0
	WWN&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : ""
	WWN Id Type&nbsp; : 0
	Device Identifier: "IBM&nbsp;&nbsp;&nbsp;&nbsp; ULTRIUM-TD4&nbsp;&nbsp;&nbsp;&nbsp; 0
	Device Type&nbsp;&nbsp;&nbsp; : SDT_TAPE
	NetBackup Drive Type: 3
	Removable&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : Yes
	Device Supports: SCSI-3
	Flags : 0x0
	Reason: 0x0
	------------------------------------------------------------
	Device Name&nbsp; : "Tape4"
	Passthru Name: "Tape4"
	Volume Header: ""
	Port: 1; Bus: 0; Target: 0; LUN: 1
	Inquiry&nbsp;&nbsp;&nbsp; : "IBM&nbsp;&nbsp;&nbsp;&nbsp; ULTRIUM-TD4&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "
	Vendor ID&nbsp; : "IBM&nbsp;&nbsp;&nbsp;&nbsp; "
	Product ID : "ULTRIUM-TD4&nbsp;&nbsp;&nbsp;&nbsp; "
	Product Rev: " "
	Serial Number: 0
	WWN&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : ""
	WWN Id Type&nbsp; : 0
	Device Identifier: "IBM&nbsp;&nbsp;&nbsp;&nbsp; ULTRIUM-TD4&nbsp;&nbsp;&nbsp;&nbsp; 0
	Device Type&nbsp;&nbsp;&nbsp; : SDT_TAPE
	NetBackup Drive Type: 3
	Removable&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : Yes
	Device Supports: SCSI-3
	Flags : 0x0
	Reason: 0x0
	&nbsp;

mark_solutions · Answer

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 · Answer

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.

Forum Discussion

Invalid Drive Number

9 Replies

Related Content

Invalid Drive Index when trying to delete drive

backupTime ge invalid OData filter

netbackup client host properties invalid error number

Tape drive serial number mismatch

Invalid Drive Type/Density

Recent Discussions

command: bperror

MS-SharePoint policy restore error (2804) .

How to restore a backup

How to configure RBAC

10 years old netbackup appliance database service down, ssl certification out date