#30 Inconsistancy in incremental backups

[Anonymous]

I'm not sure whether this is a bug, or if it was intended this way. Reading your documentation, you seem to contradict yourself in whether with the incremental backups, all files modified since the last full backup should be backed up, or all files modified since the last incremental backup should be backed up.

6. Full / incremental backup difference.
"This means that if you added or modified files in a directory defined for backups, after the last full backup time, they will be picked up in every run until the next full backup time passes."

vs.

7. The restore process.
"1. Choose which day you want to restore.
2. Restore the full backup, then restore every single incremental backup up to the day you choose."

Currently when restoring, you only need to restore the last full backup, and the incremental of the day you choose, and not all the incrementals in between, since the files in the first incremental will also be included in the second and third.

On the other hand to keep backups a bit smaller, it is possible to backup only the files that have been modified since the last backup (either full or incremental). Then your restore process would be as you documented it. To do this line 148 needs to be changed from:
print FILESTATUS $bCounter . "," . $lastFull;
to:
print FILESTATUS $bCounter . "," . $startTime;
This is the option I preferred.

Thanks for the great software!

[Nobody/Anonymous]

Logged In: NO

You can contact me at btaylor at propertysolutions dot com.

[Forrest Lump]

Thank you, nice find. I was wondering why an incremental backup was created even though no files where changed since last incremental backup.

Andreas