Menu
▾
▴
Re: [Bacula-users-es] Deduplicacion
|
From: Heitor F. <he...@ba...> - 2015-10-09 14:19:46
|
Juan,
Perdóname pelo idioma, pero lo escrebi esta documentacion:
7.17. Files Deduplication1
The main reason to use Bacula Community Files Deduplication is if you have exactly the same files between several different machines. This may be the case if: your operational systems are the same and updated to the last version; you have several machines with the same applications version.
This deduplication works in this manner: you must execute a special prior milestone backup that has a specific level: base job (always full), that should run also in a different pool. Every Bacula client backups that are configured to compare its contents to the base job ones doesn't repeat the copy of the exact same files that were already copied by the base job.
If deduplication is correctly configured you may see at the job log summary the ration of files that were not copied again because they were backed up in the correspondent base job.
In theory you could set up a base backup of a machine and compare only its future backups to its base. The practical effect of that is even you submit a full backup job it Bacula will only copy files that was changed since the last base job termination. It's basically the same behavior of running a full backup and then only differential / incremental ones, so there is not much advantage of using deduplication for a single specific machine.
Configuring Bacula Deduplication:
a) Add the new special Base Backup Job at the bacula-dir.conf. It's advisable to run that in a different pool that you must create, and is also desired to run it in a different Schedule since it's likely you will run it in a lower frequency:
Job {
Name = BaseJob
Level= Base
Pool = “Base-Pool” # you must create that.
...
}
b) Sill at the bacula-dir.conf, add the following directives to the jobs that may have the similar files that you are going to backup with the Base Job. You may also want to configure a different schedule for this job, since it will probably run in a lower frequency:
Job {
Name = BackupHeitor
Base = BackupHeitor, BaseJob
Accurate = yes
Schedule = base_schedule
FileSet = debian_7_set
...
}
The Base directive tell Bacula the universe of regular and base backup jobs that will be compared and not repeating the copy of similar files. In the correct example, BackupHeitor job is comparing itself to the job named BaseJob. The directive Accurate = yes is also a must have.
c) Don't leave bacula-dir.conf yet. You must also make some changes to your original regular backup FileSet:
FileSet {
Name = debian_7_set
Include = {
Options {
BaseJob = pmugcs5
Accurate = mcs5
Verify = pin5
}
File = /etc
File = /var
File = /opt
}
}
Each one of this required options establishes different behaviors to the way searches and compares files between base and regular backup jobs. They are the same for the verify job Bacula feature.
d) At least, still add the new pool and schedule for the base backup jobs. Please consider using a significant Volume Retention that is not shorter than regular backups, otherwise you may loose the ability to perform full restore of some jobs if the base job they rely is already recycled.
Pool {
Name = Base-Pool
Pool Type = Backup
Volume Use Duration = 18 hours
Volume Retention = 364 days
...
}
Schedule {
Name = base_schedule
Run = Differential Pool=Base-Pool 1st sunday at 12:00
}
e) Accomplish a Base job then the now deduplicated regular backup job. You may notice that similar information will appear at your Bacula log job summary:
...
Rate: 2425.4 KB/s
Software Compression: 39.7 %
Base files/Used files: 39336/39114 (99.44%)
VSS: yes
Encryption: no
...
=======================================================================
Heitor Medrado de Faria - LPIC-III | ITIL-F | Bacula Systems Certified Administrator II
Treinamento Presencial Brasília: 09 a 11 de outubro.
Telepresencial: 14 de outubro.
Ministro treinamento in-company Bacula (com implementação) na sua cidade. Me mande um email.
61 8268-4220
Site: www.bacula.com.br | Facebook: heitor.faria
========================================================================
> From: "Ana Emília M. Arruda" <emi...@gm...>
> To: "Juan Carlos huayane" <jhu...@fa...>
> Cc: "Foro Bacula" <bac...@li...>
> Sent: Friday, October 9, 2015 10:05:35 AM
> Subject: Re: [Bacula-users-es] Deduplicacion
> Hola Juan,
> Sí, puedes utilizar la deduplicación basada en ficheros del Bacula en la version
> de la comunidad. Se realiza utilizando la configuración de "base jobs". Son
> trabajos donde el FileSet incluye los ficheros/carpetas que crees que no van a
> ser cambiados a corto plazo. Por ejemplo:
> Job {
> Name = BaseJob1
> Level = Base
> FileSet = BaseJob1FileSet
> ...
> }
> Job {
> Name = BackupServer1
> Level = Full
> Base = BaseJob1
> FileSet = BackupServer1FileSet
> ...
> }
> FileSet {
> Name = BaseJob1FileSet
> Include {
> Options {
> Signature = MD5
> }
> File = /usr
> File = /etc
> }
> FileSet {
> Name = BackupServer1FileSet
> Include {
> Options {
> Signature = MD5
> }
> File = /usr
> File = /etc
> File = /var
> File = /home
> }
> Un saludo,
> Ana
> 2015-10-09 7:23 GMT-03:00 Juan Carlos huayane < jhu...@fa... > :
>> Hola Amigos
>> Tengo una duda. por el tema de ahorro de espacio. hace un tiempo sabia que en
>> Bacula se puede usar deduplicacion pero tengo la duda si es solo para la
>> version de pago o se puede realizar en el de la comunidad. ahora si es libre me
>> pueden indicar como aplicarla
>> Saludos
>> --
>> Juan Carlos Huayane
>> -- http://www.fastmail.com - Same, same, but different...
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> Bacula-users-es mailing list
>> Bac...@li...
>> https://lists.sourceforge.net/lists/listinfo/bacula-users-es
> ------------------------------------------------------------------------------
> _______________________________________________
> Bacula-users-es mailing list
> Bac...@li...
> https://lists.sourceforge.net/lists/listinfo/bacula-users-es
|