Joyce,

        Any activity within TSM dealing with client data will create one or
more database entries (just look at the number of tables containing file
entries - 8 of them). This includes the obvious like backups, archives, and
pool copies.  The biggest bang for reducing databases is to cut the number
of client files kept - use the VERE, VERD, RETE, and RETO controls on the
copy groups to control versioning and retention periods.  Also useful in
controlling database utilization is the expiration process; it just doesn't
pay off as big as copy controls do (after an initial pass following
reduction changes).  Run expiration as frequently as you can afford it; it
is a long running process against large databases.

Also part of the database is the activity log.  The longer you set the
activity log retention the more space you will need.  Consider reducing your
history retention period and look into suppressing certain types of messages
(mount requests, client activities, informationals, etc.) based on your
needs.

        Gary L. Ison
        Governor's Office for Technology
        101 Cold Harbor Drive
        Frankfort, Ky.   40601
        Phone:  (502) 564-8724
            Fax:  (502) 564-6856
E-mail: Gary.Ison AT mail.state.ky DOT us <mailto:Gary.Ison AT mail.state.ky 
DOT us>