Hi, why don't you just do a "q backup" and look for the files that should be gone according to the new policy. (this can be easily scripted with a bit of grep, awk, or perl knowledge.). Put this filelist in a file and do a "delete backup -filelist=myfilelist".
regards, Volker Am Freitag, den 07.04.2006, 10:45 -0600 schrieb Ben Bullock: > If the files still exist on the client, then they will be > rebound to the new management class. > If the files no longer exist on the client, they will keep their > original retention. > > I know of no way to change files management class once the file > has been deleted from the client. > > I believe I have heard of folks creating new 0-byte files with > the same names and running an incremental to make them get rebound to > the new MC. > > Ben > > > -----Original Message----- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of > Levi, Ralph > Sent: Friday, April 07, 2006 10:33 AM > To: ADSM-L@VM.MARIST.EDU > Subject: rebinding file backups > > I am running a tsm 5.2.7 (AIX) server and W2K3 client w/tsm 5.3 . I > originally was backing up everything with a 90 day retention class but > now I have some specific files that I only want keep for 9 days. I > added an "include" statement for just the 2 directory structures I want > changed and left the generic include alone. The order of the includes > is as seen below. > > Since I made the change newly backed up files in the directories noted > are now backed up with 9day_retention , but the files that were > previously backed up still have the 90day_retention management class on > them. > > Can anyone explain why the old backups did not rebind with the new > management class ? I know in the past if I changed the "include * > mgmt_class" it would rebind everything. > > Thanks for the help and have a nice weekend, Ralph > > Include * 90DAY_RETENTION > include "e:\Database backups\...\...\*.bak" 9DAY_RETENTION > include "e:\Station Files\...\...\*.*" 9DAY_RETENTION >
