This may be a long shot, but here's one scenario that might explain what is
happening:
      There were active copies of these folders in ADSM prior to the time you
reassigned management classes.
      These active copies in the ADSM DB would continue to point to one of the
old management classes/copy groups.
      When the scheduled backup runs the information in the ADSM DB for that
client is downloaded to the client so that the
           backup client can determine if the file is new, has changed, or has
been deleted.
      If the file has been deleted, the ADSM client will mark the file as
inactive and normal ADSM retention rules will control
          when the copies start dropping off.
     If a valid copy group does not exist, ADSM issues the error message that
you received. The last sentence "This file will not
          be backed up." may be extra information that does not apply in this
case.

         Here's some rough pseudocode to show the same thing

         Get Next ADSM DB entry
         Does this ADSM DB entry have a valid copy group?
         No
              Issue ANS1105E message
         Yes
             Does this file still exist on the client?
              NO
                     Set ADSM DB entry to Inactive because file has been deleted
             Yes
                    Has this file changed since previous backup?
                    Yes
                          Send a new backup to ADSM server
                    No
                         No need to back it up again

You might try creating the same copy groups that existed in the old domain in
your new domain. Then ADSM might not encounter the error and could then mark the
file inactive when the next scheduled backup runs.


Steve Branch
Phillips Petroleum
e-mail: swbranc AT ppco DOT com





Eliza Lau <lau AT VTCAT.CC.VT DOT EDU> on 01/20/2000 12:36:51 PM

Any replies will be addressed to: "ADSM: Dist Stor Manager"
      <ADSM-L AT VM.MARIST DOT EDU>


To:   ADSM-L AT VM.MARIST DOT EDU

cc:
(bcc: S W Branch/Sweeny/Phillips Petroleum/us)







 Subject: phantom folders in the recycle bin







Dear ADSMers,

server: ADSM 3.1.2.40 on AIX 4.3.2
client: NT 4.0 SP 4

I am baffled by two phantom folders in the recycle bin that refuse to go
away.  After I reassigned an NT client to a different management class in a
different domain two subfolders in the recycle bin just won't go away.  The
recycle bin is empty, and there are no subfolders or files listed under the
SID folders.  Explorer is set to list all hidden files.  I even excluded the
RECYCLER folder in dsm.opt with "exclude.dir ?:\recycler", backup the disks a
few times, and restarted the scheduler.  But everytime schedule backup runs
it generates the following two error messages.




01/19/2000 08:36:58 ANS1228E Sending of object
'\\bajor\c$\RECYCLER\S-1-5-21-766837305-1282808310-1190612905-1004\DC0\License
Manager' failed
01/19/2000 08:36:58 ANS1105E The management class for this file does not have a
valid backup copy group.
This file will not be backed up.

01/19/2000 08:36:58 ANS1228E Sending of object
'\\bajor\c$\RECYCLER\S-1-5-21-766837305-1282808310-1190612905-1004\DC0' failed
01/19/2000 08:36:58 ANS1105E The management class for this file does not have a
valid backup copy group.
This file will not be backed up.



dsmc q backup -subdir -ina
"c:\recycler\S-1-5-21-766837305-1282808310-1190612905-1004\"
lists the folders "DC0" and "DC0\License Manager" as ACTIVE with an unknown
management class.


Where are these two folders hiding and how do I get rid of them?  Why does
ADSM think that they even exist and are active?
I have tried everything short of deleting the recycle folder and let NT create
a new one.  Please help.


------------------------------------------------------------------------------
 Eliza Lau
 Eliza Lau
 Virginia Tech Computing Center                email : eliza.lau AT vt DOT edu
 Virginia Polytechnic Institute & State University
 1700 Pratt Drive
 Blacksburg VA 24060                           phone : (540) 231-9399
------------------------------------------------------------------------------
=========================================================================