Table of Contents
Advertisement
Example 5-2 shows the second phase—extending the database.
Example 5-2 Extending the database
tsm: LOCHNESS_SERVER1>
Available Assigned
Space Capacity Extension Reduction
(MB)
--------- -------- --------- --------- -------
2,024
tsm: LOCHNESS_SERVER1>
ANR2248I Database assigned capacity has been extended.
tsm: LOCHNESS_SERVER1>
Available Assigned
Space Capacity Extension Reduction
(MB)
--------- -------- --------- --------- ------- ------- ----- ---- ----
2,024
After the assigned capacity is extended, the output from query db changes
accordingly. As we have extended the database to use all the defined database
volumes, the maximum extension column shows 0 bytes.
5.2 Recovery log
The recovery log performs two functions, depending on its
the recovery log stores database transactions that have not yet been committed
to the database. Any operation that updates the Tivoli Storage Manager
database is first written to the recovery log. Secondly, if the recovery log mode is
roll forward
committed. Caching of transactions allows you to replay the transactions at a
later point in time to enhance database recovery, if needed. See 5.3, "Setting the
log mode" on page 196, for more information.
As with its database, Tivoli Storage Manager considers the recovery log as one
logical object, made up of a number of physical files, or
192
IBM Tivoli Storage Manager Implementation Guide
query db
Maximum
Maximum
(MB)
(MB)
(MB) (bytes)
1,000
1,024
extend db 1024
query db
Maximum
Maximum
(MB)
(MB)
(MB) (bytes)
2,024
0
2,016
, the transaction is cached in the recovery log after it has been
Page
Total
Size
Usable Pages Util
Pages
------ ----- ---- ----
996
4,096 256,000 1,202
Page
Total
Size
Usable Pages Util
Pages
4,096 518,144 1,506
mode
volumes
Used
Pct Max.
Pct
Util
0.5
0.5
Used
Pct Max.
Pct
Util
0.3
0.3
setting. Firstly,
.
Advertisement
Table of Contents
