IBM E16RMLL-I - Tivoli Storage Manager, Implementation Manual

Page: 229 / 828

Chapter 5. Database and recovery log
199
Process Process Description Status
Number
--------
-------------------- ----------------------------------------
76 Database Backup Full backup: 0 pages of 1500 backed up.
Current output volume: LTO888
tsm: LOCHNESS_SERVER1>
query dbbackuptrigger
Full Incremental Log Full Incrementals Minimum Minimum
Device Device Percentage Between Backup Log
Class Class Fulls Interval Percentage
(minutes) Freed
--------- ----------- ---------- ------------ --------- ----------
LTO2-DC LTO2-DC 75 6 0 0
Notice that once we defined the database backup trigger, a database backup
was immediately started. To verify that the
define dbbackuptrigger
command was
successful, issue the
query dbbackuptrigger
command.
5.5 Setting the expansion trigger
Tivoli Storage Manager lets you fully automate the process of increasing the
database and recovery log, whenever necessary. For example, suppose you
have a 4 GB database and a 2 GB recovery log. You want to increase the size of
the database by 25% when it is 85% utilized, but not to more than 8 GB. You also
want to increase the recovery log by 30% when it is 75% utilized, but not to more
than 4 GB.
Tip: The combination of the dbbackuptrigger and rollforward mode may
require some tuning attention. As with most automated processes, regular
operational monitoring is required.
Note: Setting a space trigger does not mean that the percentage used in the
database and recovery log will always be less than the value specified with the
FULLPCT parameter. Tivoli Storage Manager checks utilization when
database and recovery log activity results in a
commit
. Deleting database
volumes and reducing the database does not cause the trigger to activate.
Therefore, the utilization percentage can exceed the set value before new
volumes are online.