Re: [Bacula-users] Fw: Re: Renamed and moved files are backed up again
On 2017-09-20 09:01, Fabian Brod wrote: 1.If I want to back up multiple folders with projects that have partially identical files. However, these project names can change over time. You don't want to use backup software for this. You want git or zfs with dedup on, or something. I've never seen a backup system that worked the way you want. Dima -- 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
Re: [Bacula-users] Fw: Re: Renamed and moved files are backed up again
1.If I want to back up multiple folders with projects that have partially identical files. However, these project names can change over time. projects Project_A Project_B Project_C -> rename to Project_C01 Project_D Project_E Project_F 2.Yes, if a project consists of several Terrabyt data and only the directory name changes 3. If Bacula still holds the data in an older backup under a different name ... no A full backup of all data would require about 20TB of storage space. Daily about 50GB of new data are added, which should be saved every day. In the current setup 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 Brod" <fabian.b...@gmx.net> Cc: "Bacula Support" <bacula-users@lists.sourceforge.net> Betreff: Re: [Bacula-users] Fw: Re: Renamed and moved files are backed up again Hello, Fabian, > 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. > 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. I read this thread over and I could not find what is the problem that you are trying to solve. 1. Why do you need to deduplicate files backup if they are moved? 2. Will this save a significant amount of storage? 3. Do you really need to backup the data after it is moved? PS.: I never used or observed Bacula File Deduplication using two different FileSets for Base and for the ordinary jobs. Regards, -- === Heitor Medrado de Faria | EB-1 Visa | LPIC-III | ITIL-F | EMC 05-001| Bacula Systems Certified Administrator II • Bacula Enterprise does not charge per backup size and has plugins for many applications. In the USA: http://bacula.us/ • Do you need Bacula training? http://bacula.us/video-classes/[http://bacula.us/video-classes/] +55 61 98268-4220 | http://bacula.us[http://bacula.us] === -- 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
Re: [Bacula-users] Fw: Re: Renamed and moved files are backed up again
Hello, Fabian, > 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. > 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. I read this thread over and I could not find what is the problem that you are trying to solve. 1. Why do you need to deduplicate files backup if they are moved? 2. Will this save a significant amount of storage? 3. Do you really need to backup the data after it is moved? PS.: I never used or observed Bacula File Deduplication using two different FileSets for Base and for the ordinary jobs. Regards, -- === Heitor Medrado de Faria | EB-1 Visa | LPIC-III | ITIL-F | EMC 05-001| Bacula Systems Certified Administrator II • Bacula Enterprise does not charge per backup size and has plugins for many applications. In the USA: http://bacula.us/ • Do you need Bacula training? http://bacula.us/video-classes/ +55 61 98268-4220 | http://bacula.us === -- 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
Re: [Bacula-users] Fw: Re: Renamed and moved files are backed up again
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"
<rados...@korzeniewski.net[mailto:rados...@korzeniewski.net]>
An: "Roberts, Ben"
<ben.robe...@gsacapital.com[mailto:ben.robe...@gsacapital.com]>, "Fabian Brod"
<fabian.b...@gmx.net[mailto:fabian.b...@gmx.net]>
Cc: "Bacula Support"
<bacula-users@lists.sourceforge.net[mailto:bacula-users@lists.sourceforge.net]>
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
<ben.robe...@gsacapital.com[mailto:ben.robe...@gsacapital.com][mailto:ben.robe...@gsacapital.com[mailto: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[mailto:rados...@korzeniewski.net][mailto:rados...@korzeniewski.net[mailto:rados...@korzeniewski.net]]
--
Radosław Korzeniewski
rados...@korzeniewski.net[mailto: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
Re: [Bacula-users] Fw: Re: Renamed and moved files are backed up again
Ich habe die Schritte aus dem Handbuch benutzt.FileSet option. "This option
works like the verify= one, that 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
}
}
Das sagt mir das ich auch MD5 benutzen kann.
Die MD5 Summe wird ja auch in der Datenbank hinterlegt aber beim nächsten
Backup irgend wie ignoriert.
Eine andere Lösung wäre für mich ja auch OK.
Deduplication Optimized Volumes zum Beispiel.
Ich möchte nur nicht verschobene oder umbenannte Daten immer wieder neu Sichern
wenn es nicht nötig ist.
Die Enterprise Variante ist leider zu Teuer auch wenn Sie gut funktioniert.
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 Brod"
<fabian.b...@gmx.net>
Cc: "Bacula Support" <bacula-users@lists.sourceforge.net>
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
<ben.robe...@gsacapital.com[mailto: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[mailto: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
