I had a similar problem and it was due to someone (ok me) changing the
backup copy group to copy mode absolute.  There was a reason for changing
this during a test we performed but a bug in the GUI which resulted in the
value not being updated.  We ended up using the admin command line
interface to verify and reset the value from absolute to modified.

Hope this is the problem and solves the mystery.



To:       ADSM-L AT VM.MARIST DOT EDU
cc:        (bcc: Brian Bowen)
From:     lundberg AT ALLINA DOT COM @ WORLDCOM
Date:     11/13/97 03:50:16 PM CST
Subject:  Novell client out of control




I have a Novell client that has been backing up to our ADSM/6000 server
for well over a year.  The client is Novell 4.1,
the adsmclient code is at 2.1.0.6 G and the adsmserver code is at
2.1.0.12.  Last night for what ever reason, instead of doing the normal
scheduled incremental backup, it is doing a full server backup.  We can
actually see files being backed up that are dated back to the first of
the year.  This Novell server has 30 gig of data,  it will take a
lifetime to back the entire thing up.
What would cause this?  Does anyone have any  idea  what could have
possibly changed that ADSM thinks all of the files are eligible for
backup.  The Novell people assure me that they haven't done anything to
change the status of  all the files. Nothing has changed on the ADSM
server side, the copygroup has the mode set to modified.  Any help,
ideas , suggestions would be greatly appreicated......

Barb Lundberg
Allina Health System
lundberg AT allina DOT com