IBM Tivoli Storage Manager, Version 7.1

Modify DB2 lock list management

The lock list storage of DB2® that is automatically managed can become insufficient. If you deduplicate data that includes large files or large numbers of files concurrently, the data deduplication can cause insufficient storage. When the lock list storage is insufficient, backup failures, data management process failures, or server outages can occur.

File sizes greater than 500 GB that are processed by data deduplication are most likely to cause storage to become insufficient. However, if many backups use client-side data deduplication, this problem can also occur with smaller-sized files.

The following activities can use more lock list storage:

Client backups that use client-side data deduplication
Data movement within a deduplicated storage pool that uses the reclamation and MOVE DATA commands
Data movement out of a deduplicated storage pool that uses the migration and MOVE DATA commands

See Technote 1430874, Managing the DB2 LOCKLIST Configuration Parameter with Tivoli Storage Manager, for an explanation about how to estimate the peak volume of deduplication transactions that are processed. This document also contains information about the corresponding lock list requirements for managing the volume and information about how to change the DB2 limit, if necessary.

Tip: When you estimate the lock list storage requirements, follow the information described in the technote to manage storage for loads that are much larger than expected.

Feedback