Ok,
1st) is it within a "domain"
2nd) is it valid when run through include/exclude processing
3rd) a whole bunch of things... ;-)
        (I seem to remember way back in V2 that multiple things were
checked... just about along the lines of what virus checkers do... size,
checksum, etc...)

I'd check to see if maybe a volume (that might have been holding those
files) went bad on your server...
Also I'd check (via dsmc q backup -inact blahhhh) and see if the size of the
file changed ? ? ?
Also, the file might not have changed but some of the permissions on the
file might have changed (rights to access the file) and I can't say if that
constitutes a "last changed data" alteration on your client platform...

Dwight
> ----------
> From:         Palmadesso Jack[SMTP:Jack.Palmadesso AT swpc.siemens DOT com]
> Reply To:     ADSM: Dist Stor Manager
> Sent:         Wednesday, August 09, 2000 8:43 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      What determines what is to be backed up?
>
> Good Morning,
>
> What criteria does ADSM use to determine what files are to be backed up
> incrementally.  Does it go just by last date modified or by the actual
> contents of the file or something else? I have some clients that show they
> backed up some files last night that have not been modified since 8/2.
> Why
> is this happening?
>
> Jack
>