TSM DB Near Full - Suggestions Wanted. Thanks.

[coujam1]

Any suggestions on this:

tsm: SERVER1>q db
Available Assigned Maximum Maximum Page Total
Space Capacity Extension Reduction Size Usable
(MB) (MB) (MB) (MB) (bytes) Pages
--------- -------- --------- --------- ------- ---------
34,000 34,000 0 0 4,096 8,704,000
tsm: SERVER1>q db f=d
Session established with server SERVER1: AIX-RS/6000
Server Version 5, Release 5, Level 0.0
Server date/time: 06/04/19 11:28:49 Last access: 06/04/19 08:16:26

Available Space (MB): 34,000
Assigned Capacity (MB): 34,000
Maximum Extension (MB): 0
Maximum Reduction (MB): 0
Page Size (bytes): 4,096
Total Usable Pages: 8,704,000
Used Pages: 8,694,867
Pct Util: 99.9
Max. Pct Util: 100.0
Physical Volumes: 17
Buffer Pool Pages: 8,192
Total Buffer Requests: 705,735,933
Cache Hit Pct.: 98.38
Cache Wait Pct.: 0.00
Backup in Progress?: No
Type of Backup In Progress:
Incrementals Since Last Full: 0
Changed Since Last Backup (MB): 307.65
Percentage Changed: 0.91
Last Complete Backup Date/Time: 06/03/19 13:02:52
Estimate of Recoverable Space (MB): 3,243

 

[LED888]

Several things to think about:

1. Define more DB volumes to increase capacity. Are there enough PP's on the LV.
2. Increase the PP's on the LV, define more DB volumes.
3. Review the retention settings. Are we keeping too many files and/or are we keeping the files too long? What is the business requirements?
4. Do we have TSM Clients that are backing up EVERYTHING!
5. Do we have old TSM Clients that need to be removed from the TSM Server?
6. Are we adding new TSM Clients? In the future may need another TSM Server for load balancing.

Good Luck,
Sias

 

[coujam1]

Thanks.