Re: [bareos-users] bareos-dbcheck/bareos-dir -t fails everytime

? Kind Regards Sebastian Sura 26.04.24 um 14:28 schrieb Max: Hi guys, I've got  a Rocky 9 Linux VM with a predeployed PostgreSQL-DB (14.11) via ansible. The name, dbname, dbuser & dbpassword are set correctly in "/etc/bareos/bareos-dir.d/catalog/MyCatalog.conf" and the bconsole see

Re: [bareos-users] help on autoxflate

Try starting your storage daemon with debug level of at least 50 (so for example with -d100 on the command line). This should show you whether the daemon was able to load the plugin or not. You can also look at our test code, e.g. here:

Re: [bareos-users] Copy Job die after 1 minute but still running

A bug sneaked into that release.  Please update to the newest version. Am 28.03.24 um 09:26 schrieb 'Alexander P' via bareos-users: Hello everyone, Yesterday I updated from Bareos 22.1.2 to 23.0.3. I also updated the database as described here

Re: [bareos-users] MD5 digest not same File as attributes

Hi Samuel, i think i managed to reproduce your Problem.  I created a fix here if you want to check it out: https://github.com/bareos/bareos/pull/1745 Kind Regards Sebastian Sura Am 04.03.24 um 11:43 schrieb 'Samuel' via bareos-users: I finally had the chance to restart the storage daemon

Re: [bareos-users] SD Error "Volume previously written"

Sebastian Sura Am 26.02.24 um 15:13 schrieb Leon Bartle: Yes it does! bareos-sd (100): stored/ansi_label.cc:70-179 Read ansi label. bareos-sd (100): stored/ansi_label.cc:84-179 Read device got: ERR=Cannot allocate memory bareos-sd (130): stored/label.cc:143-179 Big if statement in ReadVolumeLabel

Re: [bareos-users] MD5 digest not same File as attributes

inflates on write. Do i have that right ? Does the device where the job gets consolidated onto allow concurrent writes from multiple jobs ? What selection type has your copy job ? Kind Regards Sebastian Sura Am 26.02.24 um 11:32 schrieb 'Samuel' via bareos-users: Hi again. So, as expected

Re: [bareos-users] SD Error "Volume previously written"

Could you check if the trace contains  Read device got: ERR= or if you are comfortable with it, you can also send the trace to this email address (sebastian.s...@bareos.com) and i can take a look myself. Kind Regards Sebastian Sura Am 23.02.24 um 15:54 schrieb Leon Bartle: My tapes

Re: [bareos-users] MD5 digest not same File as attributes

I meant to say File 3 has no stream 1, sorry for the confusion! Am 23.02.24 um 13:15 schrieb Sebastian Sura: Hi Samuel thanks for the gathering this info.  Ill look into the bscan issue as well though i think this might be a known issue. Regardless, regarding your actual issue: The bscan

Re: [bareos-users] MD5 digest not same File as attributes

your issue in the copy system test.  Do you do a local copy (so copy to the same sd) or a remote one? Kind Regards Sebastian Sura Am 23.02.24 um 12:56 schrieb 'Samuel' via bareos-users: Hi Sebastian, After looking at the logs some more I noticed that all jobs with this warning have in common

Re: [bareos-users] SD Error "Volume previously written"

ace: BootStrapRecord for reread; block too big for buffer. Writing second EOF failed. Kind Regards Sebastian Sura Am 23.02.24 um 11:28 schrieb Leon Bartle: Log from the message before is the output when viewing "messages". Here is list joblog jobid=176: *list joblog jobid=176  2024-0

Re: [bareos-users] SD Error "Volume previously written"

regards Sebastian Sura Am 22.02.24 um 09:08 schrieb Leon Bartle: (I am unsure of what happened to the last message, but here is a repost) bareos-webui report (see attached) bareos-webui log excerpt  (see attached) Note, that the line I colored yellow only exists in webui and not in the bconsole

Re: [bareos-users] SD Error "Volume previously written"

Can you post the joblog ? The messages that you quoted are not supposed to be errors but just informational messages, it would be very weird if they caused your backup to show up as "with warnings". Kind Regards Sebastian Sura Am 21.02.24 um 08:49 schrieb Leon Bartle: d

Re: [bareos-users] MD5 digest not same File as attributes

Stream=1998 len=80 bscan: stored/bscan.cc:494-0 Record: SessId=1 SessTim=1708427201 FileIndex=2 Stream=40 len=16 This would help us greatly in trying to debug this issue. Kind Regards Sebastian Sura Am 08.02.24 um 15:33 schrieb 'Samuel' via bareos-users: nto the following warning during copy

Re: [bareos-users] VSS ERR=The process cannot access the file because it is being used by another process

They can be found here: https://download.bareos.org/current/ Sincerly Sebastian Sura Am 25.01.24 um 21:20 schrieb 'jo.go...@hosted-power.com' via bareos-users: Where do I find the 23 pre release? I only see version 22 on the link shared earlier? :) On Thursday 25 January 2024 at 09:30:56

Re: [bareos-users] VSS ERR=The process cannot access the file because it is being used by another process

now if you tried that version and the issue still persists! Sincerly Sebastian Sura Am 18.01.24 um 19:53 schrieb Joshua Myles: Interesting. We have a mix of client-initiated and not, and at a glance it looks like the only jobs that ever have warnings ("ERR=The process cannot access t

Re: [bareos-users] VSS ERR=The process cannot access the file because it is being used by another process

the vss name translation does not work for you. I tried reproducing the problem you described with your fileset, but it just works for me. Would it be possible for you to also submit the joblog for that particular job ? You can retrieve it using "list joblog jobid=17062". Sincerely