I was told by a Tivoli Engineer at one time that you shouldn't let them
grow much over 50 gb.  Primarily, because of the reason you state here
about having the capability to restore.  In a disaster, you need to take
into consideration how much time it is going to take you to restore that
database just to get the TSM server up and running.  That time would have
to be added to the SLA requirements you might have in place to get any
application servers back up and running.





                    Paul Zarnowski
                    <vkm AT CORNELLC.CIT DOT CO       To:     ADSM-L AT 
VM.MARIST DOT EDU
                    RNELL.EDU>                 cc:
                    Sent by: "ADSM: Dist       Subject:     Re: TSM database 
maximum recommended
                    Stor Manager"               size
                    <ADSM-L AT VM.MARIST DOT ED
                    U>


                    04/03/2002 06:41 PM
                    Please respond to
                    "ADSM: Dist Stor
                    Manager"






At 12:08 PM 4/3/2002 -0500, Scott McCambly wrote:
>How many sites are running with databases this large or larger? On what
>hardware?

Our DB is now 116GB assigned (92% full).
Hardware is RS6000/M80, 2GB RAM, SSA disks (db is mirrored by TSM)
As others have said, "it depends".  If your requirement is to be able to
restore a database quickly, then your max size will be smaller.