Re: [Bacula-users] Again LTO9 and performances...
On 6/20/24 8:58 AM, Marco Gaiarin wrote: But, now, a question: this mean that in spool data get interleaved too? How they are interleaved? File by file? Block by block? What block size? No. When you have jobs running, take a look into the SpoolDirectory. You will see a 'data' *.spool file and an 'attr' *.sppol file for each job running. Once that is hit, the spoofles are written to tape, during which active jobs have to wait because the spool is full. There's no way to 'violate' this behaviour, right?! A single SD process cannot spool and despool at the same time? An SD can be spooling multiple jobs wile *one* and only one Job spool file is despooling to one drive. Add another drive and and the same is still true, but the SD can now be despooling two jobs at the same time while other jobs are spooling, and so on as you add drives. Hope this helps, Bill -- Bill Arlofski w...@protonmail.com signature.asc Description: OpenPGP digital signature ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] LTO-8 tape report error
On 6/20/24 4:54 AM, Adam Weremczuk wrote: OMG... The only reason the script started failing was a different device assignment caused by a reboot: ls -al /dev | grep sg. crw-rw 1 root tape 21, 0 Jun 19 12:25 sg0 crw-rw 1 root disk 21, 1 Jun 12 17:42 sg1 Once I've changed sg1 to sg0 it started working like a charm again :) Hello Adam, I am glad you found it. It should have been the first thing I recommended to check. 路臘 You might be interested in my `mtx-changer-python.py` drop-in replacement for the `mtx-changer` script and/or my `bacula-tapealert.py` drop-in replacement for the `tapealert` script that Bacula ships with. Both determine the /dev/sg# node automatically, on-the-fly, preventing this issue with Bacula when a /dev/sg# node changes after a reboot. The `bacula-tapealert.py` currently requires the Python `doctopt` module but I will swap that out and replace it with `argparse` shortly. I have already done this for the `mtx-changer-python.py` and a couple other scripts. Hope this helps, Bill -- Bill Arlofski w...@protonmail.com signature.asc Description: OpenPGP digital signature ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] LTO-8 tape report error
Mandi! Adam Weremczuk In chel di` si favelave... > Any idea what's going on? Consider that there are vendor utility to do quick and extensive tape unit check; for HP unit, for example, there's LTT: https://buy.hpe.com/it/it/storage/storage-software/storage-device-management-software/storeever-tape-device-management-software/hpe-library-e-tape-tools/p/406729 -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Limit job rescheduling
Mandi! Andrea Venturoli In chel di` si favelave... > At a site, I'm backing up several machines, most of which are clients > that are not powered on every day. Ciao Andrea. I use roughly the same schedule: Allow Duplicate Jobs = no Cancel Lower Level Duplicates = yes Reschedule On Error = yes Reschedule Interval = 30 minutes Reschedule Times = 8 Max Run Sched Time = 8 hours and effectively jobs, starting at the same time, tent to 'clog' the director (but i run that when i've no 'main' backup job, and i set 'Max Run Sched Time = 8 hours' to prevent conflicts). Also, i've noted that for client on dynamic IP, timout are longer: eg bacula fail immediately if client are not reachable, but fail more slowly if client does not exist in DNS. So i've moved most client on static ip. -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Again LTO9 and performances...
Mandi! Gary R. Schmidt In chel di` si favelave... >> job involved (in the same pool, i think) start to write down spool to tape. > MaximumSpoolSize is the total space used in the spool area, by all jobs. After posting, i've looked more carefully at the log and understod that. Sorry for the misunderstanding. This als make sense, because 'MaximumSpoolSize' is an SD parameters, and so cannot be 'job dependant'... But, now, a question: this mean that in spool data get interleaved too? How they are interleaved? File by file? Block by block? What block size? What defined in 'Maximum File Size'? Seems not to me... > Once that is hit, the spoofles are written to tape, during which active > jobs have to wait because the spool is full. There's no way to 'violate' this behaviour, right?! A single SD process cannot spool and despool at the same time? This seems a bit strange to me... Thanks. -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] volumes, pools, media types and labels
Hello, śr., 19 cze 2024 o 14:28 Stefan G. Weichinger napisał(a): > Am 19.06.24 um 09:46 schrieb Radosław Korzeniewski: > > > Did you label your tapes? You can't use tapes in Bacula without labeling. > > Sure I did! > > Great! So what job logs say about a volume selection when it selects "a wrong volume"? Your configuration seems to be fine, but what Bacula says about your configuration - check bconsole command show job=... Did you reload your configuration after any change? > > When you label your tapes, just use "barcodes" options and Bacula will > > read all barcodes from tapes and label them to match. > > Then you should put all your new tapes in the Scratch pool during > > labeling, so Bacula can take one to the selected pool when required. > > That's new to me. Is it relevant for my current issue? > I want it to use existing volumes, not new ones. > Are your volumes labeled correctly? > > Pool "daily" should not create a "Vol-" volume in the "File" storage ... > it shouldn't use "File" at all. > > Yes, if you configured it as described. I never had such a mistake in Bacula when correctly configured, but I've seen this kind of mistake when incorrectly configured. > > Finally you should configure the "Recycle" pool parameter pointing to > > the Scratch pool, so all your unused tapes will return to it, closing > > the cycle. > > When carefully configured it will automatically rotate all your tapes, > > which is good for them. > > > > I hope it helps > > phew, sounds even more complicated to me right now > As you wish. A default Bacula configuration which comes with a default installation is the best suited for disk based backups and this is what you call "clever defaults or automatisms" as it works perfectly from the start. It is not meant to be used "as-is" for tape backups and needs more customizations. best regards -- Radosław Korzeniewski rados...@korzeniewski.net ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] volumes, pools, media types and labels
Am 20.06.24 um 17:32 schrieb Radosław Korzeniewski: Great! So what job logs say about a volume selection when it selects "a wrong volume"? Well, it looks for a volume named "Vol-xxx" in the tape loader, which is wrong. Your configuration seems to be fine, but what Bacula says about your configuration - check bconsole command show job=... Did you reload your configuration after any change? I restarted the daemons now and then, if that's the same. Are your volumes labeled correctly? I think so. That one "ghost volume" is created by Bacula somehow. Pool "daily" should not create a "Vol-" volume in the "File" storage ... it shouldn't use "File" at all. Yes, if you configured it as described. I never had such a mistake in Bacula when correctly configured, but I've seen this kind of mistake when incorrectly configured. Well, that's why I posted the config lines ;-) I agree and know that something is incorrectly configured. The question is: what? > Finally you should configure the "Recycle" pool parameter pointing to > the Scratch pool, so all your unused tapes will return to it, closing > the cycle. > When carefully configured it will automatically rotate all your tapes, > which is good for them. > > I hope it helps phew, sounds even more complicated to me right now As you wish. A default Bacula configuration which comes with a default installation is the best suited for disk based backups and this is what you call "clever defaults or automatisms" as it works perfectly from the start. It is not meant to be used "as-is" for tape backups and needs more customizations. I appreciate your help and I am ready to learn. If I have to adjust things for using tapes: ok ... Basically I could also get rid of the whole storage "File" including the volumes. It was temporary only, the main goal is to write backups to physical tapes. But I take this as a "challenge" to learn more about the mechanisms of Bacula. (if I get migrate-jobs from File to Tape working without losing any data, that might be even better ... then remove storage "File" after doing so) thanks, Stefan ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] LTO-8 tape report error
On 17/06/2024 18:50, Bill Arlofski via Bacula-users wrote: Hello Adam, Not sure if this will be any help at all, but I just checked and see that in my `mtx-changer-python.py` drop-in replacement script, to check for tape cleaning required messages, I am using: 8< sg_logs --page=0xc /dev/sg## 8< Then I look for: 8< Cleaning action not required (or completed) or Cleaning action required 8< To determine if I need to automatically find and load a cleaning tape before returning contr ol to the SD... I had been using `tapealert` instead of sg_logs, but I found that tapeinfo clears all alert messages on the drive, so they could never be caught by the SD when it calls tapeinfo in the tapealert script. Sg_logs just reports what I need without clearing the other flags that the SD needs to know when a drive or tape is bad/damaged, etc. Best regards, Bill ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users OMG... The only reason the script started failing was a different device assignment caused by a reboot: ls -al /dev | grep sg. crw-rw 1 root tape 21, 0 Jun 19 12:25 sg0 crw-rw 1 root disk 21, 1 Jun 12 17:42 sg1 Once I've changed sg1 to sg0 it started working like a charm again :) ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
