[Bacula-users] Errors updating file digest in catalog
Hi, Several weeks ago we have updated bacula from version 7.0.5 to 7.4.1. Apparently everything was ok but...we have seen some errors like the following that appear randomly (sometimes on some jobs): Error: Catalog error updating file digest. bdb.h:105 Update failed: affected_rows=0 for UPDATE File SET MD5='qP5pf2IllJ38f2c7Q5eHyA' WHERE FileId=6148914691236517205 Although the MD5 values change, the FileId is always the same: 6148914691236517205, 0x in hexadecimal. * Apparently this value is "special", according Kern's knowledge of bacula code: I've found a thread from late 2015 (https://sourceforge.net/p/bacula/mailman/bacula-users/thread/567B4D44.30307%40sift.net/#msg34717684) referring the same problem with bacula 7.2.0. In that thread, Kern recommended set "Spool Attributes" to yes and according the user this change solved the problem but in our case we have "Spool Attributes" to yes from years so...we don't know what we can do. According the thread and our experience, it appears to be a bug introduced in bacula 7.2.0 and later releases. Any ideas? suggestions? Regards. -- Jose Manuel Blanco. -------- Area de Sistemas Servicio de las Tecnologias de la Informacion y Comunicaciones (STIC) Universidad de Valladolid Edificio Alfonso VIII, C/Real de Burgos s/n. 47011, Valladolid - ESPAÑA Telefono: 983 18-6410, Fax: 983 423271 E-mail: siste...@uva.es AVISO SOBRE CONFIDENCIALIDAD. La legislación española ampara el secreto de las comunicaciones. Este correo electrónico y sus anexos son estrictamente confidenciales. Si Vd. no es el destinatario del mismo, por favor, notifíquenoslo inmediatamente y destruya el original. No deberá copiar este mensaje ni sus anexos o usarlo para propósito alguno, ni divulgar su contenido a ninguna persona. WARNING ABOUT CONFIDENCIALITY. Spanish law guarantees privacy in electronic communications.This message and its attachments are confidential. If you are not the intended recipient please, notify us inmediately and destroy or the original to us. You should not copy this message or use it for any purpose, nor disclose its content to any other person. -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Virtual autochangers: how to "reserve" devices and "media type"
Hi, We have been using bacula with DISK BASED BACKUP during years (in a multi-pool, multi-device configuration) Recently we have "redefined" the devices as autochangers according the Bacula documentation. Although the "whole thing" appears to be running ok we have TWO questions: 1) In the previous "device mode", the MediaType of all defined devices was set as "File"...Now, in the "autochanger mode" I've also used the same MediaType "File" for ALL devices in ALL autochangers... * Is this right or MUST I use a different MediaType for every autochanger (in all its devices)? * If I must use a different MediaType...the change implies some problem with existent volumes? Must I do/change something with the existent volumes? 2) According Bacula documentation is possible to "reserve" a device in an autochanger setting the property "Autoselect=no" in that device definition but... * How can I force bacula to use these reserved devices for a restore command? * The Bacula documentation sais that this can be done but NOT HOW, and apparently the restore command (at least interactively) only permits specify the Storage, not the device... Regards. -- Jose Manuel Blanco. ---- Area de Sistemas Servicio de las Tecnologias de la Informacion y Comunicaciones (STIC) Universidad de Valladolid Edificio Alfonso VIII, C/Real de Burgos s/n. 47011, Valladolid - ESPAÑA Telefono: 983 18-6410, Fax: 983 423271 E-mail: siste...@uva.es AVISO SOBRE CONFIDENCIALIDAD. La legislación española ampara el secreto de las comunicaciones. Este correo electrónico y sus anexos son estrictamente confidenciales. Si Vd. no es el destinatario del mismo, por favor, notifíquenoslo inmediatamente y destruya el original. No deberá copiar este mensaje ni sus anexos o usarlo para propósito alguno, ni divulgar su contenido a ninguna persona. WARNING ABOUT CONFIDENCIALITY. Spanish law guarantees privacy in electronic communications.This message and its attachments are confidential. If you are not the intended recipient please, notify us inmediately and destroy or the original to us. You should not copy this message or use it for any purpose, nor disclose its content to any other person. -- Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San Francisco, CA to explore cutting-edge tech and listen to tech luminaries present their vision of the future. This family event has something for everyone, including kids. Get more information and register today. http://sdm.link/attshape___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Problem with prune/purge in Bacula
Thanks for your unvaluable help Machiel. I've read your previous topic and effectively it explains the really strange behavior of bacula regarding retention parameters :-( But honestly I think this behavior can be considered as a BUG/PROBLEM, cause a situation with a ONE host (= ONE client) with different backup types each one with its own retention parameters (TIPICALLY MEANING A POOL FOR EVERY BACKUP TYPE) can be considered as normal/usual, and the "workaround" of defining for each host different bacula clients (each one with its retention parameters) can't be considered the right way. So...A MESSAGE FOR BACULA DEVELOPERS: Please correct the bacula behavior using retention parameters. According the actual features of bacula and (logically) the documentation, the right/normal/logical/expected behavior of retention parameters (at least from user perspective) would be: 1- retention parameters defined in CLIENT resource: * they must be applied to ALL JOBS of the client, no matter the pool they used 2- retention parameters defined in POOL resource: * they must be applied ONLY to jobs of the client using ONLY THIS POOL, and never affect jobs in other pools Another option would be allow retention parameters ONLY in the client resource and NOT in the pool resource (updating the documentacion accordingly), but I think this would be the wrong way, causing bacula to loose functionality and a good feature. Perhaps are you working on this yet? Thanks in advance. El 10/06/10 16:13, Machiel van Veen escribió: > On Thursday 10 June 2010 03:24:18 pm Area de Sistemas wrote: > >> Perhaps a Bacula bug? >> Perhaps I don't understand the behaviour of retention parameters (I >> think this is less probable cause the problem appears to affect only >> some clients/copies)? >> >> Any ideas? >> >> Thanks in advance. >> >> > It seems you have another job for this client writing to a different pool with > retention times set in the client directive. When this job runs it wil prune > all jobs for the client. Regardless of any file or job retention periods set > in pool directives. > > The solution would be to create new client directives for every retention > period you need and not put them in the pool directive as you do now. > > I found this out the hard way too, if you look for the topic "Pool file/job > retention not updating" you should find my thread on this. > > Machiel. > > -- > ThinkGeek and WIRED's GeekDad team up for the Ultimate > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > lucky parental unit. See the prize list and enter to win: > http://p.sf.net/sfu/thinkgeek-promo > ___ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users > -- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Problem with prune/purge in Bacula
Hi.
We have discovered recently a problem with Bacula.
After some investigations it appears to be related with prune/purge
functions of Bacula.
More precisely it appears that Bacula prunes/purges from catalog more
jobs/files than necessary BUT only in SOME CASES: some clients appears
to have *all* jobs/files information but some not.
* But scanning some volume with older backups (according information in
old log files) they contain data of the "extra" jobs purged/pruned by
Bacula.
Every POOL has the "Volume, File and Job Retentions" and the "Volume Use
Duration" defined according the retention policies needed but it appears
that as I've said in some cases Bacula doesn't applies them correctly.
* We don't use these retention parameters in any other bacula object
(i.e.: clients)
We have bacula-dir 5.0.2.
An example of a pool definition:
Pool {
Name = Diarias-ciclo-1m
Pool Type = Backup
Next Pool = Clonados-Diarias-ciclo-1m
Recycle = yes
AutoPrune = yes
Volume Retention = 7 weeks
File Retention = 7 weeks
Job Retention = 7 weeks
Volume Use Duration = 1 day
Maximum Volumes = 0
Maximum Volume Bytes = 20 g
Storage = Disco-Copias-Diarias-ciclo-1m
Label Format = "diario-"
}
This pool is used for daily copies with a monthly cycle, so the
retention parameters are defined in order to guarantee 1 month of
copies. The retention values are greater than 1 month cause we mix
incremental/full backups (MaxFullInterval=13d, MaxDiffInterval=6d).
Perhaps a Bacula bug?
Perhaps I don't understand the behaviour of retention parameters (I
think this is less probable cause the problem appears to affect only
some clients/copies)?
Any ideas?
Thanks in advance.
P.S.
Sorry for my poor english...I hope you can understand my message.
--
ThinkGeek and WIRED's GeekDad team up for the Ultimate
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
lucky parental unit. See the prize list and enter to win:
http://p.sf.net/sfu/thinkgeek-promo
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
