I think it's hard to guess the final size of your TSM database, but it's
easy to expand it.
So I usually start with 2-4 GB and watch it / have a script watch it, and
add volumes as needed.
There is a feature that will grow the database for you, and might work OK on
MVS.
It's the DEFINE SPACETRIGGER command.
Unfortunately for those of us without mainframe-class DASD, DEFINE
SPACETRIGGER doesn't seem to handle mirroring very well. If you have
database mirror volumes defined, it will create new mirrors for any new DB
volumes it adds - that's good. But it puts them in the same directory,
i.e., on the same physical disk. That's bad. So I do it by hand.
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Coles, Peter
Sent: Tuesday, August 22, 2000 4:20 PM
To: [EMAIL PROTECTED]
Subject: Database sizing question
Sensitivity: Private
I am in the process of moving from ADSM on an AIX system to TSM on OS/390 (I
know, I know). In calculating the database size in accordance with TSM
Implementation Guide (Redbook) for 40 servers with approximately 3.4 million
files with a 60 day retention requirement I get a db size of ~128 GB. This
seems a bit much for me. Currently on the AIX side my db size is 3.7 GB.
Any ideas....
Peter Coles
Pacific Gas and Electric Company
[EMAIL PROTECTED]
