Well, I must be putting in too many hours and not getting enough sleep
(sheepish grin)... There is another problem that I was reminded of this
morning, APAR IC18287, that may also pertain to files that have undergone
compression or decompression. While we are ignoring the compression bit, we are
*not* ignoring the data streams size attribute of the file, which is the number
of physical blocks used to contain the file's data streams. The data streams
size changes with compression, so ADSM detects it changed and backs the file
up. So a mass compression or decompression of your files may also account for
this problem.

Andy Raibeck
ADSM Level 2 Support
---------------------- Forwarded by Andrew Raibeck/San Jose/IBM on 11-14-97
4-97
07:39 AM ---------------------------


Andrew Raibeck
11-14-97 12:10 AM
To: ADSM-L AT VM.MARIST DOT EDU @ internet
cc:
From: Andrew Raibeck/San Jose/IBM @ IBMUS
Subject:  Re: Novell client out of control

Hi Barb,

There are a couple of possibilities that come to mind:

1) Do you have "NWIGNORECOMPRESSBIT YES" in DSM.OPT? When files undergo NetWare
compression, an attribute is set indicating that the file has been compressed
(or decompressed). If you just had some mass compression (or decompression)
take place, and NWIGNORECOMPRESSBIT is not set to YES (default is NO), then
ADSM will consider the file to have been changed, and it will get backed up.

2) APAR IC18956 is currently open against a known problem with the NetWare
client. Some software, such as other backup software or anti-virus software,
may flip the archive bit on the files. The NetWare client detects that one of
the attributes has changed, and thus backs the file up. The APAR indicates that
ADSM should ignore archive bits (as it does on the other clients).

Andy Raibeck
ADSM Level 2 Support

        ADSM-L AT VM.MARIST DOT EDU
        11-13-97 11:08 PM
Please respond to ADSM-L AT VM.MARIST DOT EDU @ internet

To: ADSM-L AT VM.MARIST DOT EDU @ internet
cc:
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