If you assign the SYSTEMOBJECT to a different management class that only
keeps them for 45 days, the next time you run a backup all the copies
older than that will be expired automatically.  The tape/backup space
they occupy will be freed up the next time your expiration runs.

Look in the client manual for the syntax: 
   include systemobject all  mgmtclassname


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Jones, Eric J
Sent: Wednesday, January 26, 2005 7:21 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: SYSTEM OBJECT question


Good Morning.
Is there a way to delete old "SYSTEM OBJECT" files that are backed up?
What we currently do is, do an incremental backup on the entire machine
including the "SYSTEM OBJECT" nightly and keep for 90 days.  What I'd
like to do is delete some of the old "SYSTEM OBJECT" files that are old
and no longer needed.   I'm planning on changing so the "SYSTEM OBJECTS"
are only kept for 45 days but was wondering if there was a way to clean
out some of the old "SYSTEM OBJECT" backups.
I'm also planning on having Win2k backup(NTBACKUP) the SYSTEM OBJECT
file to a file before the TSM backup then have TSM backup that file.
Does anyone know of a problem with this instead of having TSM backup the
SYSTEM OBJECT everynight?
The way we currently recover if necessary
1:  Put a minimal OS on system
2:  Install TSM
3:  Restore all files to the system
4:  Restore the SYSTEM OBJECT
What I'm planning is to change the 4th step and with the files recovered
which would include the backup of the SYSTEM OBJECT(NTBACKUP) have
NTBACKUP restore from the backed up file the SYSTEM OBJECT.  I've read
in the forum some of the notes and it seems like it works without a
problem.
============================================
Client - Win2K SP3 with TSM 5.2.2
Server - AIX 5.2 with TSM 5.2.2

Have a Great Day,
Eric