It would indeed be a great space saving feature.
But I wouldn't place my bet only on md5sums, it has been proven that
there -could- occur false matches. There has to be some additional
checking as well, starting with the filename. The chances of a
duplicate md5sum in the same filename, while
Tijl Van den Broeck wrote:
It would indeed be a great space saving feature.
But I wouldn't place my bet only on md5sums, it has been proven that
there -could- occur false matches. There has to be some additional
checking as well, starting with the filename. The chances of a
duplicate
I have seen this discussed in this list before and I believe there are several problems on top of the small chance that a file will have the same size and same md5sum but different contents. One is do we only search (for dups) in the current backup job or volume or do we include other backups and
John Drescher wrote:
I have seen this discussed in this list before and I
believe there are several problems on top of the small chance that a
file will have the same size and same md5sum but different contents.
One is do we only search (for dups) in the current backup job or volume
or do we
Hello list!
I could not find hints towards this in the manual, and wonder if this
can be done with bacula:
I would like to prevent duplicate files from being backuped to the
Storage. For example: User A has a zip-File in his Download folder, and
the same zip-File in his user folder. Can I
Jens Classen wrote:
Hello list!
I could not find hints towards this in the manual, and wonder if this
can be done with bacula:
I would like to prevent duplicate files from being backuped to the
Storage. For example: User A has a zip-File in his Download folder, and
the same zip-File in
