nk I would stay with something earlier
than 4.2.2 - there are some serious locking issues that some corruption in
our DB has made almost unbearable for us.
YMMV, of course.
-Original Message-
From: Shamim, Rizwan (London) [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 20, 2002 7:00 AM
To: [EMAI
I've seen something similar to this.
We sometimes have clients that want to run a "convert archive" and most of
the time it's not a problem. We have had instances where the convert has
run for 3 days without problems. We had one case where the convert archive
and expiration clashed and the db
Greetings,
Our current environment:
> TSM on Solaris: TSM version 4.2.3.1
SQL TDP Client:TDP version 2.2.0.01
> TSM BA Client:TSM version 4.2.1.22
>
We recieved the following TDP errorrs in our client logs.
> I'd be grateful if someone could shed some ligh on this:
Thanks Del.
Problem with MAXMUMMP. Fixed now.
However I now get the following:
24-02-2003 13:23:50 ACO5456W The backup is corrupt and is not fully
restorable.
24-02-2003 13:23:50 Processing will continue.
24-02-2003 13:23:50 ACO0302E A failure occured on stripe number (3), rc =
428
24-02-2003
Thanks for your help Del.
We have tested with 4 stripes and we restored at around 28-31MB/sec
previously from tape (3590E XL).
I'll call IBM.
Thanks again.
Rizwan
Rizwan Shamim
Central Backup Service (CBS)
Merrill Lynch Europe PLC
Tel: 020 7
