HP 12000 User Manual page 174

Symptom
operating system path name
(\\.\Tape0) on a Windows host node
- but the Windows Device Manager
still shows these virtual tape drive
devices as being enabled and at the
original BusNumber/TargetID/LUN
Location.
The VLS cartridge barcode numbers
displayed on Veritas Netbackup do
not match the actual VLS cartridge
barcode numbers.
Netbackup on HP-UX cannot build a
device file for a VLS library.
Netbackup does not display the
cartridge barcodes for Autoloader
library emulations on the VLS.
HP StorageWorks Data Protector 5.1
does not display the VLS cartridge
barcodes.
VLS performance is being reduced by
test unit ready (TURs) from a Windows
host with access to the VLS.
174 Troubleshooting
Possible causes
first level of logical device binding,
the FC HBA binds the FC WWPN and
FC LUN (Fibre Channel layer devices)
to a SCSI Bus Number, SCSI Target
ID, and SCSI LUN (SCSI layer device).
At the second level, the Windows
Removable Storage Manager (RSM)
will bind the SCSI Bus Number, SCSI
Target ID, and SCSI LUN (SCSI layer
device) to an OS \\.\Tape# path
name. Only tape drives are subject to
this second binding level.
NOTE: If you have built and
connected Windows nodes before
installing the VLS system, the Windows
tape device paths can break, change,
or disappear when RSM is run.
(Windows runs RSM by default.)
When RSM initially discovers any
removable storage device, such as a
tape drive, it will make an entry in
NtmsData database. Once a tape
drive is listed in this NtmsData
database, the Windows OS can
potentially either break the second
level OS path name bind or re-bind it
to a different OS path name, even
with RSM in a "Disabled" state.
Netbackup has a 6 character barcode
limit. Only 6 characters of the actual
VLS cartridge barcode numbers will
be displayed.
Netbackup on HP-UX cannot see
virtual devices on a VLS.
Real autoloader libraries do not
support barcodes.
By default, the barcode reader support
is turned off in Data Protector 5.1.
The Removable Storage Manager or
Removable Storage program on a
Windows host is submitting TURs to
the VLS.
Solution
1. Disconnect the Windows node from
the SAN (label and unplug all FC
cables).
2. Delete all files and folders under the
"./system32/NtmsData" folder
(location of the system32 folder
varies between Windows versions).
3. In the Microsoft Computer
Management window, enable and
start the RSM.
4. Bring up the Removable Storage
utility in the Microsoft Computer
Management window.
5. Verify there are no Tape or Library
devices listed (other than the direct
attached devices such as the
CD-ROM drive).
6. Stop and Disable the RSM service
in the Microsoft Computer
Management window.
7. Reconnect the Windows node to the
SAN (plug all FC cables back in to
the original HBA Ports).
8. Repeat this process on all Windows
backup server nodes.
See the Netbackup web site to
determine if the six character limit can
be changed. If the shortening of the
cartridge barcode numbers removes
characters from the barcode numbers,
making them no longer unique, the
barcode numbers cannot be used with
Netbackup. You must create new
cartridges with no more than six
character barcode numbers.
Manually create the device file for the
virtual library. See the Veritas
Netbackup manual.
This is normal and will not cause
problems.
To turn on barcode reader support in
Data Protector:
1. Click Device & Media.
2. Right-click the VLS library name and
select Properties.
3. Click the Control tab.
4. Click the Barcode reader support box
to select it.
Stop the Removable Storage Manager
or Removable Storage program, and
set the startup type to Disabled on the
Windows host using the Services utility
located under Control Panel >
Administrative Tools.