Table of Contents
Advertisement
Figure 15-1 on page 497 shows the side effects of placing multiple storage pool
volumes on a single disk. The increased seek activity can degrade performance.
Partition or logical volume
TSM volume
Used space
Space being written to in current transactions
Figure 15-1 Tivoli Storage Manager volume definitions
It is also preferable to send backups of large amounts of data, such as entire
client databases, directly to tape instead of buffering in a disk storage pool. This
allows the client to take advantage of the high streaming performance of most
advanced tape drives when writing large files and avoids extra data movement
from the migration process, which will likely be immediately triggered.
Backups of file servers and workstations should be directed to a disk storage
pool to avoid tape mount delays. Also, a disk storage pool supports more
multiple sessions than the available tape devices.
15.2.3 Versioning
Keeping a lot of different backup versions of files makes the Tivoli Storage
Manager server database larger. A larger server database will not be accessed
as fast as a smaller one and requires more time for backup and inventory expiry
operations. The planning process is important in order to make sure you keep
only as many versions as really needed.
1 TSM volume per physical disk
2 TSM volumes per physical disk
Chapter 15. Performance considerations
Volumes shown assuming all
data was previously migrated.
Increased seek activity can
degrade performance.
Use only one volume per
physical disk.
497
Advertisement
Table of Contents
