OK, here's my good news/bad news for the informal poll:
Production 6.1 server:
New TSM 6.1.2 installation with a wompin powerful Win2K3 box, lots of
external SAN disk
Running 76 schedules of daily incrementals:
Most clients are relatively small Win2K3 servers, all TSM client 6.1
A few Linux client
>> On Fri, 2 Oct 2009 09:49:52 -0600, Kelly Lipp said:
> That last paragraph made my head hurt! I had the "opportunity" to
> take a database class in college. Didn't want to know it then,
> don't want to know it now.
There was a "Know-nothing" political party, once.. :P
> I'll echo Rick's co
estart the
db2 database as well.
> -Ursprüngliche Nachricht-
> Von: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] Im
> Auftrag von Kelly Lipp
> Gesendet: Freitag, 2. Oktober 2009 17:50
> An: ADSM-L@VM.MARIST.EDU
> Betreff: Re: AW: TSM 6.1 and the
solves your data backup challenges.
Once and for all.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Richard Rhodes
Sent: Friday, October 02, 2009 9:26 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] AW: TSM 6.1 and the ever expanding DB
I&#x
Dist Stor cc
Manager"
Re: AW: TSM 6.1 and the ever
is a problem and hope to reduce the requirements,
in future (V6.2?) releases. They still have numerous DB2/TSM interaction
bugs to squash, first!
From:
Stefan Holzwarth
To:
ADSM-L@VM.MARIST.EDU
Date:
10/02/2009 10:16 AM
Subject:
[ADSM-L] AW: TSM 6.1 and the ever expanding DB
Sent by:
"
We want also to go into production with 6.1.2. All setup is finished.
But with about 20 nodes (all export/import) we continously have trouble with
full active log and full archivelog.
Our active log size is 16Gbyte and it seems to be enough for this small setup.
But sometimes the log usage explo
