This is true...but there is something else to consider.
If you are using IBM LTO Gen 1 drives, there was a bad level of microcode that
could write a EOT mark at the BOT. A symptom of this is the inability to
read the
tape label. If this is an offsite copy, you can reproduce it with your
onsite
I have a question regarding reclamation of tapes in a collocated pool.
In out non-collocated pools I simply set a threshold and let it go.
However, in the collocated pools you have many more partially filled
tapes that will be appended to later, and makes no sense to reclaim.
But there are also
You answered it...I wasn't aware that reclamation treated a half empty
(never full) tape different from a half empty (once full) tape.
Sounds like I should have RTFM a little more. Sorry.
Thanks!
At 03:06 PM 2/4/2004, you wrote:
The reclaim only reclaims tapes that have a specific % expired. It
I saw this for the first time just last week. It was also for a storage
agent backup. I tracked the problem to a name mismatch in the
server definition for that storage agent...since I corrected the type
I have been problem free!
leonard
At 03:26 PM 1/27/2004, you wrote:
TSM Server 5.2.2 (AIX
The latest OS X client scheduler seems to work...mostly...not as clean
as I'd like it.
At 11:11 AM 1/20/2004, you wrote:
Yeah, no prob, I ran into the nfs not being ALL-LOCAL a while back.
Our NFS mounts are OS X workspaces, and since the OS X tsm client
scheduler DOES NOT WORK, and the OS X tsm
Our experience with IBM's LTO solution has been very poor.
Latest in a long string of problems was the determination that the latest
drive microcode (gen 1) 36U7 (as well as several other versions) will, under
certain circumstances after a write error, rewind the tape and write a EOT
at BOT.
We were at 5.2.1.2 briefly...no problems during that time. Currently at
5.2.1.3 and seem to have a problem labeling ACSLS tapes...still early
in the investigation though.
DB change from 5.1.6.1 to 5.2.
At 10:01 AM 11/19/2003, you wrote:
Then a week or 2 after that I will be upgrading TSM. Is
Could this be affecting you??
The problem that you could be facing is the following:
APAR= IC36543 SER=IN INCORROUT
TSM CLIENT NQR (NO QUERY RESTORE) CAN TERMINATE IMPROPERLY
IF THE RESTORE IS INTERRUPTED BY A DISK FULL/QUOTA CONDITION
.
If a TSM client no query
Our experience has been with 9840 (A's) and LTO gen 1 drives. The 9840s have
been rock solid for years, while the LTO has had more failures in the past
14 months
or so than all of our STK drives over the past 8 or so years.
The LTOs started off rough, but I must admit that lately things have
Query your drives...are they online? If so then
query your paths to those drives. If you find the
path to the library or paths to the drives offline,
vary them on and try things again.
-Original Message-
From: Sebastien Bigand [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Date: Mon, 21 Jul
According to a memo I received from IBM, the LTO
drives do NOT require periodic cleaning.
The only time ours got cleaned is when we noticed
that auto cleaning was not occuring, and before we
got the memo.
Now, we have had a few tapes stuck in drives for
various reasons, and many unexplained
yes it does...i can dig it up and send it to you if
you'd like. :)
-Original Message-
From: Richard Sims [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Date: Tue, 24 Jun 2003 09:06:50 -0400
Subject: Re: Interesting LTO fault's symptom
According to a memo I received from IBM, the LTO
drives do
Just wanted to thank everyone for opinions on sizing
a new TSM server. I appreciate all the information
and suggestions.
Thanks
leonard
You can respond direct to me instead of the list
if you wish. Thanks!
We are considering an IBM P650, either 2 or 4-way
system as our replacement TSM server. 4 to 8 GBs
of memory and around 1 terabyte of disk (FastT700?)
for database, log and disk pools.
Our current config is a Sun E4500 with
14 matches
Mail list logo
