ADSM-L

Tape mount failures result in schedule failure

2004-02-13 14:06:09
Subject: Tape mount failures result in schedule failure
From: "Zhu, David" <David.Zhu AT KRAFT DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 13 Feb 2004 13:48:20 -0500
Hi,

The environment is TSM/StorageAgent/Win2000 5.2.2, IBM 3584 LTO library.


Activity log indicate that session 237 failed to mount a tape volume
293AGHL2 in drive mt3.0.0.3, showing repeated
ANR8779E (Session: 237, Origin: SP02B_STA)
 Unable to open drive mt3.0.0.3, error number=2. (SESSION: 237)

so after 5 minutes got
ANR1401W (Session: 237, Origin: SP02B_STA)
 Mount request denied for volume 293AGHL2 - mount failed. (SESSION: 237)

It then mounted the volume successfully in drive mt6.0.0.3.

3 minutes after that, session 255 started to mount 298AGHL2 in mt6.0.0.3,
resulting in repeated
ANR8779E (Session: 255, Origin: SP18A_STA)
 Unable to open drive mt6.0.0.3, error number=170. (SESSION: 255)

It then mounted the volume successfully in drive mt5.0.0.3.

Is this behavior normal for tape libraries?  It is an indication of some
problem with the drives?  Where can I find the meaning of the error number 2
and 170?

Both tape mounts were requests by scheduled backup and it seems to me as a
result of the tape mount failures, the scheduled got a return code 12 and
showed up as failed.  Is this assessment correct?

Thanks in advance to anyone who can shed some light on this.

Regards,
David Zhu
TSM Support
david.zhu AT kraft DOT com
Tel: 416-503-7853