Logical storage pools and storage volumes are the principal
components in the Tivoli® Storage
Manager model
of data storage. By manipulating the properties of these objects,
you can optimize the use of storage devices.
Using file system cache for storage pools
By default, the Tivoli Storage
Manager server reads
and writes storage pool data with non-buffered I/O, which bypasses
the file system cache. Using file system cache can be beneficial in
certain situations but it is not a best practice.
File system fragmentation for storage pools on disk
Fragmentation problems can occur when you are writing to
scratch volumes in multiple storage pools simultaneously, in one file
system. Because unfragmented volumes generally perform better than
fragmented volumes, use the DEFINE VOLUME command
to preallocate volumes for sequential disk storage pools (DEVTYPE is FILE).
Optimal number and size of volumes for storage pools that use disk
When you calculate the size and number of volumes for storage
pools that are defined with a FILE or DISK device
class, consider the type of storage, how much storage is available,
and other variables.