Hi!
I think I solved it. I have defined the path in "Archive Device" of the
Device, defined in bacula-sd.conf, to point to the same directory as the
path in "Archive Device" of the Device for incremental backups. I have
read this advice in "Bacula : Network backup strategies and solutions".
I think I have understood too how virtual buff behaves and how job
dependency works finally :) :)
Thank you so much,
Best regards,
El 2022-02-10 08:57, ego...@ramattack.net escribió:
> Hi!,
>
> Concretely for all this set up I have borrowed ideas from
> https://www.bacula.lat/bacula-virtual-synthetic-full-and-forever-incremental-backups/?lang=es
>
>
> But it seems not to work as its... directly....
>
> Cheers!
>
> El 2022-02-09 19:48, egoitz--- via Bacula-users escribió:
>
>> ATENCION: Este correo se ha enviado desde fuera de la organización. No
>> pinche en los enlaces ni abra los adjuntos a no ser que reconozca el
>> remitente y sepa que el contenido es seguro.
>>
>> Good afternoon,
>>
>> I have been trying to configure Bacula 11 with PostgreSQL 12 as database
>> backend. (Have not seen a more advisable combination...)
>>
>> One of my goals, was to be able to do only once a first full backup and
>> later each day run an incremental backup.
>>
>> Basically I wanted to have :
>>
>> - Four month of virtualfull backup (so 4 virtual full backup) that have been
>> done in the first day of each month. Perhaps an incremental one really too,
>> after this virtual full backup of the first day of the month.
>>
>> - The rest of the days of these 4 month I would do incremental backups from
>> it's parent virtual full.
>>
>> - So, I wanted to have a virtual full backup per month, done the first day
>> of each month for having more "handy or easy" restoration, from any of the
>> following incremental backup.
>>
>> For achieving that, I have configured (I put just what I consider that are
>> the relevant parts only ) :
>>
>> + IN THE SD
>>
>> Device {
>> Name = FileStorage-BACK999999
>> Media Type = File
>> Archive Device = /expert/baculadata/LIBRERIA/LIBRERIA-BACK999999
>> LabelMedia = yes; # lets Bacula label unlabeled media
>> Random Access = Yes;
>> AutomaticMount = yes; # when device opened, read it
>> RemovableMedia = no;
>> AlwaysOpen = no;
>> Maximum Concurrent Jobs = 5
>> }
>>
>> Device {
>> Name = FileStorage-BACK999999-VF
>> Media Type = File
>> Archive Device = /expert/baculadata/LIBRERIA/LIBRERIA-BACK999999-VF
>> LabelMedia = yes; # lets Bacula label unlabeled media
>> Random Access = Yes;
>> AutomaticMount = yes; # when device opened, read it
>> RemovableMedia = no;
>> AlwaysOpen = no;
>> Maximum Concurrent Jobs = 5
>> }
>>
>> Device {
>> Name = FileStorageRestore-BACK999999
>> Media Type = File
>> Archive Device = /expert/baculadata/LIBRERIA/LIBRERIA-BACK999999R
>> LabelMedia = yes; # lets Bacula label unlabeled media
>> Random Access = Yes;
>> AutomaticMount = yes; # when device opened, read it
>> RemovableMedia = no;
>> AlwaysOpen = no;
>> Maximum Concurrent Jobs = 5
>> }
>>
>> + In the dir
>>
>> Storage {
>> Name = File-BACK999999
>> Address = node05.cloudbackup.ramattack.net
>> SDPort = 9103
>> Password = "the-password-used"
>> Device = FileStorage-BACK999999
>> Media Type = File
>> Maximum Concurrent Jobs = 5
>> TLS Enable = Yes
>> TLS Require = Yes
>> TLS CA Certificate File = "/usr/local/etc/bacula/cacert.pem"
>> TLS Certificate =
>> "/usr/local/etc/bacula/node05.cloudbackup.ramattack.net-cert.pem"
>> TLS Key = "/usr/local/etc/bacula/node05.cloudbackup.ramattack.net-key.pem"
>> }
>>
>> Storage {
>> Name = FileStorage-BACK999999-VF
>> Address = node05.cloudbackup.ramattack.net
>> SDPort = 9103
>> Password = "the-password-used"
>> Device = FileStorage-BACK999999-VF
>> Media Type = File
>> Maximum Concurrent Jobs = 5
>> TLS Enable = Yes
>> TLS Require = Yes
>> TLS CA Certificate File = "/usr/local/etc/bacula/cacert.pem"
>> TLS Certificate =
>> "/usr/local/etc/bacula/node05.cloudbackup.ramattack.net-cert.pem"
>> TLS Key = "/usr/local/etc/bacula/node05.cloudbackup.ramattack.net-key.pem"
>> }
>>
>> Storage {
>> Name = FileRestore-BACK999999
>> Address = node05.cloudbackup.ramattack.net
>> SDPort = 9103
>> Password = "the-password-used"
>> Device = FileStorageRestore-BACK999999
>> Media Type = File
>> Maximum Concurrent Jobs = 5
>> TLS Enable = Yes
>> TLS Require = Yes
>> TLS CA Certificate File = "/usr/local/etc/bacula/cacert.pem"
>> TLS Certificate =
>> "/usr/local/etc/bacula/node05.cloudbackup.ramattack.net-cert.pem"
>> TLS Key = "/usr/local/etc/bacula/node05.cloudbackup.ramattack.net-key.pem"
>> }
>>
>> AS JOB IN BACULA CONFIG :
>>
>> JobDefs {
>> Name =
>> "backed-up-vm-by-bacula-server.clientes.cloudbackup.ramattack.net-fd_defs"
>> Client =
>> "backed-up-vm-by-bacula-server.clientes.cloudbackup.ramattack.net-fd"
>> Messages = GENERAL05
>> Priority = 10
>> }
>>
>> Job {
>> Name =
>> "backed-up-vm-by-bacula-server.clientes.cloudbackup.ramattack.net-fd_copia"
>> JobDefs =
>> "backed-up-vm-by-bacula-server.clientes.cloudbackup.ramattack.net-fd_defs"
>> Type = Backup
>> Schedule = "SEMANAL_MIERCOLES_1800"
>> Messages = GENERAL05
>> ######Max Full Interval = 7 days no sense.... when using virtualfulls I
>> assume...
>> Backups To Keep = 32
>> DeleteConsolidatedJobs = yes
>> Pool = catalogo_BACK999999_incrementales
>> NextPool = catalogo_BACK999999_VF
>> Reschedule On Error = Yes
>> Reschedule Interval = 10 minutes
>> Reschedule Times = 5
>> Max Wait Time = 7200
>> Accurate = Yes
>> Storage = File-BACK999999
>> FileSet =
>> "backed-up-vm-by-bacula-server.clientes.cloudbackup.ramattack.net_backup_fileset"
>>
>> Write Bootstrap =
>> "/expert/baculadata/Bootstrap/backed-up-vm-by-bacula-server.clientes.cloudbackup.ramattack.net-fd.bsr"
>>
>> RunAfterJob =
>> "/expert/scripts/scripts-jobs-post-pre/generar_cache_catalogo.sh %i %h %l
>> BACK999999 0"
>> }
>>
>> When I have a a normal full backup plus perhaps 40 incremental backups of
>> backed-up-vm-by-bacula-server I induce a VirtualFull by modifying the
>> schedule used, causing in SEMANAL_MIERCOLES_1800, just a virtualfull in that
>> moment. It does great. It seems to consolidate jobs. Later as I set to
>> remove the consolidated ones... they get removed.... ALL seem FINE, until
>> here....
>>
>> But know... If create for instance, 10 incrementals more and I modify again
>> the SEMANAL_MIERCOLES_1800 schedule, in order to induce a new virtual full
>> at just the new time, when I do that this time does not work. It seems, it
>> cannot find the virtual full dedicated tapes in the location
>> /expert/baculadata/LIBRERIA/LIBRERIA-BACK999999 . But that's normal!! it
>> should be looking at /expert/baculadata/LIBRERIA/LIBRERIA-BACK999999-VF
>> instead!!!. At this moment I cannot do more virtual full job backups. I'm
>> stuck here....
>>
>> Apart from that I'm almost sure this config is not allowing me to have :
>>
>> - A normal full (first time) and 31 incrementals
>>
>> - New month a new virtualfull and new 31 incrementals and so on....
>>
>> - New month a new virtualfull and new 31 incrementals and so on....
>>
>> .
>>
>> .
>>
>> I say it... because I'm seeing that due to :
>>
>> Backups To Keep = 32
>> DeleteConsolidatedJobs = yes
>>
>> what I end up by getting is.... imagine I have the first month :
>>
>> 1 normal full + 50 incrementals that month (imagine I have done 50
>> incrementals because I have run them by hand due to something or
>> whatever...).....
>>
>> After the following virtualfull I end up with the 1 normal full + 32
>> incrementals + 1 new virtualfull + 1 incremental...... but then... how could
>> I recover a backup a position like was first normal full + 4 incremental
>> backups?. Is it consolidated in some place?. Where?. In the new
>> virtualfull?. But then, I think you could end up :
>>
>> A normal full + gap of deleted incrementals + N incrementals.... as far as I
>> know... you cannot recover an incremental is some of them have disappeared
>> from the previous full. Isn't it?.
>>
>> Any help would be extremely appreciated,
>>
>> Best regards,
>> ATENCION
>> ATENCION
>> ATENCION!!! Este correo se ha enviado desde fuera de la organizacion. No
>> pinche en los enlaces ni abra los adjuntos a no ser que reconozca el
>> remitente y sepa que el contenido es seguro.
>> ATENCION
>> ATENCION
>> ATENCION!!! Este correo se ha enviado desde fuera de la organizacion. No
>> pinche en los enlaces ni abra los adjuntos a no ser que reconozca el
>> remitente y sepa que el contenido es seguro.
>>
>> _______________________________________________
>> Bacula-users mailing list
>> Bacula-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bacula-users
>>
>> ATENCION: Este correo se ha enviado desde fuera de la organización. No
>> pinche en los enlaces ni abra los adjuntos a no ser que reconozca el
>> remitente y sepa que el contenido es seguro._______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
