Item Subject: Strange behavior on NetWare
     OK, hate me if you must but you're at PTF #3...
     Now that's out of the way... it would be safe to say if ADSM wrote to
     the error log in a directory that the directory changed...outside of
     that I haven't heard anything from our Netware folks... (but we are
     using PTF #4 Oh that hurt to say...)
     My understanding is that it runs similar to IBM's antivirus program in
     that it tracks the size, attribute settings, etc. BUT it doesn't touch
     anything. We had real concerns when rolling ADSM out 'cause we wanted
     to also keep running another product until folks were sure of ADSM.
     Folks yelled at first that ADSM was TOUCHING all sorts of stuff like
     the archive attribute but then after just short of a court of law they
     explained things away by other tasks they were running on their
     systems.
     Oh, ADSM might trigger updates on the directories 'cause it is netware
     certified so it must use netware I/O routines... I bet when ADSM opens
     the files to back them up it (Novell) updates the directory entries.
     On unexplained backups, check for anti-virus programs running against
     such files...also ck your share options on the backups... (this might
     point the netware folks to something) but since adsm has to use
     netware I/O routines GOD only knows what they are doing with ADSM's
     requests... Oh, do you have Novell's compression activated... one big
     early complaint was that netware would uncompress the files to give to
     ADSM only to have ADSM compress them again, if you had compression
     turned on...
     later
         DWight



______________________________ Reply Separator _________________________________
Subject: Strange behavior on NetWare
Author:  ADSM-L at unix,sh/DD.RFC-822=ADSM-L AT VM.MARIST DOT EDU
Date:    2/10/97 5:36 PM


Question for you NetWare gurus:

Environment: NetWare 4.10, ADSM 2.1.0.3

Question:  Does ADSM update the timestamps on directories when it backs
           up files from those directories?

           One of our NetWare users reports that this is the case, and has
           some pretty strong evidence to support it.  The timestamps in
           the dsmsched.log file match the timestamps on the directories.

           However, we see one other inexplicable behaviour.  An ADSM
           incremental is backing up all the files in some directories
           (perhaps all), even though the timestamps on those files indicate
           that they have not not changed recently.  This seems to only have
           happened on one particular day.  We cannot explain why - no one
           has access to this volume, other than the sysadmin, and he "did
           not make any changes that day".

Question:  On NetWare, what does ADSM look at (besides the timestamp) on a
           file to determine whether it has changed or not?

Thanks for any ideas.
..Paul

Paul Zarnowski                     Phone:   607/255-4757
Network & Computing Systems        Fax:     607/255-6523
Cornell University                 US Mail: 315 CCC, Ithaca, NY 14853-2601