Symptom
Possible causes Solution
The virtual tape drive
devices either disappear
or move to a different
operating system path
name (\\.\Tape0) on
a Windows host node
-buttheWindows
Device Manager still
shows these virtual tape
drive devices as being
enabled and at the
original BusNumber/
TargetID/LUN Location.
There are two levels of logical device
binding in the Windows OS. At the
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 L UN (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 n
odes before installing
the VLS s ystem, the Windows
tape device paths can break,
change, o
r disappear when RSM
is run. (Windows runs RSM by
default.) When RSM initially
discove
rs any removable storage
device, such as a tape drive, it
will make an entry in N tm sD ata
databa
se. 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
adifferentOSpathname,even
with R
SM in a "Disabled" state.
Delete the Windows NtmsData
database and put the RSM into the
Disabled state using the following
procedure :
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 from 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 original HBA Ports)
8. Repeat this process on all
Windows backup server nodes
The VLS cartridge
barcode numbers
displayed on Veritas
Netbackup do not match
the actual VLS cartridge
barcode numbers.
Netbackup has a 6 character
barcode limit. Only 6 characters of
the actual VLS cartridge barcode
numbers will be displayed.
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.
Netbackup on HP-UX
cannot build a device
file for a VLS library(s).
Netbackup on HP-UX cannot see
virtual devices on a VLS.
Manually create the device file for
the virtual library(s). See the Veritas
Netbackup manual.
Ne
tbackup does not
d
isplay the cartridge
barcodes for Autoloader
library emulations on the
VLS.
Re
al autoloader libraries do not
s
upport barcodes.
Th
is is normal and will not cause
p
roblems.
148
Troubleshooting
To Next Page
Loading...
