Re: [Bacula-users] Pool spec in job resource
On 5/3/22 15:46, Chris Wilkinson wrote:
I wonder if someone with more extensive knowledge of Bacula could clarify the
usage of 'pool=' and the optional
'full|differential|incremental backup pool=' directives in the job resource.
The former is required I think whether or not
the latter is given.
Since the latter will override the former, there doesn't seem any reason why
the former should *always* be required?
The reason I ask is that the Bacula module for Webmin shows the upcoming jobs
for the next day. This info also includes the
pool that will be used. Webmin always take the pool from the pool= directive
irrespective of the pool override given.
Regards
Chris Wilkinson
Hello Chris,
As you know, 'Pool' is required in a Job{} resource for the parser to be happy.
Even if it is pulled in via a JobDefs{}
resource, a Pool is required.
The 'full|differential|incremental backup pool=' directives are a great feature
that I like to use all the t
ime - well, we
can discuss the times that they get in the way later... But they are a nice
feature. (cough cough Copy/Migration jobs...)
Here is why:
Let's say you you need to run a spontaneous/manual Full job... And let's say
that the Job{} resource has a 'Pool = Default'
(or Pool = SomeIncPool) set in it because this job normally runs via schedule
where you have Pool and Level overrides in the
Schedule depending on the day...
Well, without the FullBackupPool set, this manual job would use the 'Default'
Pool (or whatever Pool was set to in the job).
If you did not remember to set the `pool=` on the bconsole `run` command line,
or modify the Pool before finally submitting
the Job, the Job would use whatever pool was set in the Job's 'Pool=' setting.
If the FullBackupPool was set in this job, you can be sure that in this example
of a manually overridden level set to Full,
the job would use the correct Full pool automatically, and not write a full job
to a 'defau
lt' pool or other pool. And you
would not need to remember to change the `pool=` (and probably the `storage=`)
before submitting the job to run.
This is also true for the cases when an incremental job gets automatically
upgraded to a Full by Bacula because a Full does
not exist in the catalog, or the MaxFullInterval has passed, causing the same
situation... These types of submitted jobs that
would normally use the "Pool=IncPool" setting to write a Full backup to, would
now, instead *always* use the correct pool for
the level of the job - even when it gets manually or automatically upgraded, or
modified.
I use these settings together with the MaxFullInterval setting so I have no
overrides in my schedules, and Bacula just knows
that after 31 days it is time to run this job as a full, and also knows what
pool (full, Inc, or Diff) to write too.
Well, actually only Inc and Full since my Jobs have 'Level = Incremental' in
them, and when they MaxFullInterval
automatically
upgrades the job to a Full, the correct Full pool is used.
Hope this helps!
Best regards,
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
[Bacula-users] Pool spec in job resource
I wonder if someone with more extensive knowledge of Bacula could clarify the usage of 'pool=' and the optional 'full|differential|incremental backup pool=' directives in the job resource. The former is required I think whether or not the latter is given. Since the latter will override the former, there doesn't seem any reason why the former should *always* be required? The reason I ask is that the Bacula module for Webmin shows the upcoming jobs for the next day. This info also includes the pool that will be used. Webmin always take the pool from the pool= directive irrespective of the pool override given. Regards Chris Wilkinson ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Beta Release 11.3.3
Hello, We are pleased to announce the new BETA release of the next major Bacula version 11.3.3 to both the Bacula website (www.bacula.org) and to SourceForge. Thanks for the valuable feedback. https://www.bacula.org/downloads/Beta-Bacula-11.3.3 This is a beta version of the new 13.0 major release with many new features and a number of changes. Please take care to test this code carefully before putting it into production. Although the new features have been tested, they have not run in a production environment. Compatibility: -- As always, both the Director and Storage daemon(s) must be upgraded at the same time. Any File daemon running on the same machine as a Director or Storage daemon must be of the same version. Older File Daemons should be compatible with the 11.3 Director and Storage daemons. There should be no need to upgrade older File Daemons. New Catalog format in version 11.3.0 and greater This release of Bacula uses a new catalog format. We provide a set of scripts that permit conversion from 9.x and earlier versions to the new 11.3 format (1025). Normally the conversion/upgrade is fast. Keep in mind that there is a big change from 9.x to 11.0 that takes longer than usual, the upgrade process will require about twice the disk space of the actual database. If you start from scratch, you don't need to run the update_bacula_tables script because the create_bacula_tables script automatically creates the new table format. However, if you are using a version of Bacula older than 5.0.0 (e.g. 3.0.3) then you need to run the update_bacula_tables script that will be found in the /src/cats directory after you run the ./configure command. As mentioned above, before running this script, please backup your catalog database, be sure to shutdown Bacula and be aware that running the script can take some time depending on your database size. Thanks for using Bacula! Best Regards, Eric Changelog 11.3.3 - baculum: Fix clearing OAuth2 properties after testing API connection on security page - baculum: Fix directing to default page after log in for users with non-admin roles - baculum: Add to install wizard pre-defined b*json tool paths for FreeBSD and - baculum: Fix #2661 required parameter PHP error on PHP 8.0 - baculum: Fix error calling method_exists() with non-objects on PHP 8 - rpms: Fix org#2633 about log directory not created on Centos7 - Update updatedb scripts - Fix SQLite update script and add upgrade event - cloud: remove useless hash checks - Fix compilation issues - Fix org#2658 About segfault with bsdjson with incorrect parameters - Fix org#2659 Install dbcheck and bsmtp in 755 New Features: - Job Storage group support - Kubernetes Plugin - New Accurate Option to Save Only File's Metadata - Windows CSV (Cluster Shared Volumes) support - Adding more logging for daemon<->daemon connection in job output - Tag support on catalog objects - Support for SHA256 and SHA512 signatures in FileSet - External LDAP Console Authentication Misc Features: - Windows Installer Silent Mode options - Add PriorJob to llist job output - Check for IP SANs when verifying TLS certs - Clarify SD vbackup device error message - Add bconsole .jlist command to get JSON output from regular list command - Ensure that the DIR will reject catalog update from the FD - Add variable for PreviousJobId in mail messages - Respect the 'nodump' flag in more OSes than just BSD - Add debug/trace/tags information to .status header - Handle lin_tape end of device with the new 'Use Lintape=yes' Device directive - Add MaximumJobErrorCount FileDaemon directive - bsmtp: Add the possibility to add emails separated with a comma as recipient list - SDPacketCheck FileDaemon used to control the network flow - Add .bvfs_ls_all_files command Main Fixes: - The presence of FileSet and Pool directives in the Job. Bug #2188 - Fix Director crash for client intiated backup - Fix Director crash for Migration job - Fix incorrect ouput for the .status client command - Skip XATTR larger than MaximumNetworkBuffer - Fix deadlock when starting the Director with a missconfigured catalog - Fix BAT tool crashing the Director - Fix org#2627 About DIR crashing for copy jobs and resource rename - Move the delete volume event just before the actual deletion - Fix mail variables not working after a conf reload - Fix OpenBSD chio-changer script fix - Fix SQL query generated with ACLs - Fix heartbeat segfault when the job is terminated very quickly - Fix About wrong backup client displayed to the user when the original client doesn't exist - Fix org#2605 About incorrect message in restore command - cdp: open the inotify stream using the CLOEXEC (close on exec) flag - docker: Check the presence of the docker
Re: [Bacula-users] Bacula Debian systemd services problem
I built v9.7 for 64 bit Raspbian. Using --with-systemd in ./configure
installed the unit files ok. There was a thread in the list on this last
month.
Regards
Chris Wilkinson
On Tue, 3 May 2022, 12:09 pm Wanderlei Huttel,
wrote:
>
> Hello guys
>
> I would like to know why when I compile Bacula source code, it doesn't
> install Debian systemd services?
>
> I always use the commands
> make -j 8
> make install
> make install-autostart
>
> I know there is a directory in source code "src/platforms/systemd", that
> has the systemd services, but when I
> try to enable it looks it gets the /etc/init.d files.
>
> root@bacsys:/usr/src/bacula/bacula/platforms/debian# systemctl status
> bacula-dir
> ● bacula-dir.service - LSB: Start Bacula Director daemon at boot time
> Loaded: loaded (/etc/init.d/bacula-dir; generated)
> Active: inactive (dead)
>Docs: man:systemd-sysv-generator(8)
>
>
>
> =
> # Trying to enable bacula services systemd
> root@bacula:~# systemctl enable {bacula-fd,bacula-dir,bacula-sd}
> bacula-fd.service is not a native service, redirecting to
> systemd-sysv-install.
> Executing: /lib/systemd/systemd-sysv-install enable bacula-fd
> bacula-dir.service is not a native service, redirecting to
> systemd-sysv-install.
> Executing: /lib/systemd/systemd-sysv-install enable bacula-dir
> bacula-sd.service is not a native service, redirecting to
> systemd-sysv-install.
> Executing: /lib/systemd/systemd-sysv-install enable bacula-sd
>
>
> =
> # Bacula source code platforms/systemd
> root@bacula:/usr/src/bacula/platforms/systemd#
> total 40K
> -rw-r--r-- 1 root root 77 mai 2 14:09 bacula.conf
> -rw-r--r-- 1 root root 66 abr 27 15:05 bacula.conf.in
> -rw-r--r-- 1 root root 930 mai 2 14:09 bacula-dir.service
> -rw-r--r-- 1 root root 948 abr 27 15:05 bacula-dir.service.in
> -rw-r--r-- 1 root root 785 mai 2 14:09 bacula-fd.service
> -rw-r--r-- 1 root root 800 abr 27 15:05 bacula-fd.service.in
> -rw-r--r-- 1 root root 979 mai 2 14:09 bacula-sd.service
> -rw-r--r-- 1 root root 988 mai 2 13:22 bacula-sd.service.in
> -rw-r--r-- 1 root root 3,8K mai 2 14:09 Makefile
> -rw-r--r-- 1 root root 3,8K abr 27 15:05 Makefile.in
>
>
> =
> If I only inform the option "--with-systemd" in my ./configure,
> in config.out get the path /lib/systemd/system
>
> ./configure \
> --enable-smartalloc \
> --with-postgresql \
> --with-db-user=bacula \
> --with-db-password=bacula \
> --with-db-port=5432 \
> --with-openssl \
> --with-readline=/usr/include/readline \
> --sysconfdir=/etc/bacula \
> --bindir=/usr/bin \
> --sbindir=/usr/sbin \
> --with-scriptdir=/etc/bacula/scripts \
> --with-plugindir=/etc/bacula/plugins \
> --with-pid-dir=/var/run \
> --with-subsys-dir=/etc/bacula/working \
> --with-working-dir=/etc/bacula/working \
> --with-bsrdir=/etc/bacula/bootstrap \
> --with-s3=/usr/local \
> --with-basename=bacula \
> --with-hostname=192.168.1.1 \
> --with-systemd
> --disable-conio \
> --disable-nls \
> --with-logdir=/var/log/bacula \
> --with-dump-email=em...@domain.com \
> --with-job-email=em...@domain.com
>
>
>
> =
> Configuration on Mon May 2 14:09:36 -03 2022:
>
>Host: x86_64-pc-linux-gnu -- debian 11.3
>Bacula version:Bacula 11.3.2 (24 March 2022)
>Source code location: .
>Install binaries: /usr/sbin
>Install libraries: /usr/lib
>Install config files: /etc/bacula
>Scripts directory: /etc/bacula/scripts
>Archive directory: /tmp
>Working directory: /etc/bacula/working
>PID directory: /etc/bacula/working
>Subsys directory: /etc/bacula/working
>Man directory: /usr/share/man
>Data directory:/usr/share
>Plugin directory: /etc/bacula/plugins
>C Compiler:gcc 10.2.1-6)
>C++ Compiler: /usr/bin/g++ 10.2.1-6)
>Compiler flags: -g -O2 -Wall -x c++ -fno-strict-aliasing
> -fno-exceptions -fno-rtti
>Linker flags:
>Libraries: -lpthread -ldl -ldl
>Statically Linked Tools: no
>Statically Linked FD: no
>Statically Linked SD: no
>Statically Linked DIR: no
>Statically Linked CONS:no
>Database backends: PostgreSQL
>Database port: 5432
>Database name: bacula
>Database user: bacula
>Database SSL options:
>
>Job Output Email: em...@domain.com
>Traceback Email: em...@domain.com
>SMTP Host Address: localhost
>
>Dir
Re: [Bacula-users] About bacula-dir.conmsg
Hey guy, thanks to supply me... it's helped a lot! De: Bill Arlofski via Bacula-users Enviado: segunda-feira, 2 de maio de 2022 12:36 Para: bacula-users@lists.sourceforge.net Assunto: Re: [Bacula-users] About bacula-dir.conmsg On 5/2/22 07:54, Guilherme Santos wrote: > Hey guys, what's up? > > Could someone tell me more about bacula-dir.conmsg? Mine is about 21G... > Why this archive has this size? > Thanks!! That file is the on-disk bconsole buffer of console messages. You can do one of either: 1. Type 'messages' in a bconsole session and watch 21GB of log files scroll by (not recommended lol) 2. Stop the Director, and delete the file, then restart the Director. Hope this helps! 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] Bacula Debian systemd services problem
Hello guys
I would like to know why when I compile Bacula source code, it doesn't
install Debian systemd services?
I always use the commands
make -j 8
make install
make install-autostart
I know there is a directory in source code "src/platforms/systemd", that
has the systemd services, but when I
try to enable it looks it gets the /etc/init.d files.
root@bacsys:/usr/src/bacula/bacula/platforms/debian# systemctl status
bacula-dir
● bacula-dir.service - LSB: Start Bacula Director daemon at boot time
Loaded: loaded (/etc/init.d/bacula-dir; generated)
Active: inactive (dead)
Docs: man:systemd-sysv-generator(8)
=
# Trying to enable bacula services systemd
root@bacula:~# systemctl enable {bacula-fd,bacula-dir,bacula-sd}
bacula-fd.service is not a native service, redirecting to
systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable bacula-fd
bacula-dir.service is not a native service, redirecting to
systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable bacula-dir
bacula-sd.service is not a native service, redirecting to
systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable bacula-sd
=
# Bacula source code platforms/systemd
root@bacula:/usr/src/bacula/platforms/systemd#
total 40K
-rw-r--r-- 1 root root 77 mai 2 14:09 bacula.conf
-rw-r--r-- 1 root root 66 abr 27 15:05 bacula.conf.in
-rw-r--r-- 1 root root 930 mai 2 14:09 bacula-dir.service
-rw-r--r-- 1 root root 948 abr 27 15:05 bacula-dir.service.in
-rw-r--r-- 1 root root 785 mai 2 14:09 bacula-fd.service
-rw-r--r-- 1 root root 800 abr 27 15:05 bacula-fd.service.in
-rw-r--r-- 1 root root 979 mai 2 14:09 bacula-sd.service
-rw-r--r-- 1 root root 988 mai 2 13:22 bacula-sd.service.in
-rw-r--r-- 1 root root 3,8K mai 2 14:09 Makefile
-rw-r--r-- 1 root root 3,8K abr 27 15:05 Makefile.in
=
If I only inform the option "--with-systemd" in my ./configure,
in config.out get the path /lib/systemd/system
./configure \
--enable-smartalloc \
--with-postgresql \
--with-db-user=bacula \
--with-db-password=bacula \
--with-db-port=5432 \
--with-openssl \
--with-readline=/usr/include/readline \
--sysconfdir=/etc/bacula \
--bindir=/usr/bin \
--sbindir=/usr/sbin \
--with-scriptdir=/etc/bacula/scripts \
--with-plugindir=/etc/bacula/plugins \
--with-pid-dir=/var/run \
--with-subsys-dir=/etc/bacula/working \
--with-working-dir=/etc/bacula/working \
--with-bsrdir=/etc/bacula/bootstrap \
--with-s3=/usr/local \
--with-basename=bacula \
--with-hostname=192.168.1.1 \
--with-systemd
--disable-conio \
--disable-nls \
--with-logdir=/var/log/bacula \
--with-dump-email=em...@domain.com \
--with-job-email=em...@domain.com
=
Configuration on Mon May 2 14:09:36 -03 2022:
Host: x86_64-pc-linux-gnu -- debian 11.3
Bacula version:Bacula 11.3.2 (24 March 2022)
Source code location: .
Install binaries: /usr/sbin
Install libraries: /usr/lib
Install config files: /etc/bacula
Scripts directory: /etc/bacula/scripts
Archive directory: /tmp
Working directory: /etc/bacula/working
PID directory: /etc/bacula/working
Subsys directory: /etc/bacula/working
Man directory: /usr/share/man
Data directory:/usr/share
Plugin directory: /etc/bacula/plugins
C Compiler:gcc 10.2.1-6)
C++ Compiler: /usr/bin/g++ 10.2.1-6)
Compiler flags: -g -O2 -Wall -x c++ -fno-strict-aliasing
-fno-exceptions -fno-rtti
Linker flags:
Libraries: -lpthread -ldl -ldl
Statically Linked Tools: no
Statically Linked FD: no
Statically Linked SD: no
Statically Linked DIR: no
Statically Linked CONS:no
Database backends: PostgreSQL
Database port: 5432
Database name: bacula
Database user: bacula
Database SSL options:
Job Output Email: em...@domain.com
Traceback Email: em...@domain.com
SMTP Host Address: localhost
Director Port: 9101
File daemon Port: 9102
Storage daemon Port: 9103
Director User:
Director Group:
Storage Daemon User:
Storage DaemonGroup:
File Daemon User:
File Daemon Group:
Large file support:yes
Bacula conio support: no -lreadline -lhistory -ltinfo
readline support: yes
TCP Wrappers support: no
TLS support: yes
Encryption support:yes
ZLIB su
