Hello,

I suspect that this may be APAR IC19431 (no ETA for fix yet). Theoretically,
the backup versions of the deleted files should be rebound based on the new
policy information, just as they do for files that still exist.

The best circumvention for this problem is to redefine the management class to
which the deleted files are bound, and then run an incremental backup of the
client node. This should cause the deleted files to be expired. After the
backup completes, the management class definition can be deleted.

Andy

Andy Raibeck
IBM Storage Systems Division
ADSM Client Development
e-mail: storman AT us.ibm DOT com



ADSM-L AT VM.MARIST DOT EDU on 07/23/98 12:58:48 AM
Please respond to ADSM-L AT VM.MARIST DOT EDU
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Re: ADSM tries to backup deleted files...


Hi Jean!
I don't think ADSM is backing up the deleted file, while it tries to back up
the file, it notices that the file is deleted and so it tries to expire it.
In order to do that it needs information about the file's management class.
That's where your problem is. Apparently you have changed/updated the
management class for this file. The (former) management class for the file
exists but does not have a valid backup copy group assigned. You should have
seen the same error when you activated the new/changed policy set.
Check which management class was/is used for the file and update it so it
has a valid backup copy group. ADSM will expire the file during the next
backup run.
Kindest regards,
Eric van Loon