Hello,

We are running ADSM client V2R1M4 on every platform now and some of
them are talking to a ADSM V2R1 Level 0.9 on VM (yes!!).

We are looking to the incremental by date facility available with V2
clients.
It looks much more faster than total incremental but does not detect
deleted files or files with changed attributes.

It just obtain the date/time of the last incremental backup and detect
new/modified files as candidates.

This is Okay anyway : we could plan to make partial incremental (by
date)
every week day and then a "full" incremental in the week-end to get
everything synchronized.

During small tests we noticed the following behavior:

Make a full incremental
touch or add N1 files in a filesystem
make a partial incremental (the N1 new files are backed up okay)
make a partial incremental (again the N1 files are backed up !!)
touch N2 files and delete N3 files in the same filesystem
make a partial incremental (N1+N2 files are backed up !!)
make a full incremental (N3 files are deleted)
make a partial incremental (nothing is backed up)

So it seems that partial incrementals are cumulative up to the next full
incremental...

On the server side, the administrative "q files node filespace f=d"
command is correct :

the "Last Backup Completion Date/Time" field is the Date/Time of the
last partial incremental !!

Is this behaviour normal ? or did I miss something ?

Cheers, michel
--
Michel Gaillard
Michel Gaillard
DSI/DPI
Alcatel Telecom
Velizy France
E-Mail: Michel.Gaillard AT vz.cit.alcatel DOT fr
Voice : (33.1) 30 67 32 56