>
> The cleanup backupgroups is intended for one reason only, to fix a bug in
> prior versions. In version 4.2.2.X, there was a bug that had the effect
> that system objects wasn't expired. What happens is that when you upgrade
> from version 4.2.2.X to version 5.1, the installation will be unable to
> convert the 4.2.2.X database to version 5.1 format.
>
> When upgrading, the installation will go well. However, after the DB
> upgrade, it will tell you to either run a db audit, or run the cleanup
> backgroups. The cleanup backupgroups can run with TSM online, which is not
> possible with an audit. The only thing it will do, is to manually deleted
> expired system objects from the database.
>
> Also, you will not see it running as a process. You will only see that the
> database utilization, and the used pages, will go down. When cleanup
> backupgroups has completed, it will leave a message in your activity log.
>
> I have done this a couple of times, and it isn't a problem. As long as you
> know that you have to run cleanup backupgroups, upgrading to TSM 5.1, wont
> be a problem. Also, after the db upgrade, you will be able to start the
> server. Also, it will function correctly, even if you haven't run cleanup
> backupgroups. BUT, it is highly recommended that you run the cleanup
> command, as the expired system objects will take up both DB space, and
> storage space, which is unnecessary.
>
> The cleanup command will run for a longer period, depending on the size of
> your database, the amount of W2K clients in your environment, and
> depending on how long you have been running backups with version 4.2.2.X.
>
> !!! AS FAR AS I KNOW, THIS PROBLEM IS ONLY RELATED TO VERSION 4.2.2.x OF
> TSM, AND NOT 4.1.3.X.

I am running 4.2.2.0, soon to be 5.1.1.6, and my 4.2.2.0 DB does not have
the problem expiring SYSTEM OBJECT.

Steve Roder, University at Buffalo
HOD Service Coordinator
VM Systems Programmer
UNIX Systems Administrator (Solaris and AIX)
TSM/ADSM Administrator
(spr AT buffalo DOT edu | (716)645-3564)