Thanks. These are mostly database backups that are time stamped so yes, they no longer exist. Unfortunately it took me 60 days to notice they were being keep. Based on your explanation I will just have to wait until they hit their 90 day expiration.
Thanks again, Ralph -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Ben Bullock Sent: Friday, April 07, 2006 12:46 PM To: [email protected] Subject: Re: rebinding file backups 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: [email protected] 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
