HP 12000 HP 12200 Gateway Virtual Library System User Guide (BW403-10001, June - Page 174

Solution, Possible causes, Symptom, Device & Media, Properties, Control, Barcode reader support

Get HP 12000 PDF manuals and user guides View all HP 12000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 174 highlights

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

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
Solution
Possible causes
Symptom
first level of logical device binding,
the FC HBA binds the FC WWPN and
operating system path name
(\\.\Tape0) on a Windows host node
1.
Disconnect the Windows node from
the SAN (label and unplug all FC
cables).
FC LUN (Fibre Channel layer devices)
to a SCSI Bus Number, SCSI Target
- but the Windows Device Manager
still shows these virtual tape drive
2.
Delete all files and folders under the
"./system32/NtmsData" folder
ID, and SCSI LUN (SCSI layer device).
At the second level, the Windows
devices as being enabled and at the
original BusNumber/TargetID/LUN
Location.
(location of the system32 folder
varies between Windows versions).
Removable Storage Manager (RSM)
will bind the SCSI Bus Number, SCSI
3.
In the Microsoft Computer
Management window, enable and
start the RSM.
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.
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
Netbackup has a 6 character barcode
limit. Only 6 characters of the actual
The VLS cartridge barcode numbers
displayed on Veritas Netbackup do
be changed. If the shortening of the
VLS cartridge barcode numbers will
be displayed.
not match the actual VLS cartridge
barcode numbers.
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.
Netbackup on HP-UX cannot see
virtual devices on a VLS.
Netbackup on HP-UX cannot build a
device file for a VLS library.
This is normal and will not cause
problems.
Real autoloader libraries do not
support barcodes.
Netbackup does not display the
cartridge barcodes for Autoloader
library emulations on the VLS.
To turn on barcode reader support in
Data Protector:
By default, the barcode reader support
is turned off in Data Protector 5.1.
HP StorageWorks Data Protector 5.1
does not display the VLS cartridge
barcodes.
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
The Removable Storage Manager or
Removable Storage program on a
VLS performance is being reduced by
test unit ready (TURs) from a Windows
host with access to the VLS.
set the startup type to Disabled on the
Windows host is submitting TURs to
the VLS.
Windows host using the Services utility
located under Control Panel >
Administrative Tools.
174
Troubleshooting