Hi Luke

You can read-up on database sizing in the Admin Guide!

Clarence Beukes
 Advisory IT Specialist - Tivoli Certified Consultant
 Geomar SSO Mid Range and Application Support Discipline
 Location:  IBM Park Sandton, IA2G
 Tel: +27 (0) 11 302-6622   Cell: +27 (0) 82 573 5665
 E-mail: clarence AT za.ibm DOT com


Luke Dahl <ldahl AT JPL.NASA DOT GOV>@VM.MARIST.EDU> on 07/16/2001 06:01:29 PM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

Sent by:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To:   ADSM-L AT VM.MARIST DOT EDU
cc:
Subject:  Database Size Issues



Hello Again,
    Is there a way to identify how the addition of a node affects the
TSM database size?  I can capture the number of files and the amount of
data that each additional node adds to the TSM server, but what I'm
really looking for is a way to separate how a particular node affects
the database size.  Even better would be to identify how much a
particular type of workstation affects the TSM database.
    For instance, if we were to add 100 typical Win2K workstations (if
there is such a thing as typical) we're wondering how much that would
affect the TSM database?  Does anyone have any information on this or
have any idea how to find out without starting with an empty database
and adding x number of nodes?  Any information would be extremely
helpful!  Thank you all!

Luke Dahl
NASA-Jet Propulsion Laboratory
818-354-7117