TSM Community, I was able to obtain more detailed information regarding System Object Filespace issue and the Cleanup Backupgroups utility, compliments of Tivoli.
4.2.3 was released 10/14/2002. This official PTF level resolves issues with expiration of file groups which are typically used for SYSTEM OBJECT filespaces for Windows clients and also releases a fully functional utility CLEANUP BACKUPGROUPS. Patch levels after 4.2.2.1 prior to PTF level 4.2.3.0 included interim fixes to both expiration and the CLEANUP BACKUPGROUPS utility. PTF 4.2.3 contains the complete set of fixes including some which were not released in the patch stream. The CLEANUP BACKUPGROUPS utility was first introduced in 4.2.2.1 as part of IC32994 however it was not fully functional until 4.2.3 level of PTF. CLEANUP BACKUPGROUPS will correct the TSM database by evaluating file groups on the server and deleting any file group that is not complete. An error in the server deletion processing for file groups was introduced in 4.2.2.0 which could result in file groups not being completely deleted during expiration or other server deletion activities. This partial deletion of the file group typically resulted in increased database utilization and volumes not being reclaimed or returned to scratch as appropriate. The error in the deletion processing as well as the CLEANUP BACKUPGROUPS utility is available in server level 4.2.3.0 The CLEANUP BACKUPGROUPS utility should be run once on the server after applying the appropriate server maintenance level that contains this fix. This utility will start a background process that can be monitored with the "QUERY PROCESS" command. As a background process, this utility may also be cancelled using the "CANCEL PROCESS" command and restarted as needed to manage the time necessary for this processing to complete. This utility will report the number of file groups it evaluates and the number that were deleted because they were not complete. The deletion error that caused the incomplete deletion of file groups did NOT cause the inappropriate or incorrect deletion of data. It caused data that was supposed to be deleted to not be completely deleted from the TSM server. These fixes are also available in server patch 5.1.5.1 for the V5.1 server. Sam Giallanza Tivoli
