A couple of ideas:

1) Rename the node's existing file spaces on the TSM server to something
else (i.e. rename /usr to /usr_old). Then the next incremental backup will
create a new file space on the TSM server, with brand new backups. After
you are comfortable that you don't need the /usr_old file space any more,
delete it (and other old file spaces) from the TSM server.

2) Change your backup copy groups' MODE setting from MODIFIED to ABSOLUTE.
The next incremental backup will back up everything (that isn't excluded),
regardless of whether it has changed.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.




"Lane, Debbie" <Debbie.Lane AT INTERMEC DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
03/05/2002 10:17
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Full backups



We have been using ADSM for a few years.  Management has asked if it is
possible to "start over", that is make it look like this is the first day
we
are using ADSM and run all full backups.
Any ideas?

Thanks,

Debbie