tup of Bacula, after renaming a folder, the entire folder
contents are saved again.
So not 50GB per day but e.g. 2TB just because the folder is called different.
Thanks
Gesendet: Freitag, 15. September 2017 um 20:47 Uhr
Von: "Heitor Faria" <hei...@bacula.com.br>
An: "Fabian Br
ng_Ba.html
Gesendet: Montag, 11. September 2017 um 17:05 Uhr
Von: "Radosław Korzeniewski"
<rados...@korzeniewski.net[mailto:rados...@korzeniewski.net]>
An: "Roberts, Ben"
<ben.robe...@gsacapital.com[mailto:ben.robe...@gsacapital.com]>, "Fabian Brod"
nktioniert.
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" <rados...@korzeniewski.net>
An: "Roberts, Ben" <ben.robe...@gsacapital.com>, "Fabian B
I have tried it with the following configuration without success.
Job {
Name = BaseData
Type = Backup
JobDefs = ChangerJob
Level = Base
FileSet = BaseFS
}
Job {
Name = BackupClient1
JobDefs = ChangerJob
Base = BackupClient1, BaseData
Accurate = yes
Level = Full
FileSet =
Thanks for the answer.
But what makes it for sense that a moved file with the same MD5 sum is saved
again?
It works as if only the complete path to the file is compared. Does anyone use
Deduplication?
Hello,
Hello, Fabian,
is it normal to back up bacula moved files or renamed files over and
Hello,
is it normal to back up bacula moved files or renamed files over and over again?
I have created a test configuration with base jobs but the files are backed up again and again.
Does anyone have a solution to the problem or a working configuration file?
To the procedure:
1. I'm
