IBM E16RMLL-I - Tivoli Storage Manager, Implementation Manual, Page: 78 / 828

48
IBM Tivoli Storage Manager Implementation Guide
on their own disk devices and controller separate from the database and the
recovery log, if possible.
Complete Table 2-11 with the primary storage pool file names and volume names
for your primary storage pool. We are considering backup and archive
requirements only, which was 226 + 28 GB = a total of 254 GB. If using 20 GB
size for disk storage pool volumes, we would need at least 13 volumes.
Table 2-11 Primary storage pool worksheet
2.8.12 Device configuration table and volume history file
The device configuration table and the volume history table also require disk
space, but they are typically very small. The device configuration table contains
entries for defined device classes and definitions for drives and libraries. Every
volume that is used by Tivoli Storage Manager is tracked in the volume history
database, including the volume identifier for the database backups. The volume
history information is periodically copied out to a volume history file that you can
specify with the VOLUMEHISTORY option in the dsmserv.opt file.
We recommend defining at least two copies of both the device configuration
table and the volume history file, in case one becomes unusable due to a
hardware or software failure. We also highly recommend that you back up the
device configuration file and the volume history file every time you back up your
Tivoli Storage Manager database. These files will be invaluable in the event that
you need to recover your Tivoli Storage Manager server.
File name Size (GB)
/tsm/stgpool/file01 20
/tsm/stgpool/file02 20
/tsm/stgpool/file03 20
/tsm/stgpool/file04 20
...
/tsm/stgpool/file13 20
Total 254