>We are running tsm-server ver 3.7.20 on aix 4.3.2 with about 400 gb per day
>backup.
>Our adsm db-size is close to 100 gb and growing daily.
>Almost each day log is overflowing with 100%, all backups fails, and server
>recovers & continues
>We are already using max 5.4 gb of log and can not increase any more on log
>volume.
We don't know the nature of your clients, but, in general, your are suffering
from congestion...
I would begin by examining how the backups are being done: Make sure your
clients are doing true Incremental backups (that is, that they are not
sending everything every day); that your Copy Pool mode is not ABSolute; etc.
Next see if the backup schedule is reasonably spread out over time so that
they are not all hitting the server at once. (The Servergraph product may
help: see www.servergraph.com.) If the backups are via schedule, check that
your Set RANDomize server spec is appropriate.
If the backups are legitimately configured and distributed over time, see
about possibly having them occur in pieces, as via Virtualmountpoint or
other techniques.
Check your server db "Cache Hit Pct" and boost BUFPoolsize size if under
like 98%. Make sure your server system has enough memory so that TSM db
operations occur in real memory, not virtual. Assure that your server
system is not burdened with other, unrelated processes during these times.
Assure that no other server housekeeping processes are running during
these times, particularly expiration.
Have your TSM db on its own disks, if possible, to speed its operations.
All that good tuning stuff.
Richard Sims, BU
