If you have a TSM database spread across mutliple database volumes on disk, be very careful on how you use them. It is best to assign multiple database volumes on different disks, all equal in size. This way, TSM is able to use the
performance of several disks equally.
Also, take a look at the assigned capacity of the TSM database. It might well be that not the full capacity of the database is assigned to TSM; this way, some database volumes are more heavily used than other. A good command to check if the database volumes are equally used is "q dbspace":
q dbspaceThese commands can be used to find out, how your database capacity is assigned. If it isn't fully assigned, then do it now.
q db f=d
Check the output of the TSM commands with the location of your database volumes on the operating system, to see if the database volumes are equally spread across multiple disks. The AIX commands iostat and vmstat will give you a good idea if your disks are used equally.
If you found this useful, here's more on the same topic(s) in our blog:
- Creating an image_data resource without preserving mirrors for use with NIM
- Show configuration of a TSM / IBM Spectrum Protect server
- Tail TSM / IBM Spectrum Protect console log
- What did the TSM admins do?
- Spectrum Protect / TSM: Display deduplicaton bytes pending removal
UNIX Health Check delivers software to scan Linux and AIX systems for potential issues. Run our software on your system, and receive a report in just a few minutes. UNIX Health Check is an automated check list. It will report on perfomance, capacity, stability and security issues. It will alert on configurations that can be improved per best practices, or items that should be improved per audit guidelines. A report will be generated in the format you wish, and the report includes the issues discovered and information on how to solve the issues as well.
Interested in learning more?
Interested in learning more?
