Actually there isn't a 50GB limitation so to speak.  Basically the
limitation comes from the fact that many TSM customers degregate
performance as they increase the size of their TSM database.  I have
seen issues with DB growing past 80GB, but then again I have other large
TSM customers whose DB is at 160GB (p690 LPAR) with no problems
whatsoever.  It is very "platform dependent."  The greater the
capabilities of the host operating system the greater scalability of a
single TSM instance.

As far as your original question goes about maintaining more versions.
I wouldn't anticipate any problems other than a minor slow down in
performance from a 13GB DB to a 20-30GB one.


--
Joshua S. Bassi
Tivoli Certified Consultant -ADSM/TSM
eServer Systems Expert -pSeries HACMP
IBM Certified - AIX 4/5L, SAN, Shark
Cell (831) 595-3962

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Coats, Jack
Sent: Wednesday, May 14, 2003 3:40 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: 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