I've used the steps from the manual. FileSet option. "This option works like
the verify = one, which is described in the FileSetFileSetResource chapter."
FileSet {
Name = Full
Include = {
Options {
BaseJob = pmugcs5
Accurate = mcs
Verify = pin5
}
File = /
}
}
Job {
Name = USR
Level = Base
FileSet = BaseFS
...
}
Job {
Name = Full
FileSet = FullFS
Base = USR
...
}
FileSet {
Name = BaseFS
Include {
Options {
Signature = MD5
}
File = / usr
}
}
FileSet {
Name = FullFS
Include {
Options {
Accurate = Ms # check for mtime / ctime and Size
Signature = MD5
}
File = / home
File = / usr
}
}
This tells me that I can also use MD5.
The MD5 sum is also stored in the database but the next backup is ignored.
Another solution would be OK for me.
Deduplication Optimized Volumes for example.
I only want to move or move renamed data again and again if it is not necessary.
The Enterprise version is unfortunately too expensive even if it works well.
http://www.bacula.org/9.0.x-manuals/en/main/File_Deduplication_using_Ba.html
Gesendet: Montag, 11. September 2017 um 17:05 Uhr
Von: "Radosław Korzeniewski"
<[email protected][mailto:[email protected]]>
An: "Roberts, Ben"
<[email protected][mailto:[email protected]]>, "Fabian Brod"
<[email protected][mailto:[email protected]]>
Cc: "Bacula Support"
<[email protected][mailto:[email protected]]>
Betreff: Re: [Bacula-users] Fw: Aw: Re: Renamed and moved files are backed up
again
Hello,
2017-09-06 10:01 GMT+02:00 Roberts, Ben
<[email protected][mailto:[email protected]][mailto:[email protected][mailto:[email protected]]]>:
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
[email protected][mailto:[email protected]][mailto:[email protected][mailto:[email protected]]]
--
Radosław Korzeniewski
[email protected][mailto:[email protected]]
------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
