Re: [Bacula-users] Volume issues with 11.0.6 running in docker
Hello Daniel, You should have a look at the NFS server logs. Looks like the volumes files are getting corrupted. There is the SyncOnClose device directive that may help in these cases where volumes are stored in nfs. Best, Ana El lun., 7 ago. 2023 18:59, Daniel Rich via Bacula-users < bacula-users@lists.sourceforge.net> escribió: > I recently migrated my bacula director and storage daemon to version 11 > and am running them in docker. Ever since, I have started getting > occasional volume errors that can only be resolved by restarting the > bacula-sd container or in some cases deleting and relabeling a volume. > Thinks will run fine for a week or two (or more) and then start throwing > errors. Has anyone else seen anything like this? > > These volumes are file volumes that live on my Synology and are mounted > over NFS. > > Here’s a example of what I’m seeing: > 07-Aug 06:10 morpheus-dir JobId 3671: shell command: run BeforeJob > "/opt/bacula/etc/scripts/make_catalog_backup.pl MyCatalog" > 07-Aug 06:11 morpheus-dir JobId 3671: Start Backup JobId 3671, > Job=BackupCatalog.2023-08-07_06.10.00_18 > 07-Aug 06:11 morpheus-dir JobId 3671: Using Device "vDrive-03" to write. > 07-Aug 06:11 morpheus-sd JobId 3671: Fatal error: block_util.c:478 Volume > data error at 0:0! Wanted ID: "BB02", got "". Buffer discarded. > 07-Aug 06:11 morpheus-fd JobId 3671: Fatal error: job.c:3012 Bad response > from SD to Append Data command. Wanted 3000 OK data > , got len=257 msg="3903 Error append data: Read label block failed: > requested Volume "morpheus-0076" on File device "vDrive-03" (/srv/backup) > is not a Bacula labeled Volume, because: ERR=block_util.c:478 Volume data > error at 0:0! Wanted ID: "BB02", got "". Buffer discarded." > 07-Aug 06:11 morpheus-dir JobId 3671: Error: Bacula morpheus-dir 11.0.6 > (10Mar22): > Build OS: x86_64-redhat-linux-gnu-bacula redhat (Core) > JobId: 3671 > Job: BackupCatalog.2023-08-07_06.10.00_18 > Backup Level: Full > Client: "morpheus-fd" 9.6.7 (10Dec20) x86_64-pc-linux-gnu,ubuntu,20.04 > FileSet: "Catalog" 2022-08-07 06:10:00 > Pool: "morpheus" (From Job resource) > Catalog: "MyCatalog" (From Client resource) > Storage: "File" (From Job resource) > Scheduled time: 07-Aug-2023 06:10:00 > Start time: 07-Aug-2023 06:11:39 > End time: 07-Aug-2023 06:11:40 > Elapsed time: 1 sec > Priority: 10 > FD Files Written: 0 > SD Files Written: 0 > FD Bytes Written: 0 (0 B) > SD Bytes Written: 0 (0 B) > Rate: 0.0 KB/s > Software Compression: None > Comm Line Compression: None > Snapshot/VSS: no > Encryption: no > Accurate: no > Volume name(s): > Volume Session Id: 72 > Volume Session Time: 1690744006 > Last Volume Bytes: 1 (1 B) > Non-fatal FD errors: 1 > SD Errors: 1 > FD termination status: Error > SD termination status: Error > Termination: *** Backup Error *** > > Dan Rich | http://www.employees.org/~drich/ >| "Step up to red alert!" "Are you sure, > sir? >| It means changing the bulb in the > sign..." >| - Red Dwarf (BBC) > ___ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users > ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] New `mtx-changer-python` Github repository is now public
Great job Bill! Thank you! El jue., 24 ago. 2023 1:33, Bill Arlofski via Bacula-users < bacula-users@lists.sourceforge.net> escribió: > Hello everyone, > > Several months ago, I asked on this list if anyone who was using Solaris > with a tape library in Bacula and was interested in > testing a new mtx-changer script which I was writing as a drop-in > replacement - with additional features - in Python: > 8< > Subject: [Bacula-users] Anyone using Solaris as a Bacula SD with a > tape library? > Link to topic: https://marc.info/?l=bacula-users=168617696107454=2 > 8< > > A big thank you to the people who responded - both Solaris users and other > OS users! > > I am happy to report that this new mtx-changer-python.py script is already > running in a few production environments. > > At this point, I feel like I have gotten as far as I can by myself and > have decided that it would be best to release it to > the public so that it can have more eyes on it and so that contributions > can be made to fix bugs, add features, or just help > make the code more "Pythonic" and just better overall. > > > General Features Summary: > -- > --- > - Works with Community and Enterprise Bacula versions > - Drop-in replacement for the default bash/perl `mtx-changer` script* > - Easily support multiple tape libraries managed by the same SD* > - Clear, easy to understand logging (if enabled) > - Several levels of logging verbosity > - Multiple libraries may be logged to the same log file with their name in > each log line, or they may be each logged to their > own separate log file. > - Fully supports Linux and FreeBSD > > > New Automatic Tape Drive Cleaning Features:** > --- > - If enabled, can check if a tape drive is signalling that it needs to be > cleaned > - If enabled, can load and unload a cleaning tape when a drive signals it > needs to be cleaned > - Currently, a pseudo-random cleaning tape is selected to be loaded when > needed*** > > > NOTES: > -- > * Can literally be used out-of-the-box to replace the standard mtx-changer > script in your Autochangers' "ChangerCommand =" > set > ting. > > * Comes with a example "INI file" configuration file. There is a global > [DEFAULT] section, and additional sections may be > added to override the [DEFAULT] setting and to allow one SD to support > more than one library using this script. > > ** Tape drive cleaning not supported on all OSes yet! This is where some > (a lot? :) of community assistance will be required > to add proper support for some of the BSDs, and possibly other Unixes. > > *** There are already ideas to keep track of cleaning tapes' usage and > possibly use a round-robin selection method rather > than the pseudo-random one as it currently is written. Thank you Arno > Lehmann for our discussions and your input about this > feature and the script in general - especially at the beginning stages. > > > Next Steps: > --- > - The Github repository is here: https://github.com/waa/mtx-changer-python > - Feel free to download the script and the example configuration file, or > just clone the repository > - Opening issues and/ > or code commits is welcome in the Github repository > > > Thank you in advance for any and all assistance! > > Best regards, > Bill > > -- > Bill Arlofski > w...@protonmail.com > ___ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users > ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula recycling volumes it should not recycle
Hello Andrea,
You have 1 job per volume and automatic pruning and recycling enabled. If
the only job in the volume is deleted from the Catalog, the recycling
algorithm will detect it and the volume will be marked as Purged and
reused. Is it happening with all volumes or only a few cases? Are you
manually deleting jobs from the Catalog?
Best,
Ana
El sáb., 2 sept. 2023 17:04, Andrea Venturoli escribió:
> On 9/2/23 12:30, Andrea Venturoli wrote:
> > Hello.
> >
> > I've been using bacula for a long long time, but I can't seem to
> > understand why, in a specific installation, volumes are recycled before
> > I think they should.
> > The only difference from several other installation, is the use of S3
> > cloud plugin.
> >
> > So:
> >
> > _ Bacula version is 11.0.6;
> >
> > _ excerpts from bacula-dir.conf:
> >> Client {
> >> Name=...
> >> Address=...
> >> FDPort = 9102
> >> Catalog = MyCatalog
> >> Password="..."
> >> File Retention=3 months
> >> Job Retention=3 months
> >> AutoPrune = yes
> >> }
> >> Pool {
> >> Name = Full
> >> Pool Type = Backup
> >> Recycle = yes
> >> AutoPrune = yes
> >> Maximum Volume Bytes = 50G
> >> Maximum Volume Jobs=1
> >> Label Format = "Full"
> >> Volume Retention=3 months
> >> Cache retention=31 days
> >> Action On Purge=Truncate
> >> }
> >
> > _ from the DB:
> >> select volumename,volretention/60/60/24 from media where volumename
> >> like 'Full%';
> >> volumename | ?column? +--
> >> Full0021 | 90
> >> Full0025 | 90
> >> Full0026 | 90
> >> Full0117 | 90
> >> Full0112 | 90
> >> Full0152 | 90
> >> Full0111 | 90
> >> Full0116 | 90
> >
> > _ yesterday I had:
> >> ls -lt|grep Full
> >> drwxr- 2 bacula bacula 512 Aug 30 22:45 Full0111
> >> drwxr- 2 bacula bacula 25600 Aug 8 22:45 Full0026
> >> drwxr- 2 bacula bacula 512 Aug 7 22:45 Full0025
> >> drwxr- 2 bacula bacula 21504 Aug 4 23:53 Full0116
> >> drwxr- 2 bacula bacula 512 Aug 4 22:33 Full0112
> >> drwxr- 2 bacula bacula 512 Jul 9 22:45 Full0021
> >> drwxr- 2 bacula bacula 25088 Jul 4 22:45 Full0152
> >> drwxr- 2 bacula bacula 512 Jul 3 22:45 Full0117
> >
> > _ today the volumes from July were recycled:
> >> ls -lt | grep Full
> >> drwxr- 2 bacula bacula 21504 Sep 1 23:55 Full0152
> >> drwxr- 2 bacula bacula 512 Sep 1 22:33 Full0117
> >> drwxr- 2 bacula bacula 512 Aug 30 22:45 Full0111
> >> drwxr- 2 bacula bacula 25600 Aug 8 22:45 Full0026
> >> drwxr- 2 bacula bacula 512 Aug 7 22:45 Full0025
> >> drwxr- 2 bacula bacula 21504 Aug 4 23:53 Full0116
> >> drwxr- 2 bacula bacula 512 Aug 4 22:33 Full0112
> >> drwxr- 2 bacula bacula 512 Jul 9 22:45 Full0021
> >
> >
> > Any idea why this happens?
>
> P.S.
> In the last job's mail I see:
> > There are no more Jobs associated with Volume "Full0117". Marking it
> purged.
>
> So it seems job retention is the problem, not volume retention.
>
>
>
> ___
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
>
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
