Hi Eric,

Check out APAR IC19431. This sounds like your problem. The
APAR closed about a month ago.

Until the fixing PTF is available, the best circumvention
is to create the management class to which the files are
bound in the new domain, then run an incremental backup.
The files should expire. After that you can delete the
management class, and you shouldn't see the problem again.

Best regards,

Andy

Andy Raibeck
IBM Storage Systems Division
ADSM Client Development
e-mail: storman AT us.ibm DOT com
"The only dumb question is the one that goes unasked."

Hi ADSM-ers!
I ran into the following situation:

Day 1: Incremental backup of Client
Day 2: Client assigned to a new Policy Domain, deleted the old one.
Day 3: c:\test on Client deleted
Day 4: Incremental backup of Client

The last backup reported a ANS5128E No Backup Copy Group for c:\test, so it
looks like ADSM cannot rebind deleted directories. This looks like a bug to
me, but I cannot find an APAR (I looked for the ANS5128E message).
Anybody seen this too?
Kindest regards,
Eric van Loon