Hello,
2017-09-06 10:01 GMT+02:00 Roberts, Ben <ben.robe...@gsacapital.com>:
> Hi Fabian,
>
>
>
> Others on the list may correct me if I’m wrong, but fundamentally Bacula
> treats different filenames as different entities to be backed up,
> regardless of content being shared across multiple files. The flags you
> have been changing only relax the checks for a given filename to see
> whether it should be backed up or not based on changes to content or
> metadata. Renaming or moving a file will cause the object to be backed up
> under the new filename again.
>
To correct all misleading statements someone can spread across internet:
Bacula will always backup the file on Incremental or Differential backups
which fullname (path+filename) does not exist at previous backups (some
additional restrictions/conditions apply). It is a true for both Bacula
Community and Bacula Enterprise and I believe it is a true for virtually
every backup system you have in the wild. No exceptions. This is a
fundamental backup functionality.
The main difference you can get using different backup software (i.e. BC
vs. BEE+Deduplication) is the content size stored in archive. Some software
can compress (as a deduplication is a kind of data compression) the file
content to achieve smaller data archive. This is what Bacula Enterprise
with GED or Aligned volumes (*) try to do.
*) To be correct Aligned volumes does not make deduplication but allow
third party external deduplication software/hardware to makes the best.
best regards
--
Radosław Korzeniewski
rados...@korzeniewski.net
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
