Andy, The exclude statements prevent files from being backed up incrementally. The management class determines how long the files are retained (number of versions or number of days). Files that have been backed up are expired according to the management class rules.
Regards, Jim Schneider -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Andrew Carlson Sent: Wednesday, March 28, 2007 10:15 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Expiring Files that Have Been Exluded We have a situation where we have two entries in our dsm.sys. One of the entries contains an inclexcl that excludes certain database filesystems, though the exlclude is using exclude not exclude.fs. The other has no inclexcl, so that when the DB person runs their backup script, the files are backed up. He is using selelctive backup statements. We thought this all was working, until we noticed, because we needed a restore, that we did not have as many backup versions as we thought we should. What we discovered, is that the backup using the inclexcl list is expiring backups in those directory.filesystems even though they are excluded. Is this the way it works? Would it work the same way if we used exclude.fs instead? the manual says that exclude.fs and exclude.dir are dropped outright, but for exclude, and etc, it only says the file is not backed up - it does not specify that the file will be expired. Thanks for any input you can provide. P.S. TSM 5.3.2.3 on AIX 5.2.8 with Sun Solaris client version 5.3.0. -- Andy Carlson ------------------------------------------------------------------------ --- Gamecube:$150,PSO:$50,Broadband Adapter: $35, Hunters License: $8.95/month, The feeling of seeing the red box with the item you want in it:Priceless.
