ADSM-L

Re: 3583 library problems

2004-09-28 09:14:19
Subject: Re: 3583 library problems
From: Moses Show <Moses.Show AT STPAUL DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 28 Sep 2004 14:14:20 +0100
TSM servers sees the drive as being defined and online along with the
library.
Can define a path for the library o.k. without any problems regarding it
staying online.
However as for the paths to the drives these have been  deleted and then
redefined and set to be online.
This is where the  problem arises as from this point the paths to the
drives stay active for maybe 30 seconds before going offline and setting
the drives themselves into a state of polling. This never used to happen
before and can't understand the inability to keep the paths online and
stable. Does anyone know why this kind of behaviour is exhibited ?



"CORP Rick Willmore" <RWillmore AT RSAC DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
27/09/2004 18:42
Please respond to
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To
ADSM-L AT VM.MARIST DOT EDU
cc

Subject
Re: 3583 library problems






I use a scalar100 which is a 3583.  I dont believe this is a library issue
though .. rather a drive mapping issue.  Sounds like tsm isnt talking to
the drives.. ie.. sure you have the elements correct?  Has it ever worked?

R.

-----Original Message-----
From: Moses Show [mailto:Moses.Show AT STPAUL DOT COM]
Sent: Monday, September 27, 2004 10:37 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: 3583 library problems


Hi people
        Am running TSM server 5.2.20 using IBM 3583 LTO library as the
backup device. However seem to have a problem with the drives. The paths
to each of the drives are varied on, but it seems that every time I update
the drives to a status of online, at least two of the drives go into a
status of polling. Anytime I attempt to do an audit library to check the
media in there the paths for the drives in the library seem to get varied
off. Has anybody experienced this before and if so how did they get around
this problem ?
==============================================================================
This communication, together with any attachments hereto or links
contained herein, is for the sole use of the intended recipient(s) and may
contain information that is confidential or legally protected. If you are
not the intended recipient, you are hereby notified that any review,
disclosure, copying, dissemination, distribution or use of this
communication is STRICTLY PROHIBITED.  If you have received this
communication in error, please notify the sender immediately by return
e-mail message and delete the original and all copies of the
communication, along with any attachments hereto or links herein, from
your system.

==============================================================================
The St. Paul Travelers e-mail system made this annotation on 09/27/2004,
01:38:33 PM.




==============================================================================
This communication, together with any attachments hereto or links contained 
herein, is for the sole use of the intended recipient(s) and may contain 
information that is confidential or legally protected. If you are not the 
intended recipient, you are hereby notified that any review, disclosure, 
copying, dissemination, distribution or use of this communication is STRICTLY 
PROHIBITED.  If you have received this communication in error, please notify 
the sender immediately by return e-mail message and delete the original and all 
copies of the communication, along with any attachments hereto or links herein, 
from your system.

==============================================================================
The St. Paul Travelers e-mail system made this annotation on 09/28/2004, 
09:15:55 AM.

<Prev in Thread] Current Thread [Next in Thread>