Incremental by date works the same as full incremental backup except for
the following:

It does not back up files whose last changed date and time is older than
the last incremental backup, even if the files are new to your
workstation.

It does not expire backup versions of files on the server for files that
have been deleted from your workstation. ADSM expires backup versions by
changing them to inactive.

It does not re-bind backup versions to different management classes if
you have changed management class assignments.

It does not back up files whose only changes are to attributes which do
not update the modification dates and times of files.

It does not check the copy frequency attribute of the backup copy group.


Note: It is recommended that you run full incremental backups
periodically to bring the ADSM server in line with your workstation's
status.


Kent L. Johnson wrote:
>
> We have a user running the ADSM 2.1 client with an ADSM 3.1 server.
>
> They have been doing "incremental by date" since installing ADSM.  ADSM
> indicates that the last backup was performed yesterday.  The backups have
> been done manually, approximately daily.
>
> The user is trying to restore a file which had been modified before
> yesterday.  The version which is on the server has a modification date of
> 6/25/98.
>
> Does anybody know of any known problems with the "incremental by date"
> option.  I understand that it is not the preferred option, but it should have
> backed up the file many times since 6/25/98.
>
> - Kent
>
> --
> Kent Johnson                        Internet: johnsk6 AT rpi DOT edu
> Unix Systems Programmer (VCC 323)      Phone: (518) 276-8175
> Rensselaer Polytechnic Institute         Fax: (518) 276-2809