do not worry, let it grow. There are soft limits only (performance,
backup/restore time..)
You can go back to 8 vesions later quite easy.

Watch overall performance, once it degrades under whatever you decide, think
abeout countermeasures.

An important point is downtime of TSM server 
you can afford after crash or after another sort of problems 
you could once have with TSM server/database (independent of its size).

To check if you comply with this your requirement, 
check right now how long "dsmc auditdb" takes 
(or "dsmc audit db" - I am not quite sure)
and repeat the test once your DB has grown.

best regards

Juraj Salak


-----Ursprüngliche Nachricht-----
Von: Coats, Jack [mailto:Jack.Coats AT BANKSTERLING DOT COM]
Gesendet: Donnerstag, 15. Mai 2003 00:40
An: ADSM-L AT VM.MARIST DOT EDU
Betreff: architectural limit on the TSM database and performance?


Some folks told me a couple of years ago that TSM has an architectural
limit of about 50G for the TSM database.  Currently we have about 13G in
ours and we would like to retain more versions.  But I don't want to
destroy my little Wintel TSM server in pushing the limits.  (It is a Dual P4
with 833 processors, 1G Ram, 6 LTO1 drives in a 3583, and a 200G disk pool)

We currently keep 8 versions for up to 60 days, and would like to get to 16
versions in the same 60 days.  Probably wouldn't double the database,
but I don't want to come to near any architectural limits.
-- TIA ... Jack