Use collocation to improve Tivoli® Storage Manager performance and maintain optimal data organization.
When you use collocation, the performance of restore operations for large amounts of data can be significantly improved because fewer mounts are required to locate the necessary files. Generation of backup sets and export operations are also faster. In addition, collocation decreases the chance for media contention with other clients. While performance is improved by using collocation, enabling it increases both the amount of server time that is needed to collocate files for storing and the number of volumes that are required for data storage.
Type | Volume usage | Volume mounts | Restore time |
---|---|---|---|
No collocation | Low volume usage | Few number of mounts for migration and reclamation | Longest restore time |
Collocated by node | High volume usage | High number of mounts for migration and reclamation | Good restore time, but not optimized for multi-session restore |
Collocated by group | Low volume usage | Few mounts for migration and reclamation | Good restore time |
Collocated by file space | High volume usage | High number of mounts for migration and reclamation | Good restore time, but not optimized for multi-session restore |
To enable collocation, use the COLLOCATE parameter on the DEFINE STGPOOL command when you are defining a primary sequential-access, copy, or active-data storage pool. You can use the UPDATE STGPOOL command to enable collocation for an existing storage pool.