It's weird.  If you MOVE a node from one DOMAIN to another,
active files will start backing up to the appropriate new management class
in the new domain.

However, inactive files that were deleted and are ready to expire get the
"no valid backup copy group" message, if the new domain DOES NOT have a
management class by the same name as their original management class in the
old domain.

I don't think there is a fix for it.  The circumvention is to create a
management class in the new domain with the same name as the old domain.

If you need more information email me directly, I will try to find the
original APAR text.

************************************************************************
Wanda Prather
The Johns Hopkins Applied Physics Lab
443-778-8769
wanda_prather AT jhuapl DOT edu

"Intelligence has much less practical application than you'd think" -
Scott Adams/Dilbert
************************************************************************




> -----Original Message-----
> From: Doug Streit [SMTP:jstreit AT ODU DOT EDU]
> Sent: Wednesday, September 08, 1999 9:41 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      invalid management class
>
>      I have over 700 files that are indicating they do not have a valid
> Backup Copy Group.  My understanding is a little sketchy, but apparently
> this is due to a change we made with our domain or management class a
> while
> back.  I believe these files have been deleted and should be expiring but
> they are referencing a management class that does not exist.
>      They are showing up as failed objects on my backups and I need to get
> them cleaned up.  Any ideas how I go about getting them to expire, or how
> to get them associated with a valid Backup Copy Group?
>
> Thanks,
> Doug