| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 326.1 | | BACHUS::VERCAMMEN | You never walk alone... | Fri Mar 14 1997 02:54 | 23 |
|
Richard,
The TAPESTART.COM media triplet specified for both tape drives
SHOULD specify exactly the same media type as you have defined
in the HSM DEVICE definition...!!! ('CompacTape III, Loader' in
your case).
Paragraph 3.8.2 of the HSM doc contains a complete step-by-step
configuration example for a TZ877. Should be the same procedure
for your drives (TF857).
Regards,
\Jan
|
| 326.2 | | RUPERT::BROWN | Govt. Exile living in Nutwood... | Fri Mar 14 1997 03:49 | 11 |
| Jan,
Thanks for taking the time to help out on this one. I should
point out that we are running in Basic mode so I'm not sure
that TAPESTART.COM is used in this mode ?
It's strange I just had a look at device $1$MIA1 and it is
allocated to HSM$SHELF_HNDLR process but smu show device says
it is 'not configured'
Gary
|
| 326.3 | Did you define Robotname ? | ATZIS1::KARTNER_M | HOUSTON, we have a problem | Mon Mar 17 1997 00:08 | 7 |
| Hi!
HAve you defined a robot name ? This has do be done in BASIC mode.
Could you provide more infos (show facility,sho shelv, sho archive,..)
bye
Michael
|
| 326.4 | | RUPERT::BROWN | Govt. Exile living in Nutwood... | Wed Mar 19 1997 04:15 | 86 |
| Well we configured the devices with a robot name and it now shows them
both as configured but fails to mount the tapes with the following problem
The magazine loaded in drive _$1$MIA1: has an invalid HSM configuration.
Please reconfigure magazine before reloading
See HSM Guide to Operations - Magazine Loaders
and likewise for $1$MIA0:
mia1: has HS1001 loaded and
mia0: has HS0001 and HS0002
SMU> show facility
HSM for OpenVMS is enabled for Shelving and Unshelving
Facility history:
Created: 13-MAR-1997 11:59:15.38
Revised: 17-MAR-1997 17:26:09.35
Designated servers: Any cluster member
Current server: HOOPY
Catalog server: Disabled
Event logging: Audit
Error
Exception
HSM mode: Basic
Remaining license: 20 gigabytes
SMU> show shelf
Shelf HSM$DEFAULT_SHELF is enabled for Shelving and Unshelving
Catalog File: DISK$GENERAL:[HSM$SERVER.CATALOG]HSM$CATALOG.SYS
Shelf History:
Created: 13-MAR-1997 11:59:14.29
Revised: 17-MAR-1997 17:53:43.33
Backup Verification: Off
Save Time: <none>
Updates Saved: All
Archive Classes:
Archive list: HSM$ARCHIVE01 id: 1
HSM$ARCHIVE02 id: 2
Restore list: HSM$ARCHIVE01 id: 1
HSM$ARCHIVE02 id: 2
SMU> show archive
HSM$ARCHIVE01 has been used
Identifier: 1
Media type: CompacTape III
Label: HS0001
Position: 3
Device refs: 1
Shelf refs: 2
HSM$ARCHIVE02 has not been used
Identifier: 2
Media type: CompacTape III, Loader
Label: HS1001
Position: 0
Device refs: 1
Shelf refs: 2
SMU> show device
HSM drive HSM$DEFAULT_DEVICE is enabled.
Shared access: < shelve, unshelve >
Drive status: Not configured
Media type: Unknown Type
Robot name: <none>
Enabled archives: <none>
HSM drive _$1$MIA0: is enabled.
Dedicated access: < shelve, unshelve >
Drive status: Configured
Media type: CompacTape III, Loader
Robot name: _$1$MIA0:
Enabled archives: HSM$ARCHIVE01 id: 1
HSM drive _$1$MIA1: is enabled.
Dedicated access: < shelve, unshelve >
Drive status: Configured
Media type: CompacTape III, Loader
Robot name: _$1$MIA1:
Enabled archives: HSM$ARCHIVE02 id: 2
|
| 326.5 | is #2 possible? | COOKIE::HOLSINGER | HSM Engineering, DTN 522-2843 | Wed Mar 19 1997 15:01 | 16 |
| >The magazine loaded in drive _$1$MIA1: has an invalid HSM configuration.
>Please reconfigure magazine before reloading
>See HSM Guide to Operations - Magazine Loaders
I checked the code which raises this particular exception. It can occur either
of the following cases:
1. The magazine contains no tapes which follow the HSM basic mode naming
convention.
2. The magazine contains two or more tapes with identical volume names
(which pass the HSM basic mode naming convention).
Please check the magazines for either of these conditions.
Regards,
/Paul
|
| 326.6 | I don't think so | RUPERT::BROWN | Govt. Exile living in Nutwood... | Thu Mar 20 1997 01:45 | 39 |
| HOOPY_V6.2> smu
SMU> shutdown/force
SMU> Exit
HOOPY_V6.2> mount/ov=id $1$mia0:
%MOUNT-I-MOUNTED, HS0001 mounted on _$1$MIA0: (KRIKIT)
HOOPY_V6.2> dism/nounlo $1$mia0:
HOOPY_V6.2> mount/ov=id $1$mia1:
%MOUNT-I-MOUNTED, HS1001 mounted on _$1$MIA1: (ARTHUR)
HOOPY_V6.2> dism/nounlo $1$mia1:
started hsm again via smu start and attempted to shelve a file
opcom displayed
%%%%%%%%%%% OPCOM 20-MAR-1997 08:40:31.89 %%%%%%%%%%%
Request 317, from user HSM$SERVER on HOOPY
Please load magazine containing volume "HS1001" into drive _$1$MIA1:
%%%%%%%%%%% OPCOM 20-MAR-1997 08:40:32.89 %%%%%%%%%%%
Request 318, from user HSM$SERVER on HOOPY
Please load magazine containing volume "HS0001" into drive _$1$MIA0:
8:41:56.38, request 317 was completed by operator _HOOPY$TNA54:
%%%%%%%%%%% OPCOM 20-MAR-1997 08:41:56.73 %%%%%%%%%%%
Message from user HSM$SERVER on HOOPY
The magazine loaded in drive _$1$MIA1: has an invalid HSM configuration.
Please reconfigure magazine before reloading
See HSM Guide to Operations - Magazine Loaders
%%%%%%%%%%% OPCOM 20-MAR-1997 08:41:56.74 %%%%%%%%%%%
Request 319, from user HSM$SERVER on HOOPY
Please load magazine containing volume "HS1001" into drive _$1$MIA1:
and likewise for mia0 (only volume HS0001)
confused, I sure am ...
you want to log on and take a look ?
|
| 326.7 | Tape Drives TMSCP-served, but Robot Loaders are not. | KERNEL::COURTNEYM | Save Water: Dilute it! | Tue Apr 29 1997 04:08 | 62 |
| Hi,
I'm the Basingstoke CSC support specialist helping Richard with
this problem.
Richard is using HSM BASIC mode, to shelve/archive to 2 TF857s which
are connected via DSSI to a 4-node mixed architecture cluster.
One TF85 was visible via DSSI to VAXes, KRIKIT and ARTHUR, being
served to the other nodes in the cluster via TMSCP.
Originally, the shelf server was running on node HOOPY,
We solved the error by re-configuring the HSM shelf server, so it
ran on one of the nodes where the tape jukeboxes on the DSSI are
'directly connected'. This means that for all shelves, all archive
classes can use only one of the tape jukeboxes - not ideal in case of
a failure and less than Digital's recommendations in the docs.
The V2.0A release notes allude to this fact, whilst discussing SCSI
tape jukes, I assume this also applies to DSSI, though it's not
stated whether this also applies to non-SCSI configurations.
EXTRACT FROM DOCUMENTS: POLYCENTER HSM for OpenVMS V2.0A Release Notes
(2.1 Basic Mode Robot Name Support)
POLYCENTER HSM Guide to Operations
(4.1.18 TMSCP-Served Tapes)
"However, for robotically-controlled tape jukeboxes and magazine
loaders, cluster-wide support for the robot operations is not
provided. This means that the robot load/unload commands must be
issued on the node on which the device resides, meaning that the shelf
server must also be defined to be that node. This applies to both
Basic and Plus modes...."
If you try to talk to the loader via DSSI, and you don't have a
direct connection, you get this error:
$ show dev mia0
Device Device Error Volume Free Trans Mnt
Name Status Count Label Blocks Count Cnt
$1$MIA0: (KRIKIT) Online 0
$ set host /dup /server=mscp$dup /task=params krikit
%HSCPAD-F-FAILCONSRVR, Failed to establish connection to server
-SYSTEM-F-NOLISTENER, specified remote system process not listening
This is what alerted me to the problem, when I queried myself as to
what the node name for the tape controller should be - I found TAPEC0
was the actual node, and it was served to the cluster by node KRIKIT.
But when trying to use HSM Basic mode, you just get this:
The magazine loaded in drive _$1$MIA1: has an invalid HSM configuration.
Please reconfigure magazine before reloading
See HSM Guide to Operations - Magazine Loaders
Is is possible to change either the error message or add a note in
the docs to cover this possiblity?
Mark Courtney, Software Specialist,
OpenVMS Support, UK Customer Support Center (UVO)
|