| Title: | Storage Library System |
| Moderator: | COOKIE::REUTER |
| Created: | Sun Oct 13 1991 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 2270 |
| Total number of notes: | 7850 |
Hello to everybody.
I have a customer using SLS V2.7 to manage his backup jobs - scheduled
through DECscheduler - on a TL820.
Whenever for some reason he aborts the job via DECscheduler, the
process obviously dies, and the cartridge is unloaded but still in the
drive. The consequence is that next backup job allocates the drive,
seen as "available" under VMS, but then failes with an access violation
or dies anyway while trying to load another volume.
I have heard this is automatically handled in V2.8A, which is planned
to be installed at this customer's site.
Does anybody know if this is true?
(The same kind of backup performed on a TA90 already works unloading the
previous tape before loading next one)
Thanks for help,
Iolanda
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2238.1 | COOKIE::MCCLELLAND | Marty, SLS/MDMS Engineering | Tue Apr 22 1997 10:37 | 14 | |
> Whenever for some reason he aborts the job via DECscheduler, the
> process obviously dies, and the cartridge is unloaded but still in the
> drive. The consequence is that next backup job allocates the drive,
> seen as "available" under VMS, but then failes with an access violation
> or dies anyway while trying to load another volume.
Sorry, I don't understand your problem statement. I can say that
your access violation is most likely fixed in V2.8A. However, rather
than the accvio, you'll probably still see MRD_UNLOAD_FAIL because
the database shows the volume as still loaded when actually it is not.
Since the process was terminated abnormally, you can expect to see
this kind of result.
Marty
| |||||
| 2238.2 | ROM01::FRISINA | Thu Apr 24 1997 03:16 | 26 | ||
I was probably not able to explain the problem clearly.
The question was:
Phase 1:
Abort of an SLS process, so that the result is:
- cartridge still in the drive;
- SLS database shows volume is in the drive;
- VMS device related to the drive is available for use
Phase 2:
Next SLS backup is executed. The question is:
- Will SLS (or the robot or the driver or whatever) realize the
cartridge is still in the drive which it is going to use for next
backup (it is written in the database) and therefore unload it
before proceeding with the backup itself?
It doesn't work in this way in V2.7. I wonder what happens with
V2.8A...
Thanks
Iolanda
| |||||
| 2238.3 | COOKIE::MCCLELLAND | Marty, SLS/MDMS Engineering | Fri Apr 25 1997 08:26 | 13 | |
> - Will SLS (or the robot or the driver or whatever) realize the
> cartridge is still in the drive which it is going to use for next
> backup (it is written in the database) and therefore unload it
> before proceeding with the backup itself?
Since the previous backup to the volume was terminated, the volume ends
with a partial saveset, so another saveset cannot be appended. Assuming
AUTOSEL=1, SLS will unload the current volume, load the least recently
freed volume from the jukebox, and use it for this backup.
Marty
| |||||