If it's only a few files, you can force them to expire by using the following
workaround
1. Define a management class with zero retentions.
2. In the options file, include each file or directory that you want to wipe
    to the new management class, and exclude the same files from the default:
    example:
    Exclude  c:\userstuff\oldstuff\unwanted.dat
    Include c:\userstuff\oldstuff\unwanted.dat new-management-class
    (If the files have already been deleted from the source, you can create
    dummy files with the same name as the old.)
 3. (If running the scheduler service, stop and restart the scheduler to force
it to
     re-read the options file)
4. Run an incremental backup against the files to bind them to the new class,
5. Delete the files from the source.
6. Run another incremental to expire the now deleted files.
7. Clean up the options file

On Friday, February 25, 2000 10:58 AM, Fujikawa, Walt [SMTP:WFujikaw AT EBMUD 
DOT COM]
wrote:
> Situation:
> User deletes some files off of a Novell server volume that's backed up with
> ADSM.  ADSM comes along and sees they no longer exist and expires them.
> User knows they are still on tape and requests to have them deleted from
> tape.
> Is there a way to purge these individual files from the tape without
> affecting the other gazillion files in the given storage pool?  The policy
> set that these files live in is setup as such:
> If client data exists keep 2 versions.
> If client data is deleted keep 2 versions.
> Retain extra backup version 180 days.
> Retain only backup version 360 days.