IBM E16RMLL-I - Tivoli Storage Manager, Implementation Manual

Page: 240 / 828

210
IBM Tivoli Storage Manager Implementation Guide
We see that there is enough space to reduce the log by 8 MB, the size of the
default recovery log volume. To delete the volume, use the
delete logvol
command, as shown in Example 5-17.
Example 5-17 Deleting a recovery log volume
tsm: ATLANTIC>
q logvol
Volume Name Copy Volume Name Copy Volume Name Copy
(Copy 1) Status (Copy 2) Status (Copy 3) Status
---------------- ------ ---------------- ------ --------------- ------
/usr/tivoli/tsm- Sync'd Undef- Undef-
/server/bin/lo- ined ined
g.dsm
/tsm/log/primar- Sync'd /tsm/log/mirror- Sync'd Undef-
y/logp_01.dsm /logm_01.dsm ined
tsm: ATLANTIC>
delete logvol /usr/tivoli/tsm/server/bin/log.dsm
ANR2264I Delete process initiated for recovery log volume /usr/tivoli/tsm/
server/bin/log.dsm (process id 12).
ANS8003I Process number 12 started.
tsm: ATLANTIC>
q logvol
Volume Name Copy Volume Name Copy Volume Name Copy
(Copy 1) Status (Copy 2) Status (Copy 3) Status
---------------- ------ ---------------- ------ --------------- ------
/tsm/log/primar- Sync'd /tsm/log/mirror- Sync'd Undef-
y/logp_01.dsm /logm_01.dsm ined
Even though the volume no longer appears in the
query logvol
output, the file
itself is not deleted by the process. You should now physically remove the file
from the file system.
5.8 Database backup
The Tivoli Storage Manager database is the heart of Tivoli Storage Manager—it
tracks the location of all your backed-up objects. Without it, your backups are just
a bunch of ones and zeros. It is vitally important to run regular Tivoli Storage
Manager database backups.
If the database becomes damaged or lost, you can restore it by running the Tivoli
Storage Manager server in database restore mode: DSMSERV RESTORE DB.
You will require the latest database backup media.