, 2001 7:58 AM
To: [EMAIL PROTECTED]
Subject:Re: LTO restore performance - seek problem?
Hello,
you need the PGA3 microcode which should be
available early next week, date subject to change.
This is the microcode that should address
On Tue, 22 May 2001, Jeff Bach wrote:
Did the microcode level PGA3 address the LTO performance issues?
Apparently not. I had a space reclamation run all day yesterday, and
today a move data process that's moved about 4 gigs, tape to tape, in only
7 hours!!! The 1550 (aka PGA3) microcode does
I've just had the firmware upgraded to 1550 (don't know the patchname)
from 12U7 and, at this stage, it doesn't look like it has fixed the read
performance problem
I audited 2 tapes with ~25% utilization in a filling state (I don't expect
many gaps in data). One took 3 hours the other 5.
During
Rejean,
Have you heard a release date for the PGA3 microcode? The 0CE1 and 12U7
levels are killing me on tape reclamations and stgpool backups...
Is there a site where i can get the 0BN1 code and downgrade the drives?
I'm not sure if downgrading is supported/recommended but i'm getting
Hello all,
I applied OCE1 microcode to 2 3583 drives recently, and i think
performance is suffering now! Backup seems fine, but tape-to-tape
operations is taking forever... perhaps restore is suffering as well, i
have not tried any large restores.
I'm seeing the same behavior Rejean describes
I applied OCE1 microcode to 2 3583 drives recently, and i think
performance is suffering now! Backup seems fine, but tape-to-tape
operations is taking forever...
The early period in another IBM tape technology... We went through
a lot of the same pain in the early days of 3590 and 3570. It's
] To: [EMAIL PROTECTED]
EDU cc:
Sent by: Subject: Re: LTO restore performance -
seek problem?
ADSM: Dist
Stor Manager
[EMAIL PROTECTED]
IST.EDU
Something else you could check.
We have been having the same kind of symptom on our 3590 B1A
drives. In conjuction with the CE, we opened the covers on the
drive and physically watched what was happening. To our surprise,
we saw that every so often the drive would decide that something
was
PROTECTED]
/IBM@IBMCA cc:
Sent by: Subject: Re: LTO restore performance -
seek problem?
ADSM: Dist
Stor Manager
[EMAIL PROTECTED]
IST.EDU
Hi!
Your problem sounds familiar to me.
We've similar problems running HSM (or now: Tivoli Space Manager) with
a LTO 3583. (Ok, it is not the best way to use a LTO Library with
HSM, but that was not my decision). For a recall of 2 GBs we need half a
day.
But: a normal restore of a client is as
John,
This problem is very interesting to me as we are thinking of throwing away our
17 ATL libraries running Legato's NetWorker 6.0.1 in favor of 2 LTO 3584's
running
Tivoli Storage Manager (we will actually use a Sun E420). I thought colocation
was suppose to speed up recoveries, it sounds as
PROTECTED]
Subject:Re: LTO restore performance - seek problem?
John,
This problem is very interesting to me as we are thinking of throwing away
our
17 ATL libraries running Legato's NetWorker 6.0.1 in favor of 2 LTO 3584's
running
Tivoli Storage Manager (we will actually use a Sun E420). I
Greetings,
I have seen many posts on adsm.org about LTO, but none that
addresses the problem I am seeing. Backup speed seems to be fine, at
least as far as I can tell. But when I do a restore, I see a strange
behavior. The restore seems to happen in bursts, where the restore
pulls back
: Thursday, May 03, 2001 6:40 AM
To: [EMAIL PROTECTED]
Subject:LTO restore performance - seek problem?
Greetings,
I have seen many posts on adsm.org about LTO, but none that
addresses the problem I am seeing. Backup speed seems to be fine, at
least as far as I can tell. But when I do
jdschn@attglo To: [EMAIL PROTECTED]
bal.net cc:
Sent by: Subject: LTO restore performance - seek
problem?
ADSM: Dist
Stor Manager
[EMAIL PROTECTED
-Original Message-
From: John Schneider [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 03, 2001 8:40 AM
To: [EMAIL PROTECTED]
Subject:LTO restore performance - seek problem?
Greetings,
I have seen many posts on adsm.org about LTO, but none that
addresses the problem
restore performance - seek problem?
Greetings,
I have seen many posts on adsm.org about LTO, but none that
addresses the problem I am seeing. Backup speed seems to be fine, at
least as far as I can tell. But when I do a restore, I see a strange
behavior. The restore seems to happen in bursts
17 matches
Mail list logo
