Re: [Bacula-users] Verify Jobs not pruning cache when using S3 storage

[Eric Bollengier via Bacula-users]

Hello Martin,

On 6/19/24 12:57, Martin Reissner wrote:

Hello,

we're running a Bacula 15.0.2 setup which stores everything in S3 storage and 
due to having a lot of data to backup every day

we use

   Truncate Cache = AfterUpload
   Upload = EachPart

in our "Cloud" ressources, to ensure the systems running the SDs do not run out 
of diskspace. This works pretty well but I recently

started to configure Verifyjobs with

   Level = VolumeToCatalog

for some important jobs and it looks like when running the Verifyjob, data gets 
transferred from S3 to the directory specified
as "Archive Device" in the "Device" ressource, sometimes also known as 
"cloudcache" and is then compared to the respective data in the catalog.
So far so good, but it seems that even after a successful verification the 
volume data remains there, probably until the volume is reused and for

large jobs this takes up quite some space which causes diskspace issues on the 
SD.

Am I maybe missing something there and is there some option that can be used to 
prune the cache after a (successful) verifyjob?


Yes, you have a cloud command to prune the cache, I suggest to run it at a
regular interval inside an admin job for example. (cloud prune allpools 
storage=XXX)

Hope it helps!

Best Regards,
Eric



___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] After configure, make command error fails to install Bacula-Community

[Eric Bollengier via Bacula-users]

Hello James,

On 5/3/24 22:57, James Israel via Bacula-users wrote:

I am trying to configure bacula-15.0.2 (from the bacula-15.0.2.tar.gz file 
found at https://www.bacula.org/source-download-center, the “Download Bacula 
Community” link), and after many installs of software that was needed for the 
configure to work, the make script is stalling out at:

make[1]: Entering directory '/tmp/bacula-15.0.2/src/filed'
Compiling restore.c
restore.c: In function ‘bool decompress_data(JCR*, int32_t, char**, 
u_int32_t*)’:
restore.c:1387:13: error: ‘compress_len’ was not declared in this scope; did 
you mean ‘comp_len’?
  1387 | compress_len = jcr->compress_buf_size;
   | ^~~~
   | comp_len
restore.c:1388:13: error: ‘cbuf’ was not declared in this scope
  1388 | cbuf = (const unsigned char*)*data + 
sizeof(comp_stream_header);
   | ^~~~
restore.c:1389:13: error: ‘real_compress_len’ was not declared in this scope
  1389 | real_compress_len = *length - sizeof(comp_stream_header);
   | ^
make[1]: *** [Makefile:189: restore.o] Error 1

Something about the function isn’t working, but I can’t figure out how to fix 
it. It is saying some things were “not declared in this scope”, how to declare 
them? (compress_len, cbuf, real_compress_len)


This is a problem that I'm going to fix, but I believe that something like gzip
is not installed. I would recommend to install them in order to use the
compression feature.


Is something more needed in the configure operation? I configured with a script 
that included:


Look the output of the configure, you might see if gzip is detected properly.

Best Regards,
Eric



CFLAGS="-g -Wall" \
   ./configure \
   --sbindir=/opt/bacula/bin \
   --sysconfdir=/etc/bacula \
   --enable-smartalloc \
   --enable-conio \
   --enable-bat \
   --with-postgresql \
   --with-working-dir=/opt/bacula/working \
   --with-scriptdir=/etc/bacula/scripts \
   --with-plugindir=/etc/bacula/plugins \
   --with-pid-dir=/var/run \
   --with-subsys-dir=/var/run \
   --with-dump-email=em...@humortimes.com \
   --with-job-email=em...@humortimes.com \
   --with-smtp-host=mail.humortimes.com \
   --with-aws \
   --with-baseport=9101

James Israel




___
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] Version of openssl supported (bacula with postgresql)

[Eric Bollengier via Bacula-users]

Hello Eduardo,

On 4/8/24 09:57, Eduardo Rothe via Bacula-users wrote:

While installing bacula-postgresql in fedora39 (package downloaded from the 
bacula repositories) I am getting the following messages:


- nothing provides libcrypto.so.10()(64bit) needed by 
bacula-postgresql-15.0.2-24032211.el7.x86_64 from Bacula-Community> - nothing 
provides libssl.so.10()(64bit) needed by 
bacula-postgresql-15.0.2-24032211.el7.x86_64 from Bacula-Community

I believe this is because bacula requires an older version of openssl. What is 
the latest version of openssl supported by bacula ? Can I infer openssl-1.0.* ?
A very nice beginning of week to all
Eduardo
bacula 15.0.2
postgresql 15.6
openssl 3.1.1fedora 39



I would not try to install Centos7 packages to a Fedora system, it's two
different things. In this case, you can take the Fedora version if it's
recent (it should), or compile it yourself, the recent OpenSSL should be
ok with some warnings about their constant need of breaking their API.

Hope it helps!

Best Regards,
Eric



___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Mistakenly erased label headers from LTO with btape test / need help to salvage content

[Eric Bollengier via Bacula-users]

Hello Yohann,

On 3/25/24 16:11, Dedy Yohann wrote:

Dear bacula community,
I made a mistake today while making maintenance tasks.

I unintentionaly ran the "btape test" command on a LTO cartidge that was 
already labeled and assigned to our main backup pool.

When I realized data was written on the tape after a couple of seconds, I 
stopped the operation (ctrl-c) in panic...
Unfortunately the evil was already done, now when I try to restore data from 
this volume, the cartidge is correctly loaded in the drive (barcode checked by 
the autochanger) but I get this error once data is read from the tape :

bacula-sd JobId 425: Warning: acquire.c:279 Read acquire: Could not unserialize 
Volume label: ERR=label.c:987 Expecting Volume Label, got FI=0 Stream=0 
len=64412

Is there a way to manually restore the content of the tape or force the 
relabelling of the tape without erasing the content of the cartidge?


I'm afraid that your tape is lost. Usually when you write at the start of the
tape, the old data is no longer accessible.

If the data is really important, I know that some companies have special
tape drives with a home made firmware that can bypass the EOF marker and
get your data back, but they are not cheap.

Good luck,
Best Regards,
Eric



___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

[Bacula-users] Bacula Release 15.0.2

[Eric Bollengier via Bacula-users]

Hello,

We are pleased to announce the release of Bacula version 15.0.2 to both the 
Bacula website (www.bacula.org) and to SourceForge release.


This release brings a lot of new features and plugins. More detailed information
about the changes is available on
https://www.bacula.org/15.0.x-manuals/en/main/New_Features_in_15_0_0.html

Binaries for Windows, Redhat 7,8,9 (and compatible systems), Debian 11/12 and
Ubuntu 20/22 LTS are available on Bacula.org.

This release contains more than 1000 commits, big thanks to all the
contributors and specially Bacula Systems for their support!

Thank you for using Bacula.
Eric

---

This is a 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 15.0 Director and Storage
daemons. There should be no need to upgrade older File Daemons.

In 15.0, we have upgraded the volume format from BB02 to BB03 to support
options such as the Volume encryption. Old volumes can still be used by the
15.0 Storage Daemon, however, new 15.0 BB03 volumes cannot be used by old
Storage Daemons.

New Catalog format in version 15.0.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 15.0 format
(1026).  Normally the conversion/upgrade is automatic, though 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.

The database upgrade introduced in 11.0 should significantly increase
performance when inserting a large number of Jobs with a lot of Files into the
database catalog.

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 and the
grant_bacula_privileges scripts 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.


Release 15.0.2 / 21 March 2024


Security:
 - Director TOTP Console authentication plugin
 - Better restricted console support
 - Add Storage Daemon Volume encryption support
 - Add support for Immutable filesystem flag for volumes
 - Add support for Append Only filesystem flag for volumes
 - Clamav Antivirus plugin
 - Malware detection code (via Abuse.ch)
 - Add AllowedBackupDirectories FileDaemon's directive
 - Add AllowedScriptDirectories FileDaemon's directive
 - Add ExcludeBackupDirectories FileDaemon's directive
 - Add AllowedRestoreDirectories FileDaemin's directive

Management:
 - New FreeSpace and LastBackedUpTo storage group policy
 - New ZSTD fileset compression support
 - Add Kubernetes CSI Volume Snapshot support
 - Add Amazon Cloud driver (in replacement of libS3 cloud driver)
 - Switch Storage Daemon volume format from BB02 to BB03
 - New Bacula Installation Manager (BIM) to ease the installation
 - Add runscript "AtJobCompletion" execution option

Catalog changes:
 - FileSet content description in the FileSet table
 - Add Job/RealStartTime catalog field
 - Add Job/Encrypted catalog field
 - Add Media Protected and UseProtect fields
 - Add Media VolEncrypted field
 - Add FileEvent table and "list fileevent" to track malware and viruses
 - Plugins list available in the Client table
 - Store verified jobid into the catalog PriorJobId Job field

Console changes:
 - Add JSON output to various commands (.jlist, .api 2 api_opts=j)
 - .help enhancement with description of commands
 - help command restricted to the available commands
 - Add .search bconsole command
 - Add bconsole "list joblog jobid=x pattern=xxx" option
 - Add fileindex=jobid,fidx option in .bvfs_restore
 - Add VolType to .bvfs_versions
 - Add "update volumeprotect storage=xxx" bconsole command
 - Add "status dir novolume" to not compute volume in status director output
 - Limit the "status dir" schedule output to 50 jobs. Can be managed via 
"limit=x offset=y" parameters

 - Add new error codes to job messages
 - Update timestamp of the pid file after a reload command
 - Add ".status dir client=" filter
 - Add "list 

Re: [Bacula-users] Error installing Bacula 13.0.4 on Debian 12 Bookworm

[Eric Bollengier via Bacula-users]

Hello Tomasz,

On 2/18/24 17:44, Tomasz Świderski wrote:


When trying to install Bacula 13.0.4 on Debian 12 Bookworm, when I enter the 
"apt update" command, an error is shown:


E: Splitting of clearsigned file 
/var/lib/apt/lists/partial/www.bacula.org_packages_65d0b113ad6f6_debs_13.0.4_dists_bookworm_Release failed as it doesn't contain all expected parts
E: The repository 'https://www.bacula.org/packages/65d0b113ad6f6/debs/13.0.4 
bookworm Release' provides only weak security information.



It seems to me that the Packages and Release files in the 
https://www.bacula.org/packages//debs/13.0.4/dists/bookworm/main/binary-amd64/ repository should not be empty.


The installation from the Ubuntu jammy repository was successful.

I have fixed the issue and re-uploaded new binaries, it should work now.

Best Regards,
Eric


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Error Installing Bacula 15.0.1 on Ubuntu 22.04 Server

[Eric Bollengier via Bacula-users]

Hello Mark,

Apparently, the MySQL service has some problems, and the direct consequence is
that the director cannot start properly.

I would suggest to dig into MySQL logs to determine the problem, maybe a space
problem for example.

Once resolved, you should be able to start the director.

Best Regards,
Eric

On 2/19/24 05:23, Mark Martinson wrote:

Hello – I just upgraded to Bacula 15.0.1 from 13.0.3 on Ubuntu 22.04.1 Server 
(Jammy).  I run MySQL Server version 8.0.36 with Bacula and up until yesterday 
it worked just fine (I had run a few Bacula backups prior to starting the 
upgrade).  I installed Bacula 13.0.3 and 15.0.1 from the Ubuntu repository by 
modifying the /etc/apt sources.list and 
/etc/apt/sources.list.d/Bacula-Community.list files.  Modifying those files for 
both installs worked.

Unfortunately, post the Bacula 15.0.1 upgrade, bacula-dir initially starts 
successfully, but eventually stops.
Running $ sudo systemctl status bacula-dir, just after a $ sudo systemctl stop 
bacula-dir and restart, I receive:
● bacula-dir.service - Bacula Director Daemon service
  Loaded: loaded (/lib/systemd/system/bacula-dir.service; enabled; vendor 
preset: enabled)
  Active: active (running) since Sun 2024-02-18 22:19:24 CST; 5s ago
Main PID: 2884 (bacula-dir)
   Tasks: 2 (limit: 38306)
  Memory: 2.1M
 CPU: 13ms
  CGroup: /system.slice/bacula-dir.service
  └─2884 /opt/bacula/bin/bacula-dir -fP -c 
/opt/bacula/etc/bacula-dir.conf

Feb 18 22:19:24 LinuxS-WS1 systemd[1]: Started Bacula Director Daemon service.

Waiting a little bit and re-running status, I receive the following errors:
Command $ sudo systemctl status bacula-dir, results in:
× bacula-dir.service - Bacula Director Daemon service
  Loaded: loaded (/lib/systemd/system/bacula-dir.service; enabled; vendor 
preset: enabled)
  Active: failed (Result: exit-code) since Sun 2024-02-18 21:02:12 CST; 
54min ago
 Process: 2144 ExecStart=/opt/bacula/bin/bacula-dir -fP -c 
/opt/bacula/etc/bacula-dir.conf (code=exited, status=1/FAILURE)
Main PID: 2144 (code=exited, status=1/FAILURE)
 CPU: 20ms

Feb 18 21:02:12 LinuxS-WS1 bacula-dir[2144]: MySQL connect failed either server 
not running or your authorization is incorrect.
Feb 18 21:02:12 LinuxS-WS1 bacula-dir[2144]: 18-Feb 21:02 bacula-dir ERROR 
TERMINATION
Feb 18 21:02:12 LinuxS-WS1 bacula-dir[2144]: Please correct configuration file: 
/opt/bacula/etc/bacula-dir.conf
Feb 18 21:02:12 LinuxS-WS1 systemd[1]: bacula-dir.service: Main process exited, 
code=exited, status=1/FAILURE
Feb 18 21:02:12 LinuxS-WS1 systemd[1]: bacula-dir.service: Failed with result 
'exit-code'.

Note that both bacula-sd and bacula-fd are active and running without errors on 
this machine.

Running $ sudo systemctl status mysql, I receive:
mysql.service - MySQL Community Server
  Loaded: loaded (/lib/systemd/system/mysql.service; enabled; vendor 
preset: enabled)
  Active: failed (Result: exit-code) since Sun 2024-02-18 21:00:03 CST; 
58min ago
 Process: 1479 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre 
(code=exited, status=1/FAILURE)
 CPU: 8ms

Feb 18 21:00:03 LinuxS-WS1 systemd[1]: mysql.service: Scheduled restart job, 
restart counter is at 5.
Feb 18 21:00:03 LinuxS-WS1 systemd[1]: Stopped MySQL Community Server.
Feb 18 21:00:03 LinuxS-WS1 systemd[1]: mysql.service: Start request repeated 
too quickly.
Feb 18 21:00:03 LinuxS-WS1 systemd[1]: mysql.service: Failed with result 
'exit-code'.
Feb 18 21:00:03 LinuxS-WS1 systemd[1]: Failed to start MySQL Community Server.

Trying to login to mysql by running $ mysql -u root -p (and entering the proper 
passcode when prompted), I receive:
ERROR 2002 (HY000): Can't connect to local MySQL server through socket 
'/var/run/mysqld/mysqld.sock' (2)

Trying to restart mysql server by running $ sudo systemctl restart mysql, I 
receive:
Job for mysql.service failed because the control process exited with error code.
See "systemctl status mysql.service" and "journalctl -xeu mysql.service" for 
details.

Entering $ systemctl status mysql.service, I receive:
× mysql.service - MySQL Community Server
  Loaded: loaded (/lib/systemd/system/mysql.service; enabled; vendor 
preset: enabled)
  Active: failed (Result: exit-code) since Sun 2024-02-18 22:02:28 CST; 39s 
ago
 Process: 2783 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre 
(code=exited, status=1/FAILURE)
 CPU: 10ms

Feb 18 22:02:28 LinuxS-WS1 systemd[1]: mysql.service: Scheduled restart job, 
restart counter is at 5.
Feb 18 22:02:28 LinuxS-WS1 systemd[1]: Stopped MySQL Community Server.
Feb 18 22:02:28 LinuxS-WS1 systemd[1]: mysql.service: Start request repeated 
too quickly.
Feb 18 22:02:28 LinuxS-WS1 systemd[1]: mysql.service: Failed with result 
'exit-code'.
Feb 18 22:02:28 LinuxS-WS1 systemd[1]: Failed to start MySQL Community Server.

Entering $ journalctl -xeu mysql.service, I receive:
The process' exit code is 'exited' 

[Bacula-users] Beta Release 15.0.1

[Eric Bollengier via Bacula-users]

Hello,

I'm pleased to announce that the second beta version of the next Bacula
Community version 15.0 was pushed on our git repository (Branch-15.0).

The beta version 15.0.1 should be pretty stable. The list of the changes is very
impressive as you can see in the following section and in the ChangeLog. Thanks
to all the contributors, specially Bacula Systems. The documentation update is
still in progress, but a good part of the new features are already covered.

We have upgraded the volume format from BB02 to BB03 to support options such as
the Volume encryption. Old volumes can still be used by the 15.0 Storage
Daemon, however, new 15.0 BB03 volumes cannot be used by old Storage Daemons.

A set of Debian/Ubuntu/Redhat packages are already uploaded to bacula.org.

Thanks for using Bacula,

Best Regards,
Eric

Security:
 - Director TOTP Console authentication plugin
 - Better restricted console support
 - Add Storage Daemon Volume encryption support
 - Add support for Immutable filesystem flag for volumes
 - Add support for Append Only filesystem flag for volumes
 - Clamav Antivirus plugin
 - Malware detection code (via Abuse.ch)
 - Add AllowedBackupDirectories FileDaemon's directive
 - Add AllowedScriptDirectories FileDaemon's directive
 - Add ExcludeBackupDirectories FileDaemon's directive
 - Add AllowedRestoreDirectories FileDaemin's directive

Management:
 - New FreeSpace and LastBackedUpTo storage group policy
 - New ZSTD fileset compression support
 - Add Kubernetes CSI Volume Snapshot support
 - Add Amazon Cloud driver (in replacement of libS3 cloud driver)
 - Switch Storage Daemon volume format from BB02 to BB03
 - New Bacula Installation Manager (BIM) to ease the installation
 - Add runscript "AtJobCompletion" execution option

Catalog changes:
 - FileSet content description in the FileSet table
 - Add Job/RealStartTime catalog field
 - Add Job/Encrypted catalog field
 - Add Media Protected and UseProtect fields
 - Add Media VolEncrypted field
 - Add FileEvent table and "list fileevent" to track malware and viruses
 - Plugins list available in the Client table
 - Store verified jobid into the catalog PriorJobId Job field

Console changes:
 - Add JSON output to various commands (.jlist, .api 2 api_opts=j)
 - .help enhancement with description of commands
 - help command restricted to the available commands
 - Add .search bconsole command
 - Add bconsole "list joblog jobid=x pattern=xxx" option
 - Add fileindex=jobid,fidx option in .bvfs_restore
 - Add VolType to .bvfs_versions
 - Add "update volumeprotect storage=xxx" bconsole command
 - Add "status dir novolume" to not compute volume in status director output
 - Limit the "status dir" schedule output to 50 jobs. Can be managed via 
"limit=x offset=y" parameters

 - Add new error codes to job messages
 - Update timestamp of the pid file after a reload command
 - Add ".status dir client=" filter
 - Add "list jobs reviewed=<1|0>" command
 - Add Runscript to control the run queue (RunsWhen=Queue)
 - Add ".ls dironly" bconsole command
 - Add new Job statuses when the Job is waiting on SD/FD
 - Add new PriorJobId and PriorJobName to volume label format variables
 - Progress Status for Copy/Migration Jobs in "status director" output
 - Add  "list fileevent" bconsole command

Baculum and Rest API changes:
 - Add joberrors parameter to jobs endpoint
 - Add fileset parameter to objects endpoint
 - Add filename and path properties to fileevent endpoints
 - Add sorting parameters to clients endpoint
 - Add running jobs property to clients endpoint
 - Add documentation for os and version filters in clients endpoint
 - Add os and version parameters to clients endpoint
 - Add os, version properties and overview parameter to clients endpoint
 - Add endpoint to check disk archive device prformance on storage
 - Add endpoint to list files and dirs on storage daemon host
 - Add delete pool endpoint
 - Add delete object endpoint
 - Use new delete module in volume and job endpoints
 - Add module for delete command
 - Add client name parameter to clients endpoint
 - Add file events API endpoint
 - Improve extended name validator
 - Speed up dashboard page loading
 - Fix parsing director time in time endpoint
 - Add objecttype parameter to object categories endpoint
 - Add second dimensional sorting and use it for sorting jobstatus in
 - Add modify default object sorting in object overview endpoint
 - Fix support for PHP 5.4 in web interface layer
 - Fix content field in job record
 - Improve support for newer PostgreSQL versions
 - Add fileset content property to jobs endpoint
 - Add object categories endpoint
 - Add support for ALL action in console ACL
 - Add objecttype filter to objects names endpoint
 - Add default sorting by endtime to objects overview endpoint
 - Add sorting parameters to volumes overview endpoint
 - Add second dimension of sorting in jobs objects endpoint
 - Add offset and limit parameters to director status endpoint
 - Add sorting by 

Re: [Bacula-users] bacula-fd hangs during backup

[Eric Bollengier via Bacula-users]

Hello Peter,

Without the ReadFifo directive, it's unlikely to cause a problem,
and the file daemon output is pretty clear, we are not at this file.

The problem can be somewhere else, and a good start is a "status dir"
and "status storage".

Best Regards,
Eric

On 2/13/24 06:23, Peter Sjoberg wrote:


Actually, I think I found the root cause - a pipe!

The file listed in the client status is not the problem but close to it is a 
pipe (maybe next file) and that is what causing the issue in all cases.

I striped down the directory to just one file and it still fails

root@defiant1:/home/debug# find .zoom -ls
  23855106  4 drwx--   4 sys  adm  4096 Feb 13 00:11 .zoom
  23855107  4 drwxrwxr-x   2 ba   ba   4096 Feb 13 00:11 
.zoom/data
  23855116  0 prw-r--r--   1 ba   ba  0 Mar 12  2021 
.zoom/data/com.zoom.ipc.confapp__res
  23855110  4 drwxrwxr-x   2 sys  adm  4096 May  5  2020 
.zoom/reports

root@defiant1:/home/debug#


and if I send something to the pipe the job finish ok and restoring the job did 
include the pipe.


/ps

On 2024-02-12 23:36, Peter Sjoberg wrote:


In short - no and no, no special files
Also, while I haven't waited forever I have left it for several hours so it's 
not like it's just some house cleaning left.

It does happen on different servers, sample below is my laptop.

=== My fileset:
FileSet {
 Name = "debugfs2"
 Ignore FileSet Changes = yes
 Include {
   Options {
 signature=MD5
 honor nodump flag=yes
 noatime=yes
 keepatime = no
 sparse=yes
 exclude = yes
 wild = *~
 wild = *.tmp
 }
   File = "/home/ba/.zoom"
   }
 }

= run command
echo run BackupQ_defiant1 FileSet="debugfs2" Level=Full yes|bconsole


= client status when hung
root@quark:~# echo stat client=defiant1-fd|bconsole #CLIENTSTAT
Connecting to Director quark:9101
1000 OK: 10002 techwiz-dir Version: 13.0.3 (02 May 2023)
Enter a period to cancel a command.
stat client=defiant1-fd
Connecting to Client defiant1-fd at defiant1:9102

defiant1-fd Version: 13.0.3 (02 May 2023) 
x86_64-pc-linux-gnu-bacula-enterprise ubuntu 22.04

Daemon started 12-Feb-24 23:22. Jobs: run=2 running=1.
 Heap: heap=856,064 smbytes=606,583 max_bytes=794,675 bufs=188 max_bufs=203
 Sizes: boffset_t=8 size_t=8 debug=0 trace=0 mode=0,0 bwlimit=0kB/s
 Crypto: fips=N/A crypto=OpenSSL 3.0.2 15 Mar 2022
 Plugin: bpipe-fd.so(2)

Running Jobs:
JobId 255 Job BackupQ_defiant1.2024-02-12_23.29.48_18 is running.
    Full Backup Job started: 12-Feb-24 23:29
    Files=2 Bytes=0 AveBytes/sec=0 LastBytes/sec=0 Errors=0
    Bwlimit=0 ReadBytes=0
    Files: Examined=2 Backed up=2
    Processing file: /home/ba/.zoom/logs
    SDReadSeqNo=8 fd=5 SDtls=1
Director connected using TLS at: 12-Feb-24 23:30



 Content of that directory

root@defiant1:~# find  /home/ba/.zoom -ls
  15728688  4 drwx--   7 ba   ba   4096 Apr 28  2021 
/home/ba/.zoom
  16130303  4 drwx--   2 ba   ba   4096 Apr 28  2021 
/home/ba/.zoom/screenCapture
  16130301  4 drwxrwxr-x   2 ba   ba   4096 Feb 12 18:47 
/home/ba/.zoom/logs
  16023538  4 drwxrwxr-x   4 ba   ba   4096 Apr 28  2021 
/home/ba/.zoom/data
  16023540  0 prw-r--r--   1 ba   ba  0 May  5  2020 
/home/ba/.zoom/data/com.zoom.ipc.assistantapp__res
  16023541  0 prw-r--r--   1 ba   ba  0 Mar 12  2021 
/home/ba/.zoom/data/com.zoom.ipc.confapp__req
  16023539  0 prw-r--r--   1 ba   ba  0 Apr 28  2021 
/home/ba/.zoom/data/com.zoom.ipc.assistantapp__req
  16130305  4 drwx--   2 ba   ba   4096 Mar 23  2021 
/home/ba/.zoom/data/VirtualBkgnd_Custom
  16131475   1564 -rw---   1 ba   ba    1597940 Mar 23  2021 
/home/ba/.zoom/data/VirtualBkgnd_Custom/{ff6d8a57-d810-4dd2-bf1b-8366c063728f}
  16023542  0 prw-r--r--   1 ba   ba  0 Mar 12  2021 
/home/ba/.zoom/data/com.zoom.ipc.confapp__res
  16023545 52 -rw---   1 ba   ba  53248 Apr 28  2021 
/home/ba/.zoom/data/zoomus.enc.db
  16130304  4 drwx--   2 ba   ba   4096 Mar 23  2021 
/home/ba/.zoom/data/ConfAvatar
  16131472 36 -rw---   1 ba   ba  36397 Mar 23  2021 
/home/ba/.zoom/data/ConfAvatar/conf_avatar_6c72761c1ad5cc6f485dce3966cbb705_100
  16131473  4 -rw---   1 ba   ba   1020 Mar 23  2021 
/home/ba/.zoom/data/ConfAvatar/conf_avatar_9e6b3f01c5d33a2052c2681a42b4e659_100
  16131474  4 -rw---   1 ba   ba   1020 Mar 23  2021 
/home/ba/.zoom/data/ConfAvatar/conf_avatar_e977cbed2632f5b11882e92e31f32516_100
  16023544  8 -rw---   1 ba   ba   5120 Mar 23  2021 
/home/ba/.zoom/data/zoommeeting.enc.db
  16130302  4 drwxrwxr-x   2 ba   ba   4096 May  5  2020 

[Bacula-users] Bacula Release 13.0.4

[Eric Bollengier via Bacula-users]

Hello,

We are pleased to announce the release of Bacula version 13.0.4 This is a
minor bugfix release of the new stable version. We recommend to upgrade to this
version.

The new release 13.0 has many new features and a number of changes.
Please take care to test this code carefully before putting it
into production. The version 13.0.4 fixes a compatibility problem with old
Bacula FileDaemons.

This release of Bacula uses a new catalog format.  We provide a set of
scripts that permit to convert a 11.x and earlier versions to the new
13.0 format (1024).  Normally, it is fast and automatic.

Note that converting from 9.x is a big change that takes longer than usual.
Beetween 9.x and 11.x, the upgrade process will require more or less twice
the size of the actual database on disk.

Please see the ReleaseNotes for how to build Bacula 13.0.4 with the
correct libs3 for use with the Amazon Cloud.

Most of the binaries (rpm, deb) are already ready, more should come
this week.

Thank you for using Bacula,
Eric


Release 13.0.4 / 12 February 2024


13.0.4 is a minor bug fix release.

 - Fix org#2704 about old FD (< 13.0) compatibility. Job messages were not 
properly handled by the Director.

 - Fix compilation on FreeBSD
 - Remove baculabackupreport. Can be found at 
https://github.com/waa/baculabackupreport


 - baculum: Add sorting by fileset in objects overview endpoint
 - baculum: Add sorting by objectcategory in objects overview endpoint
 - baculum: Add client name parameter to clients endpoint
 - baculum: Add default sorting by endtime to objects overview endpoint
 - baculum: Add delete client endpoint
 - baculum: Add delete object endpoint
 - baculum: Add delete pool endpoint
 - baculum: Add director time endpoint
 - baculum: Add documentation for client parameter in objects endpoint
 - baculum: Add documentation for os and version filters in clients endpoint
 - baculum: Add endpoint to check disk archive device performance on storage 
daemon host

 - baculum: Add endpoint to list files and dirs on storage daemon host
 - baculum: Add file events API endpoint
 - baculum: Add filename and path properties to fileevent endpoints
 - baculum: Add fileset content property to jobs endpoint
 - baculum: Add fileset parameter to objects endpoint
 - baculum: Add group_offset and unique_objects parameters to objects endpoint
 - baculum: Add group_order_by and group_order_direction parameters to 
documentation
 - baculum: Add group_order_by and group_order_direction parameters to objects 
endpoint

 - baculum: Add job level property to sources endpoint
 - baculum: Add job name and fileset to status client endpoint
 - baculum: Add job status filter to objects endpoint
 - baculum: Add job type property to objects overview endpoint
 - baculum: Add joberrors filter to sources endpoint
 - baculum: Add joberrors parameter to jobs endpoint
 - baculum: Add modify default object sorting in object overview endpoint
 - baculum: Add module for delete command
 - baculum: Add notes about object type filters in objects overview endpoint
 - baculum: Add object categories endpoint
 - baculum: Add object names endpoint
 - baculum: Add object overview endpoint
 - baculum: Add object types endpoint
 - baculum: Add objectname parameter to jobs objects endpoint
 - baculum: Add objectsize property to objects overview endpoint
 - baculum: Add objectsource property to objects overview endpoint
 - baculum: Add objecttype filter to objects names endpoint
 - baculum: Add objecttype parameter to object categories endpoint
 - baculum: Add offset and limit parameters to director status endpoint
 - baculum: Add os and version parameters to clients endpoint
 - baculum: Add os, version properties and overview parameter to clients 
endpoint
 - baculum: Add path property to objects overview endpoint
 - baculum: Add pool resnames endpoint
 - baculum: Add regex operator support in queries
 - baculum: Add restricting resources in objects overview endpoint
 - baculum: Add running jobs property to clients endpoint
 - baculum: Add second dimension of sorting in jobs objects endpoint
 - baculum: Add second dimensional sorting and use it for sorting jobstatus in 
sources overview endpoint

 - baculum: Add server parameter to list vsphere datastores endpoint
 - baculum: Add sorting by endtime and add endtime property to objects overview 
endpoint

 - baculum: Add sorting by joberrors if sorted by jobstatus first
 - baculum: Add sorting parameters to clients endpoint
 - baculum: Add sorting parameters to volumes overview endpoint
 - baculum: Add storage resnames endpoint
 - baculum: Add support for ALL action in console ACL
 - baculum: Add to group function sorting group capability
 - baculum: Add volume names endpoint
 - baculum: Change M365 tenants endpoint output to contain tenant names
 - baculum: Fix content field in job record
 - 

Re: [Bacula-users] orphaned filename records

[Eric Bollengier via Bacula-users]

Hello Adam,

On 12/22/23 13:04, Adam Weremczuk wrote:

Hi all,

Bacula 9.6.7 on Debian 11.



Every 3 months I run "dbcheck -f -c /etc/bacula/bacula-dir.conf"

Last time 32,525 orphaned filename records were found and deleted and the count 
was 27,550 before that > ...


Q1
There have been no major changes in terms of clients and datasets. What could 
possibly justify a jump from 32,525 to 8,745,187 in 3 months?


Difficult to say without the files themself, or the job records/logs associated.
For example it can be files coming from a cache, a new server, etc...

Usually, you should find the top producers, and just by listing the files, you
will get your answer.


Q2
I have never run ".bvfs_clear_cache yes" before typing yes.
Is it really a necessary step requiring opening a second shell and running this 
command manually?


It is not recommended to clear the Path entries all the time because the
bvfs cache building process is quite slow. You might want to clean it up
once every 6 months, or based on a number of records.


Is there any reason this step hasn't been directly incorporated into "dbcheck"?


Yes, dbcheck will not drop this cache for the reason I gave just before.

Side note, switching to a recent version of Bacula will make dbcheck almost
useless because the Filename entries are no longer in a separated table.

Only the Path table will need a cleanup if it becomes too big to fit in memory.

Best Regards,
Eric


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Procedure to clear off historical CDP journal/spool content ?

[Eric Bollengier via Bacula-users]

Hello Myles,

On 1/21/24 05:04, MylesDearBusiness via Bacula-users wrote:

Hello,

Other backup systems comparable to Bacula CDP plugin such as the NFS .snapshot 
model limit the number of daily/weekly snapshots that are made available.

I see the Bacula cdp-client maintains an always-growing journal / spool 
directory, the sizes of which appear to be unbounded, which as a system 
administrator makes me nervous.

My question : if I wanted to remove CDP detected file versions that were older 
than a certain amount of time (ie. one year) what would be the best tool / 
methodology to do so?



Normally the Bacula backup job should cleanup the journal and the spool
directory. Maybe it is not properly configured or it has a bug. I would
suggest to give some more information like the job/fileset, the job output
some overview of the spool and journal before and after the backup job.

Thanks,

Best Regards,
Eric



___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Bacula BPIPE help

[Eric Bollengier via Bacula-users]

Hello Ismael,

On 2/2/24 16:57, Ismael Matos wrote:

Hello everyone,

I've been spending time trying to make BPIPE work for me to take backup of
a few postgres databases.  So far, it seems, not enough time, so success is
still away from me.  I've already tried the FIFO file approach and gave up.

Backup works perfectly when I use pg_dump to a /tmp/ directory, but I'd
rather skip creating those intermediate files, as the databases are growing
faster than expected.


Normally, you can send the pg_dump into the bpipe plugin using more or less
the same command.


I believe some of you out there have been using the BPIPE approach with the
postgres databases.

May I ask you to send the relevant snippets of shell script and
bacula-dir/bacula-fd config files?


I think it's the right place to share experience and get help.

Best Regards,
Eric


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Some CDP plugin questions

[Eric Bollengier via Bacula-users]

Hello Myles,

On 1/16/24 18:47, MylesDearBusiness via Bacula-users wrote:

Hello, Bacula experts.

I was pleasantly surprised to see the CDP plugin is part of the community 
edition. I'm hoping to take full advantage of this.

I'm running it on a Ubuntu 22.04.3 LTS bare metal cloud server.

After looking at the main reference manual section 47.1, I still have questions:

- If I want to specify multiple users to be monitored, do I just have multiple Plugin = 
"cdp: userHome=/home/" directives in my director FileSet / Include 
configuration?


I would put only one plugin line and multiple userHome directories (or user=)

   Plugin = "cdp: user=eric user=myles"



- Is it legal to specify a number of Plugin directives in my FileSet Include block as 
well as multiple "File = /path/to/dir-to-monitor" directives all together ?


Yes, it will work


- I'm seeing evidence that my /root/.cdp-sdir is the only place where the spool directory is created (I'm 
running my fd as root), despite me having multiple "cdp: userHome" lines, so what exactly are 
the semantics of this directive? The documentation says that this points to the home directory of the cdp 
user, which presumably would be the user running the fd, and the place where the spool directory is 
placed, but I want to monitor multiple places, including user home directories and key places such as 
/var/lib/mysql where I didn't think the Plugin = "cdp: user=" directive was 
appropriate, so I'm using the userHome directive for these cases. Hope it works.


The .cdp-sdir is used by the cdp daemon that is monitoring your files, you
should have one in each user directory.



- I don't see /opt/bacula/bin/cdp-client running continuously on my /bin/ps -Af 
command output, am I expected to launch this myself at startup?


Yes, it should be started, I believe that we have a GUI to run it, but it can be
started with your session as well.


Since I'm seeing evidence that spooling is happening, with the config I've 
described, in what cases is this client automatically run? For example, is this 
client only run when a job is launched? What is the recommended way of setting 
this up?


No, it runs when the user is logged in, files that are modified are copied in
the spool directory, and the Bacula job will come from time to time to backup
all versions and do some cleanup. Doing so, the CDP will work even if you
are not connected to the network.



- Since the Linux cdp uses the inotify API, whose man page states is not 
recursive, am I assured that when I specify a directory that CDP will tell 
inotify to monitor all its subdirectories as well?


Yes, this part is handled by the cdp daemon. I would recommend to not monitor
hundred of thousand directories, but really where you work.


- ChatGPT insists that in the file daemon configuration each directory to back up may be specified 
in a separate "Plugin {cdp: userHome=/home/} block but I see nothing in the 
documentation that corroborates this, it also says that when specifying in this way, the director 
FileSet block may have just a single plugin line referencing no directories{ Options {...} Plugin = 
"cdp"}. Is my just my AI hallucinating or does this configuration work ?


I would rather trust the users list, the code or both, but not chatgpt for that 
:-)

Best Regards,
Eric


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

[Bacula-users] Beta Release 15.0.0 - packages

[Eric Bollengier via Bacula-users]

Hello,

I have pushed a couple of binaries on bacula.org (ubuntu jammy, debian bullseye
and almalinux 8), you might find them under:

https://www.bacula.org/packages/beta/

To get the configuration to use in your package manager, you can browse the 
directories and click on the get_repos.php file.


The output should look like:

# Add key to APT
# curl 
https://bacula.org/downloads/Bacula-4096-Distribution-Verification-key.asc | 
sudo apt-key add -

#
# Add this line to /etc/apt/sources.list.d/baculacommunity.list and execute 
\"apt-get update\"

deb https://www.bacula.org/packages/beta/debs/15.0.0/ bullseye main
#
# Install: apt-get install bacula-postgresql

And you can follow the instructions and enjoy this new version.

Any feedback is welcome!

Best Regards,
Eric


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

[Bacula-users] Beta Release 15.0.0

[Eric Bollengier via Bacula-users]

Hello,

I'm pleased to announce that the first beta version of the next Bacula
Community version 15.0 was pushed on our git repository (Branch-15.0). The beta 
version

15.0.0 should be pretty stable. The list of the changes is very impressive as
you can see in the following section and in the ChangeLog. Thanks to all the
contributors, specially Bacula Systems. The documentation update is still in
progress, but a good part of the new features are already covered.

We have upgraded the volume format from BB02 to BB03 to support options such as
the Volume encryption. Old volumes can still be used by the 15.0 Storage
Daemon, however, new 15.0 BB03 volumes cannot be used by old Storage Daemons.

More news in the next days, specially with a set of Debian/Ubuntu/Redhat 
packages.
Thanks for using Bacula,

Best Regards,
Eric

Security:
 - Director TOTP Console authentication plugin
 - Better restricted console support
 - Add Storage Daemon Volume encryption support
 - Add support for Immutable filesystem flag for volumes
 - Add support for Append Only filesystem flag for volumes
 - Clamav Antivirus plugin
 - Malware detection code (via Abuse.ch)
 - Add AllowedBackupDirectories FileDaemon's directive
 - Add AllowedScriptDirectories FileDaemon's directive
 - Add ExcludeBackupDirectories FileDaemon's directive
 - Add AllowedRestoreDirectories FileDaemin's directive

Management:
 - New FreeSpace, LastBackedUpTo, FreeSpaceLeastUsed, LastBackupedToStore 
storage group policies

 - New ZSTD fileset compression support
 - Add Kubernetes CSI Volume Snapshot support
 - Add Amazon Cloud driver (in replacement of libS3 cloud driver)
 - Switch Storage Daemon volume format from BB02 to BB03
 - New Bacula Installation Manager (BIM) to ease the installation
 - Add runscript "AtJobCompletion" execution option

Catalog changes:
 - FileSet content description in the FileSet table
 - Add Job/RealStartTime catalog field
 - Add Job/Encrypted catalog field
 - Add Media Protected and UseProtect fields
 - Add Media VolEncrypted field
 - Add FileEvent table and "list fileevent" to track malware and viruses
 - Plugins list available in the Client table
 - Store verified jobid into the catalog PriorJobId Job field

Console changes:
 - Add JSON output to various commands (.jlist, .api 2 api_opts=j)
 - Add .search bconsole command
 - Add bconsole "list joblog jobid=x pattern=xxx" option
 - Add "update volumeprotect storage=xxx" bconsole command
 - Add "status dir novolume" to not compute volume in status director output
 - Limit the "status dir" schedule output to 50 jobs. Can be managed via 
"limit=x offset=y" parameters

 - Add new error codes to job messages
 - Update timestamp of the pid file after a reload command
 - Add "list jobs reviewed=<1|0>" command
 - Add Runscript to control the run queue (RunsWhen=Queue)
 - Add new Job statuses when the Job is waiting on SD/FD
 - Add new PriorJobId and PriorJobName to volume label format variables
 - Progress Status for Copy/Migration Jobs in "status director" output
 - Add  "list fileevent" bconsole command
 - help command restricted to the available commands
 - .help enhancement with description of commands
 - Add fileindex=jobid,fidx option in .bvfs_restore
 - Add VolType to .bvfs_versions
 - Add ".status dir client=" filter
 - Add ".ls dironly" bconsole command

Baculum and Rest API changes:
 - Add joberrors parameter to jobs endpoint
 - Add fileset parameter to objects endpoint
 - Add filename and path properties to fileevent endpoints
 - Add sorting parameters to clients endpoint
 - Add running jobs property to clients endpoint
 - Add documentation for os and version filters in clients endpoint
 - Add os and version parameters to clients endpoint
 - Add os, version properties and overview parameter to clients endpoint
 - Add endpoint to check disk archive device prformance on storage
 - Add endpoint to list files and dirs on storage daemon host
 - Add delete pool endpoint
 - Add delete object endpoint
 - Use new delete module in volume and job endpoints
 - Add module for delete command
 - Add client name parameter to clients endpoint
 - Add file events API endpoint
 - Improve extended name validator
 - Speed up dashboard page loading
 - Fix parsing director time in time endpoint
 - Add objecttype parameter to object categories endpoint
 - Add second dimensional sorting and use it for sorting jobstatus in
 - Add modify default object sorting in object overview endpoint
 - Fix support for PHP 5.4 in web interface layer
 - Fix content field in job record
 - Improve support for newer PostgreSQL versions
 - Add fileset content property to jobs endpoint
 - Add object categories endpoint
 - Add support for ALL action in console ACL
 - Add objecttype filter to objects names endpoint
 - Add default sorting by endtime to objects overview endpoint
 - Add sorting parameters to volumes overview endpoint
 - Add second dimension of sorting in jobs objects endpoint
 - Add offset and limit parameters 

Re: [Bacula-users] Aligned plugin inactive on 13 version

[Eric Bollengier via Bacula-users]

Hello Christophe,

Yes, aligned is missing on that build, I have fixed it, can you try
with 13.0.3-23102316 ?

Thanks

Best Regards,
Eric

On 10/23/23 16:16, Christophe Maillard wrote:

Hello Eric,

Thanks for the help.

So, I have installed this 3 new packages on the storage server

dpkg -l |grep bacula
ii  bacula-aligned  13.0.3-23050308~jammy   
amd64Network backup, recovery and verification - Aligned Format Plugin
ii  bacula-client   13.0.3-23102313~jammy   
amd64Network backup, recovery and verification - file daemon
ii  bacula-common   13.0.3-23102313~jammy   
amd64Network backup, recovery and verification - common support files
ii  bacula-console  13.0.3-23102313~jammy   
amd64Network backup, recovery and verification - text console

(new version for the aligned plugin is not available)

But still have the same issue when I launch the SD service in debug mode :

/opt/bacula/bin/bacula-sd -d 150 -f -c /opt/bacula/etc/bacula-sd.conf
bacula-sd: address_conf.c:289-0 Initaddr 0.0.0.0:9103
slco-bkpsto-02-sd: jcr.c:130-0 read_last_jobs seek to 192
slco-bkpsto-02-sd: jcr.c:137-0 Read num_items=0
slco-bkpsto-02-sd: plugins.c:97-0 load_plugins
slco-bkpsto-02-sd: plugins.c:133-0 Rejected plugin: want=*-sd.so got 
name=bpipe-fd.so len=11
slco-bkpsto-02-sd: plugins.c:133-0 Rejected plugin: want=*-sd.so got 
name=bacula-sd-aligned-driver-13.0.3.so len=34
slco-bkpsto-02-sd: plugins.c:121-0 Failed to find any plugins in 
/opt/bacula/plugins
slco-bkpsto-02-sd: stored.c:711-0 calling init_dev FileChgrSLCO-BKPSTO-02-Dev01
slco-bkpsto-02-sd: init_dev.c:141-0 init_dev dev_type=9
slco-bkpsto-02-sd: init_dev.c:177-0 Num drivers=15
slco-bkpsto-02-sd: init_dev.c:185-0 loadable=1 type=9 loaded=0 name=aligned 
handle=0
slco-bkpsto-02-sd: init_dev.c:471-0 loadable=1 type=9 loaded=0 name=aligned 
handle=0
slco-bkpsto-02-sd: init_dev.c:481-0 Open SD driver at 
/opt/bacula/plugins/bacula-sd-aligned-driver-13.0.3.so
slco-bkpsto-02-sd: init_dev.c:484-0 Driver=aligned handle=7ffa8800bcb0
slco-bkpsto-02-sd: init_dev.c:486-0 Lookup "BaculaSDdriver" in driver=aligned
slco-bkpsto-02-sd: init_dev.c:488-0 Driver=aligned entry point=0
slco-bkpsto-02-sd: init_dev.c:493-0 Lookup of symbol "BaculaSDdriver" 
driver=/opt/bacula/plugins/bacula-sd-aligned-driver-13.0.3.so failed: 
ERR=/opt/bacula/plugins/bacula-sd-aligned-driver-13.0.3.so: undefined symbol: 
BaculaSDdriver
slco-bkpsto-02-sd: stored.c:713-0 SD init done FileChgrSLCO-BKPSTO-02-Dev01 
(0x0)
slco-bkpsto-02-sd: stored.c:715-0 Could not initialize SD device 
"FileChgrSLCO-BKPSTO-02-Dev01"
slco-bkpsto-02-sd: events.c:48-0 Events: code=SD0001 daemon=slco-bkpsto-02-sd 
ref=0x238f type=daemon source=*Daemon* text=Storage startup 13.0.3 (02May23)
slco-bkpsto-02-sd: bnet_server.c:90-0 Addresses 0.0.0.0:9103
slco-bkpsto-02-sd: bsock.c:861-0 socket=5 who=client host=163.109.66.19 
port=9103
slco-bkpsto-02-sd: bnet_server.c:235-0 Accept 
socket=169.60.146.84.9103:163.109.66.19.46720 s=0x55aea5bccdf8
slco-bkpsto-02-sd: dircmd.c:195-0 Got a DIR connection at 23-Oct-2023 09:11:59
slco-bkpsto-02-sd: authenticatebase.cc:365-0 TLSPSK Remote need 202
slco-bkpsto-02-sd: authenticatebase.cc:335-0 TLSPSK Local need 202
slco-bkpsto-02-sd: authenticatebase.cc:560-0 TLSPSK Start TLS
slco-bkpsto-02-sd: bnet.c:96-0 TLS server negotiation established.
slco-bkpsto-02-sd: cram-md5.c:68-0 send: auth cram-md5 challenge 
<1781139798.1698070319@slco-bkpsto-02-sd> ssl=2
slco-bkpsto-02-sd: cram-md5.c:132-0 cram-get received: auth cram-md5 
<1540330470.1698070320@slbr-bkpdir-01-dir> ssl=2
slco-bkpsto-02-sd: cram-md5.c:156-0 sending resp to challenge: 
RGpXhWN/S+l6hm+9f9+JkC
slco-bkpsto-02-sd: dircmd.c:227-0 Message channel init completed.
List plugins. Hook count=0

Do I miss something ?

Thanks

Best Regards,
Christophe




Cegid est susceptible d'effectuer un traitement sur vos donn?es personnelles ? 
des fins de gestion de notre relation commerciale. Pour plus d'information, 
consultez https://www.cegid.com/fr/privacy-policy
Ce message et les pi?ces jointes sont confidentiels et ?tablis ? l'attention 
exclusive de ses destinataires. Toute utilisation ou diffusion, m?me partielle, 
non autoris?e est interdite. Tout message ?lectronique est susceptible 
d'alt?ration; Cegid d?cline donc toute responsabilit? au titre de ce message. 
Si vous n'?tes pas le destinataire de ce message, merci de le d?truire et 
d'avertir l'exp?diteur.

Cegid may process your personal data for the purpose of our business 
relationship management. For more information, please visit our website 
https://www.cegid.com/en/privacy-policy
This message and any attachments are confidential and intended solely for the 
addressees. Any unauthorized use or disclosure, either whole or partial is 
prohibited. E-mails are susceptible to alteration; Cegid shall therefore not be 
liable for the 

Re: [Bacula-users] Aligned plugin inactive on 13 version

[Eric Bollengier via Bacula-users]

Hello Christophe,

Nice spot, could you test with the new binaries that I have pushed
this morning?

Thanks
Best Regards,
Eric

On 10/12/23 12:09, Christophe Maillard wrote:

Hello everyone,

I'm working on the project to replace an old Bacula 9.4 by the latest version 
13.0.3, with the Director and the storages installed on different servers, and 
I plan to use ZFS deduplication on the storages. Backups will be stored on 
disks with virtual drives.
This servers are installed with Ubuntu 22.04 LTS  (Jammy).

So no problem with the installations on each servers, I used the official 
packages available here :
https://www.bacula.org/packages/5cee4d079821e/debs/13.0.3/dists/jammy/main/binary-amd64/


   *   This is my storage configuration on the Director:

Autochanger {
   Name = FileSLCO-BKPSTO-02
   Address = slco-bkpsto-02.domain
   SDPort = 9103
   Password = "*"
   Device = FileChgrSLCO-BKPSTO-02
   Media Type = FileSLCO-BKPSTO-02
   Maximum Concurrent Jobs = 20
   Autochanger = FileSLCO-BKPSTO-02
   TLS Enable = yes
   TLS Require = yes
   TLS CA Certificate File = /opt/bacula/ssl/bacula_int.crt
   TLS Certificate = /opt/bacula/ssl/bacula.crt
   TLS Key = /opt/bacula/ssl/bacula.key
}


   *   This is the configuration in the file bacula-sd.conf on one of the 
storage

Storage {
   Name = slco-bkpsto-02-sd
   SDPort = 9103
   WorkingDirectory = "/opt/bacula/working"
   Pid Directory = "/opt/bacula/working"
   Plugin Directory = "/opt/bacula/plugins"
   Maximum Concurrent Jobs = 20
}

Director {
   Name = slbr-bkpdir-01-dir
   Password = ""
   # TLS
   TLS Enable = yes
   TLS Require = yes
   TLS Verify Peer = yes
   TLS Allowed CN = slco-bkpsto-02.domain
   TLS CA Certificate File = /opt/bacula/ssl/bacula_int.crt
   TLS Certificate = /opt/bacula/ssl/bacula.crt
   TLS Key = /opt/bacula/ssl/bacula.key
}

Autochanger {
   Name = FileChgrSLCO-BKPSTO-02
   Device = FileChgrSLCO-BKPSTO-02-Dev01
   Changer Command = ""
   Changer Device = /dev/null
}

Device {
   Name = FileChgrSLCO-BKPSTO-02-Dev01
   Media Type = FileSLCO-BKPSTO-02
   Archive Device = /home/bacula
   LabelMedia = yes
   Random Access = Yes;
   AutomaticMount = yes;
   RemovableMedia = no;
   AlwaysOpen = no;
   Maximum Concurrent Jobs=1
   Device Type = Aligned
   Maximum Block Size = 128K
   Minimum Block Size = 0
   File Alignment = 128K
   Padding Size = 512
   Minimum Aligned Size = 4096
}

Messages {
   Name = Standard
   director = slbr-bkpdir-01-dir = all
}


   *   Aligned plugin is installed and present on the storage


ll /opt/bacula/plugins/
total 100
drwxr-xr-x  2 root root  4096 Oct  6 13:10 ./
drwxr-xr-x 12 root root  4096 Oct  6 13:10 ../
-rw-r--r--  1 root root 15544 May  3 02:04 bacula-sd-aligned-driver-13.0.3.so
-rw-r--r--  1 root root 75960 May  3 02:03 bpipe-fd.so


   *   And the ZFS configuration


zfs list
NAME  USED  AVAIL REFER  MOUNTPOINT
tank  194K  1.42T   24K  /tank
tank/bacula24K  1.42T   24K  /home/bacula

zfs get recordsize
NAME PROPERTYVALUESOURCE
tank recordsize  128K local
tank/bacula  recordsize  128K inherited from tank


   *   But at the time to request the storage from the Director, with the 
status storage command, an information is missing, the Device Aligned, which is 
necessary to load drives at the start of a backup in a deduplication context

*status storage=FileSLCO-BKPSTO-02
Connecting to Storage daemon FileSLCO-BKPSTO-02 at slco-bkpsto-02.domain:9103

slco-bkpsto-02-sd Version: 13.0.3 (02 May 2023) 
x86_64-pc-linux-gnu-bacula-enterprise ubuntu 22.04
Daemon started 12-Oct-23 04:18. Jobs: run=0, running=0.
Ulimits: nofile=1024 memlock=unlimited status=nofile
Heap: heap=946,176 smbytes=199,240 max_bytes=199,434 bufs=120 max_bufs=122
Sizes: boffset_t=8 size_t=8 int32_t=4 int64_t=8 mode=0,0 newbsr=0
Crypto: fips=N/A crypto=OpenSSL 3.0.2 15 Mar 2022
Res: ndevices=1 nautochgr=1

Running Jobs:
Director connected using TLS at: 12-Oct-23 04:49
No Jobs running.


Jobs waiting to reserve a drive:


Terminated Jobs:


Device status:
Autochanger "FileChgrSLCO-BKPSTO-02" with devices:
FileChgrSLCO-BKPSTO-02-Dev01

Device "FileChgrSLCO-BKPSTO-02-Dev01" is not open or does not exist.
==


Used Volume status:




You have messages.


   *   It looks the aligned plugin is not loaded during the SD service restart. I tried 
to modify the rights to access to the plugin files. I also thried with the line 
"Media Type = Aligned" but without success, and no additional information is 
available in the logs.
I precise that this configuration is working well on the 11 version.

This is the last point before the migration from the old Bacula to this one, 
but really blocking.

Any help with be great.

Thanks.

Regards,

Christophe M.



Cegid est susceptible d'effectuer un traitement sur vos donn?es personnelles ? 
des fins de gestion de notre relation commerciale. Pour plus d'information, 

Re: [Bacula-users] Running backup job without file records in catalog

[Eric Bollengier via Bacula-users]

Hello,

On 9/28/23 12:17, Yateen Shaligram Bhagat (Nokia) wrote:

Hi All,

I would like to know if we can define a backup job (real or virtual) that DOES 
NOT put the file records in the catalog at all.


I believe that we have Pool directive to control that, something like 
CatalogFiles = yes/no


You may have a try, it's not very usual, but in some cases, it can help.

Best Regards,
Eric


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Adding missing foreign keys to PostgreSQL - avoiding dbcheck

[Eric Bollengier via Bacula-users]

Hello Dan,

On 10/3/23 21:01, Dan Langille wrote:

On Tue, Oct 3, 2023, at 1:45 PM, Eric Bollengier via Bacula-users wrote:

Hello Dan,

On 9/30/23 15:54, Dan Langille wrote:
Basically, each time you insert something, you need to query the other tables to
check the existence or not of records. The checks for the existence of the
records is already done at the bacula level one time per job, no real need to do
it one time per insertion/update/delete.


Is that one-time-per-job check done via a SELECT on the database? I should 
explain analyze that one too and see if we can optimize that.


Look the code, we get/create the fileset record, pool record, client, device,
... records when we start a job or load the configuration.

For Path, the query itself ensures that we have the proper records, it's
builtin.


For example, one index I have been using this index for years. I find it 
referenced[1] in the the 5.x documentation, but it is not part of the catalog 
creation.

  "file_jobid_idx" btree (jobid)

This index vastly improves the construction of the files, often going from 
hours to seconds. I don't recall when that index was added here, but building 
trees has never been an issue here.


This index is great, but it uses GB of space and it has a cost during the
insertion of the attributes. PostgreSQL can use the composed index on JobId,
PathId instead to locate records, so you may add it back if you want, but it's
not mandatory.


How many GB? Do we know? We can easily find out too.

bacula=# select pg_table_size('file_jobid_idx');
  pg_table_size
---
37937438720
(1 row)

That's about 40GB.  I'll check the explain analyse and see how things go and 
come up with cost. Right now, we have no data.

Some might say: if the cost > 0 it's not worth it. However, it is worth it, 
IMO. Databases are much better at enforcing relational integrity than code is. 
It's what they do.


When Marc Cousin and I have worked on the Batch insert procedures, we have
tested all these scenario including the FKEY, it was back in 2006 maybe.
PostgreSQL has done a lot of progress since and SSD are replacing spinning disks
for example, so it might be different, hard to say without a deep analysis with
a large data set.

Our complete analysis and wide range of tests that we did for a couple of months
ended with the code we have today.

Best Regards,
Eric


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Adding missing foreign keys to PostgreSQL - avoiding dbcheck

[Eric Bollengier via Bacula-users]

Hello Dan,

On 9/30/23 15:54, Dan Langille wrote:

Hello,

The Bacula PostgreSQL schema is missing several foreign keys (FK). Foreign keys 
are not a new database concept; they've been around for decades. They are 
reliable and robust.


Yes, it's robust, but Bacula is doing mass insertion, and here, the cost is
bigger than the benefits IMHO. Of course, if someone can run tests on a 
multi-billion record database and show us that the cost is around few %, we can

consider them.

Basically, each time you insert something, you need to query the other tables to
check the existence or not of records. The checks for the existence of the
records is already done at the bacula level one time per job, no real need to do
it one time per insertion/update/delete.


Wednesday, I started a dbcheck on a Bacula database. Granted, that database is 
19 years old and this is the first time I've run dbcheck (as far as I know). 
That dbcheck is still going. FYI, the dump to disk is about 140GB; lots of 
cruft removal.

When PostgreSQL was first added to Bacula, there was resistance to FK, and I 
did not pursue the issue. Thus, it persists to this day. I hope to change that.


I don't think they are necessary, we use transaction in the cleanup now days, so
orphan records should not exist anymore.


I would like to take that development work back up (pun intended), and start 
adding foreign keys back into Bacula, at least for PostgresQL. That might 
remove the need for dbcheck (again, at least for Bacula on PostgreSQL).


dbcheck is needed from time to time to purge the Path table mostly, other tables
should be ok with a recent version. Not sure the algorithms in dbcheck are
always the best ones to find a remove records.


For example, one index I have been using this index for years. I find it 
referenced[1] in the the 5.x documentation, but it is not part of the catalog 
creation.

 "file_jobid_idx" btree (jobid)

This index vastly improves the construction of the files, often going from 
hours to seconds. I don't recall when that index was added here, but building 
trees has never been an issue here.


This index is great, but it uses GB of space and it has a cost during the 
insertion of the attributes. PostgreSQL can use the composed index on JobId,

PathId instead to locate records, so you may add it back if you want, but it's
not mandatory.


I have no timeline for this work, but just posting the intent often gives me 
the incentive to get started.



1 - https://www.bacula.org/5.2.x-manuals/en/main/main/Catalog_Maintenance.html



Best Regards,
Eric


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] [Bacula-devel] Bacula Release 13.0.3

[Eric Bollengier via Bacula-users]

Hello Elias,

On 5/3/23 00:49, Elias Pereira wrote:

hello Eric,

Do you have a release date for Bacula Community Binaries 10.0.3?


I think that they are now all uploaded. We will run smoke tests to ensure that
everything can be installed properly, so they should be ok by Friday or early
next week.

Best Regards,
Eric


On Tue, May 2, 2023 at 4:47 PM Eric Bollengier via Bacula-devel <
bacula-de...@lists.sourceforge.net> wrote:


Hello,

We are pleased to announce the release of Bacula version 13.0.3 This is a
minor bugfix release of the new stable version. We recommend to upgrade to
this
version.

The new release 13.0 has many new features and a number of changes.
Please take care to test this code carefully before putting it
into production. The version 13.0.3 has some interesting new features
around the restricted console.

This release of Bacula uses a new catalog format.  We provide a set of
scripts that permit to convert a 11.x and earlier versions to the new
13.0 format (1024).  Normally, it is fast and automatic.

Note that converting from 9.x is a big change that takes longer than usual.
Beetween 9.x and 11.x, the upgrade process will require more or less twice
the size of the actual database on disk.

Please see the ReleaseNotes for how to build Bacula 13.0.3 with the
correct libs3 for use with the Amazon Cloud.

Most of the binaries (rpm, deb) are already ready, more should come
this week.

Thank you for using Bacula,
Eric

13.0.3 is a minor bug fix release with several new features and a number
of bug
fixes.

   - Fix #10030 About small issue while canceling the restore command

   - Fix #9968 Enhance restricted Console support
   - Fix #10032 Allow restore menu 1 to users without sqlquery command ACL
   - Fix #10033 Add extra Client and FileSet ACL checks to the estimate
command
   - Fix #9907 About Director crash with Runscript Console
   - Fix #9968 Adapt restore menu and add RBCLIENT/BCLIENT in some ACL SQL
checking
   - Fix small memory leak with setbandwidth command
   - Adapt delete, prune, purge commands to work with restricted consoles
   - Check ClientACL in acl_access_jobid_ok()
   - Check Pool specific ACL in select_media_dbr()
   - Disable Bootstrap manual selection in restore for Restricted Console
   - Do not display specific SQL errors to restricted consoles
   - Include BackupClient in list jobs, list jobmedia, list joblog
   - Restrict the use of local files during the restore file selection
process
when using a Restricted Console
   - Take the first valid FileSet for the restore Job with restricted
consoles

   - baculum: Add checking errors in output from vsphere plugin servers,
hosts
and datastores commands
   - baculum: Add new m365 plugin mailbox list endpoint
   - baculum: Add VMware vSphere datastore list endpoint
   - baculum: Add VMware vSphere host list endpoint
   - baculum: Add VMware vSphere restore host list endpoint
   - baculum: Add VMware vSphere server list endpoint
   - baculum: Add a new endpoint to list jobs together with objects
   - baculum: Add client filter to objects endpoint
   - baculum: Add client property to object and objects endpoint
   - baculum: Add client resnames endpoint
   - baculum: Add client, pool, fileset and fileset content properties to
jobs
objects endpoint
   - baculum: Add displaying bconsole command output if command is multiline
   - baculum: Add enabled flag filter to volumes endpoint
   - baculum: Add endpoint to list m365 jobs by email
   - baculum: Add endtime property and filters to source list endpoint
   - baculum: Add estimated job values endpoint that uses job historical
data for
estimation
   - baculum: Add fileindex parameter to bvfs restore endpoint
   - baculum: Add fileset and filesetid filters to jobs objects endpoint
   - baculum: Add fileset content property to sources endpoint output
   - baculum: Add job errors property to objects endpoint
   - baculum: Add job errors property to sources endpoint
   - baculum: Add job status property to objects endpoint
   - baculum: Add job type to sources endpoint
   - baculum: Add joberrors filter to jobs objects endpoint
   - baculum: Add joberrors filter to objects endpoint
   - baculum: Add mediaid to volume overview endpoint
   - baculum: Add method to execute SQL queries
   - baculum: Add more detailed output to restore endpoint
   - baculum: Add objectid parameter to Bvfs restore endpoint
   - baculum: Add objecttype parameter to jobs objects endpoint
   - baculum: Add offset and limit parameters to bvfs versions endpoint
   - baculum: Add offset parameter to filesets endpoint
   - baculum: Add offset parameter to m365 plugin email list endpoint
   - baculum: Add offset parameter to sources endpoint
   - baculum: Add options to configure preserving table settings
   - baculum: Add order_by and order_direction parameters to sources
endpoint
   - baculum: Add order_by and order_direction parameters to volumes
endpoint
   - baculum: Add order_by and order_direction 

[Bacula-users] Bacula Release 13.0.3

[Eric Bollengier via Bacula-users]

Hello,

We are pleased to announce the release of Bacula version 13.0.3 This is a
minor bugfix release of the new stable version. We recommend to upgrade to this
version.

The new release 13.0 has many new features and a number of changes.
Please take care to test this code carefully before putting it
into production. The version 13.0.3 has some interesting new features
around the restricted console.

This release of Bacula uses a new catalog format.  We provide a set of
scripts that permit to convert a 11.x and earlier versions to the new
13.0 format (1024).  Normally, it is fast and automatic.

Note that converting from 9.x is a big change that takes longer than usual.
Beetween 9.x and 11.x, the upgrade process will require more or less twice
the size of the actual database on disk.

Please see the ReleaseNotes for how to build Bacula 13.0.3 with the
correct libs3 for use with the Amazon Cloud.

Most of the binaries (rpm, deb) are already ready, more should come
this week.

Thank you for using Bacula,
Eric

13.0.3 is a minor bug fix release with several new features and a number of bug
fixes.

 - Fix #10030 About small issue while canceling the restore command

 - Fix #9968 Enhance restricted Console support
 - Fix #10032 Allow restore menu 1 to users without sqlquery command ACL
 - Fix #10033 Add extra Client and FileSet ACL checks to the estimate command
 - Fix #9907 About Director crash with Runscript Console
 - Fix #9968 Adapt restore menu and add RBCLIENT/BCLIENT in some ACL SQL 
checking
 - Fix small memory leak with setbandwidth command
 - Adapt delete, prune, purge commands to work with restricted consoles
 - Check ClientACL in acl_access_jobid_ok()
 - Check Pool specific ACL in select_media_dbr()
 - Disable Bootstrap manual selection in restore for Restricted Console
 - Do not display specific SQL errors to restricted consoles
 - Include BackupClient in list jobs, list jobmedia, list joblog
 - Restrict the use of local files during the restore file selection process 
when using a Restricted Console

 - Take the first valid FileSet for the restore Job with restricted consoles

 - baculum: Add checking errors in output from vsphere plugin servers, hosts 
and datastores commands

 - baculum: Add new m365 plugin mailbox list endpoint
 - baculum: Add VMware vSphere datastore list endpoint
 - baculum: Add VMware vSphere host list endpoint
 - baculum: Add VMware vSphere restore host list endpoint
 - baculum: Add VMware vSphere server list endpoint
 - baculum: Add a new endpoint to list jobs together with objects
 - baculum: Add client filter to objects endpoint
 - baculum: Add client property to object and objects endpoint
 - baculum: Add client resnames endpoint
 - baculum: Add client, pool, fileset and fileset content properties to jobs 
objects endpoint

 - baculum: Add displaying bconsole command output if command is multiline
 - baculum: Add enabled flag filter to volumes endpoint
 - baculum: Add endpoint to list m365 jobs by email
 - baculum: Add endtime property and filters to source list endpoint
 - baculum: Add estimated job values endpoint that uses job historical data for 
estimation

 - baculum: Add fileindex parameter to bvfs restore endpoint
 - baculum: Add fileset and filesetid filters to jobs objects endpoint
 - baculum: Add fileset content property to sources endpoint output
 - baculum: Add job errors property to objects endpoint
 - baculum: Add job errors property to sources endpoint
 - baculum: Add job status property to objects endpoint
 - baculum: Add job type to sources endpoint
 - baculum: Add joberrors filter to jobs objects endpoint
 - baculum: Add joberrors filter to objects endpoint
 - baculum: Add mediaid to volume overview endpoint
 - baculum: Add method to execute SQL queries
 - baculum: Add more detailed output to restore endpoint
 - baculum: Add objectid parameter to Bvfs restore endpoint
 - baculum: Add objecttype parameter to jobs objects endpoint
 - baculum: Add offset and limit parameters to bvfs versions endpoint
 - baculum: Add offset parameter to filesets endpoint
 - baculum: Add offset parameter to m365 plugin email list endpoint
 - baculum: Add offset parameter to sources endpoint
 - baculum: Add options to configure preserving table settings
 - baculum: Add order_by and order_direction parameters to sources endpoint
 - baculum: Add order_by and order_direction parameters to volumes endpoint
 - baculum: Add order_by and order_direction params to jobs objects endpoint
 - baculum: Add output parameter to run job endpoint
 - baculum: Add output parameter to run restore endpoint
 - baculum: Add overview parameter to job list endpoint
 - baculum: Add overview parameter to objects endpoint
 - baculum: Add pool filter to volumes endpoint
 - baculum: Add priorjobname parameter to jobs endpoint
 - baculum: Add priorjobname property to jobs endpoint
 - baculum: Add restore_host parameter to vsphere plugin datastores API endpoint
 - baculum: Add server parameter to 

Re: [Bacula-users] Failed to create el9 rpm package

[Eric Bollengier via Bacula-users]

Hello Guilherme,

On 3/15/23 15:58, Guilherme Santos wrote:

I'm having trouble creating the package. Below is the information about the 
environment and the error.

Environment

Operating System: Rocky Linux 9.1
Source code to package: bacula-9.4.4.tar.gz


In general, compiling an old software (9.4.4 is 4 years old) on a new system
is a long and painful process.

I would recommend to compile the new version 13.0 instead.

Best Regards,
Eric


Software to build the package: rpmdevtools rpmlint

- bacula.spec.in
# basic defines for every build
%define _release   0
%define _version   9.4.4
%define productbacula
%define depkgs_version 24Dec11
tcpwrappers 0
lzo 0

Command executed to create the binary .rpm package
$ rpmbuild -bb --define "build_rh9 1" --define "build_client_only 1" --define 
"build_mysql 1" ~/rpmbuild/SPECS/bacula.spec.in

Compiling bsnapshot.c
bsnapshot.c: In member function 'char* lvm::get_lv_from_dm(char*, POOLMEM**, 
u_int32_t*, u_int32_t*)':
bsnapshot.c:1123:32: error: 'major' cannot be used as a function
  1123 |if (maj == major(sp.st_rdev) &&
   |   ~^~~~
bsnapshot.c:1124:32: error: 'minor' cannot be used as a function
  1124 |min == minor(sp.st_rdev))
   |   ~^~~~
make: *** [Makefile:155: bsnapshot.o] Error 1
make: Leaving directory '/home/rpmbuild/BUILD/bacula-9.4.4/src/tools'
error: Bad exit status from /var/tmp/rpm-tmp.zfjnRT (%install)

RPM build errors:
 Macro expanded in comment on line 536: %{suse} && ! 0%{?opensuse_bs}
 Macro expanded in comment on line 537: %debug_package
 extra tokens at the end of %endif directive in line 715:  %endif   
# suse
 extra tokens at the end of %endif directive in line 720:  %endif   
# mdk
 extra tokens at the end of %endif directive in line 725:  %endif   
# !suse && !mdk
 extra tokens at the end of %endif directive in line 727:  %endif   
# ! usesystemd
 Bad exit status from /var/tmp/rpm-tmp.zfjnRT (%install)

LOG: /var/tmp/rpm-tmp.zfjnRT
# fix me - building enable-client-only installs files not included in 
bacula-client package
# Program docs not installed on client
rm -f $RPM_BUILD_ROOT/usr/share/man/man8/bacula-dir.8.gz
rm -f $RPM_BUILD_ROOT/usr/share/man/man8/bacula-sd.8.gz
rm -f $RPM_BUILD_ROOT/usr/share/man/man8/bcopy.8.gz
rm -f $RPM_BUILD_ROOT/usr/share/man/man8/bextract.8.gz
rm -f $RPM_BUILD_ROOT/usr/share/man/man8/bls.8.gz
rm -f $RPM_BUILD_ROOT/usr/share/man/man8/bscan.8.gz
rm -f $RPM_BUILD_ROOT/usr/share/man/man8/btape.8.gz
rm -f $RPM_BUILD_ROOT/usr/share/man/man8/dbcheck.8.gz
rm -f $RPM_BUILD_ROOT/usr/share/man/man8/bregex.8.gz
rm -f $RPM_BUILD_ROOT/usr/share/man/man8/bwild.8.gz
rm -f $RPM_BUILD_ROOT/usr/share/man/man1/bsmtp.1.gz
rm -f $RPM_BUILD_ROOT/opt/bacula/scripts/bacula
rm -f $RPM_BUILD_ROOT/opt/bacula/scripts/bacula_config
rm -f $RPM_BUILD_ROOT/opt/bacula/scripts/bacula-ctl-dir
rm -f $RPM_BUILD_ROOT/opt/bacula/scripts/bacula-ctl-sd
rm -f $RPM_BUILD_ROOT/opt/bacula/scripts/disk-changer
rm -f $RPM_BUILD_ROOT/opt/bacula/scripts/dvd-handler
rm -f $RPM_BUILD_ROOT/opt/bacula/scripts/mtx-changer
rm -f $RPM_BUILD_ROOT/opt/bacula/scripts/startmysql
rm -f $RPM_BUILD_ROOT/opt/bacula/scripts/stopmysql
rm -rf $RPM_BUILD_ROOT/opt/bacula/scripts/updatedb
rm -f $RPM_BUILD_ROOT/opt/bacula/scripts/bconsole
rm -f $RPM_BUILD_ROOT/opt/bacula/scripts/mtx-changer.conf
rm -f $RPM_BUILD_ROOT/opt/bacula/bin/bacula

 [ "%{buildarch}" = "noarch" ] || QA_CHECK_RPATHS=1 ;
 case "${QA_CHECK_RPATHS:-}" in [1yY]*) /usr/lib/rpm/check-rpaths ;; esac
 /usr/lib/rpm/check-buildroot



___
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] What is 'voltype'?

[Eric Bollengier via Bacula-users]

Hello,

The VolType is an internal field that corresponds to the device type,
and the device type list is defined in baconfig.h

enum {
   B_FILE_DEV = 1,
   B_TAPE_DEV = 2,
   B_DVD_DEV  = 3,
   B_FIFO_DEV = 4,
   B_VTAPE_DEV= 5,/* change to B_TAPE_DEV after init */
   B_FTP_DEV =  6,
   B_VTL_DEV =  7,/* Virtual tape library device */
   B_ADATA_DEV = 8,   /* Aligned data Data file */
   B_ALIGNED_DEV = 9, /* Aligned data Meta file */
...
};

When it is 0, it probably means that the volume was never used. Normally it's
handled automatically, so maybe you have a MediaType or a Pool issue.

Hope it helps!

Best Regards,
Eric

On 3/3/23 16:48, kjohn...@eclypse.org wrote:

Rob,

Thanks for this helpful reply.  It had not occurred to me to look through the 
configuration files.

As far as the current manual is concerned, "searches in main.pdf dated 14 Sep 2022 for 
"voltype" and "Volume Type" both came up empty."  Perhaps different search terms 
would have been more helpful.

I have not used Baculum or BWeb, so I cannot comment there.

It may be that my problem had nothing to do with voltype.  The volume I was 
using had recently been added to the pool, and had never been used in that 
pool.  Purging that volume allowed the backup to proceed when I restarted the 
job.  I did not foresee that an empty volume would need to be purged before use.

Ken



   
From: r...@craeon.net [mailto:r...@craeon.net]

Sent: Wednesday, March 01, 2023 3:22 PM
To: kjohn...@eclypse.org
Cc: bacula-users
Subject: Re: [Bacula-users] What is 'voltype'?

Voltype is an arbitrary name given to a certain type of volume. It must be consistent across all bacula 
configuration files. For example in my setup I have "LTO8" as a voltype. This references my actual 
LTO 8 tapes, but I could have named them anything, like "George" or "duck".

I kind of think that maybe a voltype "0" and "2" is not very informative for 
someone who must maintain the system.

I think (but can't remember for sure), voltype must be defined in SD conf and 
referenced in bacula director conf for each job.

Web tools like Baculum and BWeb may strip out all comments, making it more 
difficult to examine how bacula is configured.

I don't have it in front of me, but try to find the current manual pdf on the 
bacula website. I had to dig around to find the correct manual for my version.
Robert Gerber
402-237-8692
r...@craeon.net

On Wed, Mar 1, 2023, 1:12 PM  wrote:
bconsole list volume displays a field called 'voltype'.  What is this used for, 
and how can I set it?

Searches in main.pdf dated 14 Sep 2022 for "voltype" and "Volume Type" both 
came up empty.

I have a backup job that should run on a volume that has a voltype of 0, and it 
will not progress.  I observe that all other volumes in that pool have a 
voltype of 2.

Thanks.


Ken





___
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




___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] dbcheck, postgres, OOM...

[Eric Bollengier via Bacula-users]

Hello Marco,

On 2/27/23 16:50, Marco Gaiarin wrote:



I've tried to lieave more RAM to the VM that run the director (and the DB),
first 8, the 16 now i try with 32GB, but...


For the archive, with 32GB of RAM pstgres does not crash, but still cath an
out_of_memory condition (correctly) and abort the query.


How can i do? Thanks.



I would recommend to tune the database server correctly, PostgreSQL is smart
enough to use the resources that are allocated for any kind of query. When
running "out of memory", it will for example use the disk.

Maybe the disk is not correctly sized for your database? Maybe the Postgresql
configuration is not adequate? (the default work_mem was about 64k few versions
ago), etc...

Hope it helps!

Best Regards,
Eric


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

[Bacula-users] Bacula Release 13.0.2

[Eric Bollengier via Bacula-users]

Hello,

We are pleased to announce the release of Bacula version 13.0.12 This is a
minor bugfix release of the new stable version. We recommend to upgrade to this
version.

The new release 13.0 has many new features and a number of changes.
Please take care to test this code carefully before putting it
into production.

This release of Bacula uses a new catalog format.  We provide a set of
scripts that permit to convert a 11.x and earlier versions to the new
13.0 format (1024).  Normally, it is fast and automatic.

Note that converting from 9.x is a big change that takes longer than usual.
Beetween 9.x and 11.x, the upgrade process will require more or less twice
the size of the actual database on disk.

Please see the ReleaseNotes for how to build Bacula 13.0.2 with the
correct libs3 for use with the Amazon Cloud.

Most of the binaries (rpm, deb) are already ready, more should come
this week.

Thank you for using Bacula,

Eric

13.0.2 is a minor bug fix release.

 - Fix #9535 avoid "Will not descend from / to /good_dir"
 - Fix #9568 About "cancel inactive" command Storage Daemon selection
 - Fix #9614 Re-create Jobs with bscan only if the bootstrap is matching
 - Fix #9686 Grant PROCESS privilege to bacula user to allow catalog backup
 - Fix #9876 Update information printed during file restore error
 - Fix #9882 About tapealert script issue on rhel8
 - Fix Cython detection on python >= 3.8
 - Fix bconsole command issue after a first error
 - Fix errors in update_bacula_tables
 - Fix org#2577 Remove -f option from MySQL update scripts to detect errors 
properly
 - Fix org#2628 About improving the update_bacula_tables script on up to date 
catalogs

 - Fix org#2665 About memory leak on FreeBSD with extended attributes
 - Fix org#2666 About fixing getaddrinfo check in ./configure

 - baculum: Add afterjobid parameter to job list endpoint
 - baculum: Add jobids parameter to objects endpoint
 - baculum: Add plugin column
 - baculum: Add age parameter to jobs and objects endpoints
 - baculum: Add capability to restore using plugin
 - baculum: Add dedupengine output type to status storage
 - baculum: Add documentation for component actions
 - baculum: Add documentation to new job sort parameters
 - baculum: Add documentation to new jobids parameter in job list endpoint
 - baculum: Add event list and single event record endpoints
 - baculum: Add group_limit, order_by and order_direction parameters to objects 
endpoint

 - baculum: Add groupby parameter to object list endpoint
 - baculum: Add job sum statistics endpoint
 - baculum: Add jobids parameter to Bvfs update endpoint
 - baculum: Add missing objectid parameter to API documentation
 - baculum: Add multiple jobids filter to jobs endpoint
 - baculum: Add new fileindex property to objects
 - baculum: Add new filters to object category sum endpoint
 - baculum: Add new job, fileset and media properties support
 - baculum: Add object category stats endpoint
 - baculum: Add object category status endpoint
 - baculum: Add object size statistics endpoint
 - baculum: Add object versions endpoint
 - baculum: Add offset parameter to event and pool list endpoint
 - baculum: Add offset parameter to jobs, objects and volumes endpoints
 - baculum: Add offset parameter to messages endpoint
 - baculum: Add offset parameter to storage and client list endpoint
 - baculum: Add option to enable/disable audit log
 - baculum: Add patch for offset parameter support in SQL queries
 - baculum: Add query command support, object endpoint and m365 user list 
endpoint
 - baculum: Add restore plugin option fields endpoint
 - baculum: Add restore plugin options endpoint
 - baculum: Add search Bacula items endpoint
 - baculum: Add single object record endpoint
 - baculum: Add sources endpoint
 - baculum: Add time range parameters to jobs endpoint
 - baculum: Add time range parameters to objects endpoint
 - baculum: Add to jobs endpoint parameters to sort property and sort order
 - baculum: Fix OFFSET parameter in PHP framework
 - baculum: Fix sources endpoint double results
 - baculum: Fix time range filter for job and object endpoints
 - baculum: Fix using multiple job statuses in list jobs jobstatus filter
 - baculum: Fix using operators for SQL queries

 - cloud: Fix #8351 Catalog part number correction notification goes debug
 - cloud: Fix #9508 transfer remove dcr use for JobId
 - cloud: Fix #9606 Rearange POOLMEM usage in cb functions

 - k8s: Add support for Python3.10

 - win32: Fix org#2667 enable sockaddress_storage for windows
 - win32: Switch to openssl 1.1.1t

Bugs fixed/closed since last release:
 8351 9508 9535 9568 9606 9614 9686 9876 9882



___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] volume relabel

[Eric Bollengier via Bacula-users]

Hello,

On 1/18/23 11:47, Yateen Shaligram Bhagat (Nokia) wrote:

Hi all,

We are using disk based Bacula backup up. (9.4.4)

We want to archive older backups into a separate archive pool (with a long 
retention time) with no associated job record in the catalog.
We are doing it by migrating current backup job to an archive pool, then do a 
job purging from the archive volume.

Further we need to relabel the new archive volume with a specific name like 
archive_2022.
We tried it using the relabel command. (relabel oldvolume=xxx volume=yyy )

Observations:

1.  In the catalog, it renames the old volume name to a new volume name ; 
this is expected.

2.  However, on the storage side, the old disk volume got truncated to 254 
bytes, all the contents were lost .

Expectation was that on the storage side also the old volume will get renamed 
to a new volume with no loss of data.


relabel means that you rewrite a label to a volume, so the content is lost. If 
you want to rename a volume, I would suggest to take a different approach.


It's not in the Bacula's spirit to allow such operation (it might be difficult
to find back where is your data if you start to rename volumes).

You can still change the catalog Media table and move the physical file to
a new name for example.

Hope it helps!

Best Regards,
Eric


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Setting the to address for Bacula GDB traceback

[Eric Bollengier via Bacula-users]

Hello Dan,

On 11/7/22 02:00, Dan Langille wrote:

Hello,

I'm getting some traceback emails like this:

From: root@localhost
Subject: Bacula GDB traceback of bacula-dir on bacula.int.example.org
Sender: bac...@bacula.int.example.org
To: root@localhost

There is no 'root@localhost' defined with my bacula-dir configuation.

[bacula dan /usr/local/etc/bacula] % sudo grep root@localhost * 0:56:01
bacula-dir.conf:#  mail = root@localhost = all, !skipped, saved
bacula-dir.conf.sample:  mail = root@localhost = all, !skipped
bacula-dir.conf.sample:  operator = root@localhost = mount
bacula-dir.conf.sample:  mail = root@localhost = all, !skipped

The above are either comments or .sample - none should be active.

Where is this address coming from?


Sounds like a default value, perhaps the full Messages resource can
help here.

Best Regards,
Eric



___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Bacula-dir.conf as a csv

[Eric Bollengier via Bacula-users]

Hello Guilherme,

On 9/22/22 21:42, Guilherme Santos wrote:

Hey guys, what's up?

Has someone know if anyone made a script or something about that make the 
bacula-dir.conf as a csv? The idea to simplify what I have in my config and 
make some filters.


CSV I'm not sure it's possible so easily, but you can convert the configuration
to JSON and apply some filters. From JSON, you might get CSV more easily.

look bdirjson, bsdjson, bfdjson

Hope it helps!

Best Regards,
Eric



___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Broken link about Kubernetes plugin. Bacula 13.0.1.

[Eric Bollengier via Bacula-users]

Hello,

I believe that it's now fixed.

Best Regards,
Eric

On 9/14/22 17:01, Eric Bollengier via Bacula-users wrote:

Hello,

On 13.09.22 15:28, Douglas Vinicius Esteves wrote:

Hello!

I need to test the features of Bacula 13.0.1, the Kubernetes plugin.

Reading the material on Bacula.org[1] about the Features.

When I try to open the link: More information about the Kubernetes plugin can 
be found on (here[2]). The link is broken, does anyone have another link or 
any way to fix the content link?


This is a bug in the manual generation, the source file is present and included, 
so it should be rendered.


I need to have a look,

Thanks for the report.

Best Regards,

Eric




___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Broken link about Kubernetes plugin. Bacula 13.0.1.

[Eric Bollengier via Bacula-users]

Hello,

On 13.09.22 15:28, Douglas Vinicius Esteves wrote:

Hello!

I need to test the features of Bacula 13.0.1, the Kubernetes plugin.

Reading the material on Bacula.org[1] about the Features.

When I try to open the link: More information about the Kubernetes plugin can 
be found on (here[2]). The link is broken, does anyone have another link or 
any way to fix the content link?


This is a bug in the manual generation, the source file is present and included, 
so it should be rendered.


I need to have a look,

Thanks for the report.

Best Regards,

Eric



___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

[Bacula-users] Working for Bacula?

[Eric Bollengier via Bacula-users]

Hello,

If you like Bacula, maybe you would like to have the opportunity
to work for Bacula Systems and contribute to improve Bacula over
the time. We have two open positions for the moment, and you are
welcome to apply.

https://baculasystems.com/company/careers-at-bacula-systems/senior-technical-writer/

https://baculasystems.com/company/careers-at-bacula-systems/customer-support-engineer/

I'm looking forward to work with you!

Best Regards,
Eric


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

[Bacula-users] Bacula Status report - 30 August 2022

[Eric Bollengier via Bacula-users]

The topics for this Status Report are:

1. Bacula Release Status

2. Bacula Binaries

3. Windows Binaries

4. macOS Binaries

5. New Services

===

1. Bacula Release Status

The latest Bacula version 13.0.1 was released to Source Forge and to
www.bacula.org.  This version includes many enhancements to Baculum (the Web
GUI interface to Bacula), new Storage Group support for the Dir and the SD,
a Kubernetes plugin, a new Accurate option to update only meta data during
an incremental backup job, external LDAP support for Console and many more.


Note: The version 13.0.0 has a problem to start the Storage Daemon systemd
service.

2. Bacula Binaries
Thanks to the build support from Bacula Systems, we now have binaries for a
number of popular distributions.  If you need additional distributions,
please notify us on the bacula-users email list.

The release format is with standard packaging using debs rpms, ... that are
specific to each system.  However, unlike most Linux distributions, we
install the Community Binaries into the directory /opt/bacula as
recommended in the Bacula manual and as used by the Bacula Enterprise
Edition.  This Bacula file release standard is not uncommon and vastly
simplifies installation, support, backup and recovery of Bacula itself.
Basically, most of the release will be installed into /opt/bacula except
for the few system files that must be placed in certain locations such as
the start/stop scripts and the man text.

To register and get access to Bacula pre-built binaries please go to
www.bacula.org and on the main menu bar select Downloads -> Bacula Binary
Package Download, then fill out the registration.  Note, ultimately you
will receive a special download link that will give you access to the
binaries.  Please keep that link for future access to the binary repository
for updates and new releases.

3. Windows Binaries
They can be found in www.bacula.org -> Downloads -> Windows Binaries

4. macOS Binaries
New macOS packages can be found in www.bacula.org -> Downloads -> Deb, RPM and
OSx Packages

5. Project Services Update

Bacula.org server had a serious hardware issue in June. We have been able to
recover most of the data, and we have moved the services to a new location.  It
is now hosted by Bacula Systems in a secured environment. We are in the process 
of converting and upgrading our different web services (cgit, mantis, cdash, 
wiki) to an on-premise gitlab ultimate instance. This will take a bit of time

and I will keep you updated. If you have an account in Mantis, you will receive
an activation email for the new Gitlab instance.

Unfortunately, CDASH and the Wiki are still not available today - we anticipate 
these will be replaced by Gitlab. Indeed, the wiki has already been ported into

GitLab.

The archive of the Wiki is available on:
https://web.archive.org/web/20220125230419/https://wiki.bacula.org/doku.php

Thanks for using Bacula — be happy because there is much more to come!


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

[Bacula-users] Gitlab migration

[Eric Bollengier via Bacula-users]

Dear All,

As a valued member of the Bacula Community and a user of either Git or Mantis
bug tracker for Bacula Community, we would like to inform you that we have
started to migrate your mantis account and issues to the new GitLab instance.

The Gitlab instance, like the git repository and Mantis bug tracker is hosted by
Bacula Systems in Switzerland. Our IT team will be migrating issues from Mantis
to GitLab and we will also redirect the old git repository to be centralized in
our GitLab.

During this migration, please do not create new issues on Gitlab.

If you **DO NOT** want us to create an account in the new system for you, please
reply to the welcome message and gitlab will record your opt-out.

Thank you for using Bacula and we look forward to seeing you in the new
Community Edition Gitlab shortly.

Best Regards,
Eric


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Migrating from mariadb to postgresql

[Eric Bollengier via Bacula-users]

Hello Uwe,

On 25.08.22 14:25, Uwe Schuerkamp wrote:

Hi folks,

I'm trying (for educational purposes) to migrate an existing bacula
catalog to use with a postgres backend (mariadb10 / postgresql12,
Ubuntu 20.04).


I've imported the bacula catalog using pgloader and this config:

LOAD DATABASE
FROM mysql://bacula:X@localhost/bacula
INTO postgresql://bacula:X@localhost/bacula

WITH include drop, create tables, no truncate,
create indexes, reset sequences, foreign keys;


The import works fine, however when connecting to bacula 13.0.1 (compiled
from source for postgres use) I get the following message in bconsole:

25-Aug 14:08 zif-dir JobId 0: Warning: Encoding error for database
"bacula". Wanted SQL_ASCII, got UTF8


The database has to be created with the -E SQL_ASCII, it is done before

you load the catalog I believe. Make sure you use the create_bacula_database

script.


Bacula might have to store characters coming from the different clients 
(filename and


path mostly), and we have no guarantee that they will be in valid UTF8.

If you try to store only UTF8 filenames, it will be ok, but if one of your 
clients

is in ISO8859-15 for example, it will fail the attribute insertion.

So, the DB has to be created with this attribute.

An other way of solving the issue would have been to escape anything

coming from the client to valid UTF8, but instead, we have changed the

postgresql parameter.

Hope it helps!

Best Regards,

Eric



Most web searches are ancient so I'm wondering if the ASCII bit is
still a valid requirement? In bconsole, the volume, job and client
names all look quite funny when doing a stat dir and the volume isn't
found when I run a backup job (probably due to this encoding issue).


I've also checked the configure script for any options related to the
encoding, but could not find anything, also I've used the provided
create_postgres_database script to (hopefully) initialize the catalog
db in postgres with the correct encoding.

Is there anything I'm doing wrong? Please excuse my ignorance, as I'm
only now getting my feet wet with postgres especially w/r to the
mariadb import...

Thanks in advance & all the best,

Uwe





___
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] Q: ConnectToDirector not working as documented for FD Director directive

[Eric Bollengier via Bacula-users]

Hello Justin,

On 7/17/22 19:31, Justin Case wrote:

I eventually removed the 9.X FD (from the Debian standard repos) from this
Debian machine and installed the 13.X FD (from the Community Edition Debs).
Running it manually works fine, it connects to the Director (11.x) and the
backup job runs successfully.

There is one thing still unclear to me: From the Debian standard repos there
is still the /etc/init.d/bacula-fd script to start and stop the FD. However,
the pathes in the script fit where the standard repos install the FD
(/usr/sbin/bacula-fd) and its configuration (/etc/bacula/bacula-fd). Surely I
can edit /etc/init.d/bacula-fd to put in where the Community Edition Debs put
the FD and config.

My questions is this: does a proper bacula-fd service script for /etc/init.d
usually come with the Community Edition Debian Debs? (in my case it did not
seem so)


The good old SysV scripts are still in the source tree, but now that the
debian distro (and the others) have switched to systemd, the package will
no longer setup the sysv scripts.

I believe that the bacula-ctl-fd/dir/sd scripts are still provided with the
package, and they can be used to manage the services. Note that I would not
mix systemd and scripts at the same time, but you can probably use them.

Hope it helps!

Best Regards,
Eric


All the best, J/C


On 19. Jun 2022, at 14:36, Justin Case  wrote:

The Debian FDs are 9.x, the DIR and SD are 11.x. It is just 1 Debian FD
that needs ConnectToDirector, so I guess I just need to upgrade the FD on
this one host.


On 19. Jun 2022, at 13:49, Josh Fisher  wrote:

Debs are available from the www.bacula.org website. You can build from
source. I'm not sure what version is in the normal Debian repositories,
but I think it must be older than 11.0. You can see the version by
running bacula-fd -? from the command line. But to use the
ConnectToDirector feature, you will have to upgrade to version 11.x on
all clients and Director and Storage daemons.


On 6/17/22 17:35, Justin Case wrote:

That is the normal debian package “bacula-client”. Which other package
would I use instead?


On 17. Jun 2022, at 21:08, Josh Fisher  wrote:

You must have an old version of bacula-fd on the client. The
ConnectToDirector was implemented in version 11.0.


On 6/17/22 10:00, Justin Case wrote:

Yes, I tried to make sense of this error message, but there is no
other directive above director in this config file (see my other
email, I have attached the config file there).


On 17. Jun 2022, at 14:16, Josh Fisher 
wrote:

Did you follow the error message's suggestion? "Perhaps you left
the trailing brace off of the previous resource" (or A
previous resource in the bacula-fd.conf file) We would need to
see the entire bacula-fd.conf file in order to help.








___ 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 wiki down

[Eric Bollengier via Bacula-users]

Hello,

We are in the process to implement a gitlab instance to replace
some old pieces of our different services, it takes a bit of time.
Any help is welcome of course to convert documents.

For the time being, you can access the copy of the site here
https://web.archive.org/web/20220125230419/https://wiki.bacula.org/doku.phpd

Best Regards,
Eric

On 7/23/22 14:55, PenguinWhispererThe wrote:

Hi,

I used to have an article linked here:
https://wiki.bacula.org/doku.php?id=sshtunnel

However it seems the wiki.bacula.org domain is no longer working.
Will it come back?

Thanks in advance.






___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

[Bacula-users] Bacula Release 13.0.1

[Eric Bollengier via Bacula-users]

Hello,

We are pleased to announce the release of Bacula version 13.0.1. This is
a minor bugfix release of the new stable version.

The new release 13.0 has 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.

This release of Bacula uses a new catalog format.  We provide a set of
scripts that permit to convert a 11.x and earlier versions to the new
13.0 format (1024).  Normally, it is fast and automatic.

Note that converting from 9.x is a big change that takes longer than usual.
Beetween 9.x and 11.x, the upgrade process will require more or less twice
the size of the actual database on disk.

Please see the ReleaseNotes for how to build Bacula 13.0.1 with the
correct libs3 for use with the Amazon Cloud.

The binaries (rpm, deb) should be ready next week, but new features are not
all fully included (kubernetes).

Thank you for using Bacula,
Eric



Release 13.0.1 / 05 August 2022

13.0.1 is a minor bug fix release.

 - Fix org#2657 About startup problem for bacula-sd
 - Fix org#2594 About compilation warning on VolRead/WriteTime
 - Fix org#2644 Add support for binary files to bacula md5sum
 - Fix org#2655 About incorrect definition of MAX_FOPTS
 - Fix org#2656 About incorrect error message on TLS CA Certificate

 - baculum: Adapt code to use PSR-4 autoloader
 - baculum: Fix #2653 PHP warning about wrong array_key_exists() parameter in 
session record

 - baculum: Improve logging and add audit log

 - osx: Fix #9309 about extended attribute backup error on macOS
 - Rework MacOS package

 - rpms: Add kubernetes spec file
 - rpms: Add spec file for k8s tools
 - rpms: Fix cloud package
 - rpms: more work on docker and docker tools
 - win32: update openssl to 1.1.1q

Bugs fixed/closed since last release:
 2657 2594 2644 2655 2656 2653 9309


Complete ReleaseNotes are available here
https://www.bacula.org/bacula-release-13-0-1/


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] bacula-sd fails at startup, but runs OK with manual start

[Eric Bollengier via Bacula-users]

Hello Robert,

The issue can be solved by adding "Type=forking" to the service,
or adding -fT to the command line.

...
Type=forking
ExecStart=/opt/bacula...
...

Best Regards,
Eric

On 7/25/22 16:50, Robert Reihs wrote:

Issue Reported: https://bugs.bacula.org/view.php?id=2657

On Mon, Jul 25, 2022 at 4:37 PM Robert Reihs  wrote:


Hi,
I have the same problem with a newly bacula 13 installation on debian.
When modifying the systemctl to startup bacula-sd in foreground the service
starts fine. When removing it again service is  not starting and no error
messages shown. Only output in syslog:
Jul 25 16:21:48 localhost systemd[1]: Started Bacula Storage Daemon
service.
Jul 25 16:21:48 localhost systemd[1]: bacula-sd.service: Succeeded.
Also no trace file is generated. Settings
in /usr/lib/systemd/system/bacula-sd.service:
...
WorkingDirectory=/opt/bacula/working
ExecStart=/opt/bacula/bin/bacula-sd -dt -T -m -d 200 -c
/opt/bacula/etc/bacula-sd.conf
...
Best
Robert






___
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] Logwatch report

[Eric Bollengier via Bacula-users]

Hello Gestio,

On 6/23/22 11:25, Gestió Servidors wrote:

Hello,

I have copied scripts from "logwatch" bacula source folder, but when I run
"logwatch --debug High --service bacula --output stdout", logwatch doesn't
run fine because it can't locate "Logwatch.pm". It seems logwatch process
gets wells all logs files (I log some servers in some different files), but
when all files concatenated go by the perl pipe, it fails in this line:

Processing Service: bacula ( cat /var/cache/logwatch/logwatch.dSY3aBHv/bacula
|  /usr/bin/perl /etc/logwatch/scripts/shared/applybaculadate ''
|/usr/bin/perl /etc/logwatch/scripts/services/bacula) 2>&1


If I run this line manually, I get this error message:

Can't locate Logwatch.pm in @INC (you may need to install the Logwatch
module)


I believe that you need to install the logwatch package on your system.
Scripts are installed, but the base software is not.

Hope it helps!

Best Regards,
Eric


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Bacula Error Compiling S3 Libs in Ubuntu 22.0.4

[Eric Bollengier via Bacula-users]

Hello Wanderlei,

On 7/5/22 11:54, Wanderlei Huttel wrote:

Hello

I'm trying to compile Bacula S3 libs in Ubuntu 22.0.4 and I'm getting the
error below:
I removed the "-Werror" flag and it apparently compiles without errors only
warnings. Is it ok?


I believe it's ok, but the functions prototype have changed once again with
OpenSSL 3, this change requires to update almost all piece of code ever written
with openssl, including libs3 that is not so well maintained. We have a project
to replace libs3 with the aws command line program for the cloud driver, aws is
more likely to be supported, waiting for that, libs3 with your change is ok.

Best Regards,
Eric


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

[Bacula-users] Bacula Release 13.0.0

[Eric Bollengier via Bacula-users]

Hello,

We are pleased to announce the release of Bacula version 13.0.0. This is
a major release of the new stable version.

The new release 13.0 has 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.

This release of Bacula uses a new catalog format.  We provide a set of
scripts that permit to convert a 11.x and earlier versions to the new
13.0 format (1024).  Normally, it is fast and automatic.

Note that converting from 9.x is a big change that takes longer than usual.
Beetween 9.x and 11.x, the upgrade process will require more or less twice
the size of the actual database on disk.

Please see the ReleaseNotes for how to build Bacula 13.0.0 with the
correct libs3 for use with the Amazon Cloud.

The binaries (rpm, deb, macOS) should be ready, but new features are not
all yet included (kubernetes). Windows binaries are available
and they will be updated with OpenSSL 1.1.1q this week.

Thank you for using Bacula,
Eric

--

Release 13.0.0 04 July 2022

13.0.0 is a major release.

New Features:
-
 - Job 'Storage Group' support
 - Kubernetes plugin
 - New Accurate option to save only file's ACL and metadata
 - Windows CSV (Cluster Shared Volumes) support
 - More logging for daemon<->daemon connections in Job log 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 bconsole 'llist job' output
 - Check for IP SANs when verifying TLS certs
 - Clarify SD vbackup Device error message
 - Remove deprecated sbrk in MacOS and Windows
 - Add bconsole .jlist command to get JSON output from regular list commands
 - Ensure that the Director will reject catalog updates 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 bconsole .bvfs_lsfiles allfiles command

Main Fixes:
 - Fix org#2188 About the presence of FileSet and Pool directives in the Job
 - Fix Director crash for Client Initiated Backup
 - Fix Director crash for Migration Job
 - Fix incorrect output for the .status client command
 - Skip XATTR larger than MaximumNetworkBuffer
 - Fix deadlock when starting the Director with an improperly configured catalog
 - Fix Director crash caused by BAT
 - Fix org#2627 About Director 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 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 tools during loadPlugins()
 - Fix reload issue when a Job doesn't have a Pool defined
 - Fix Copy Job with SelectionType=PoolUncopiedJobs selecting Jobs from wrong 
Pool
 - Fix about checking for Storage being used for Job restart/resume
 - Fix about incorrect variable substitution with the query command
 - Fix org#2579 About incorrect JSON generated from empty Messages resource
 - Fix #9116: copy job missuses the client->FdStorageAddress directive
 - Fix org#2658 About segfault with bsdjson with incorrect parameters
 - Skip storage daemon detection if the information is not available in the BSR
 - alist: Fix for memory overflow access
 - Fix org#2659 Install dbcheck and bsmtp in 755
 - Fix org#2662 About SQLite migration script issue
 - snapshot: Adapt for BTRFS 5.17
 - snapshot: Fix snapshot delete/prune command
 - snapshot: Fix #9143 About snapshot not properly stored in the catalog
 - snapshot: Add support for new LVM 2.03.15
 - rpms: Fix org#2633 about log directory not created on Centos7

GUI:
 - 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: Fix #2667 keep original fileset options order
 - baculum: Add to install wizard pre-defined b*json tool paths for FreeBSD and 
older Debian/Ubuntu

 - baculum: Fix #2661 required parameter PHP error on PHP 8.0
 - baculum: Fix error calling method_exists() with non-objects on PHP 8
 - baculum: Fix clearing 

Re: [Bacula-users] Beta Release 11.3.4

[Eric Bollengier via Bacula-users]

Hello Olivier,

On 6/24/22 13:27, OLIVIER DELESTRE (Personnel) wrote:

Hi,

Before updating my production server in version 10.0.6, i want make a new test 
Vm ( CentOs 7.9 ) and Bacula 9.6.7, like the production.


it's 11.0.6, and RPMs are very different

I Use the New repo , 
https://www.bacula.org/packages/xxx/rpms/9.6.7/el7/x86_64/


RPMS packages for el7 are available now, we are working on debian/ubuntu.
It's working normally.


But when i install a conflict appear :

yum install bacula-postgresql.x86_64 ( i pre install psql before same error )

../..

Installation -> bacula-postgresql

Installation pour dépendances -> bacula-mysql

../..

Transaction check error:
   le fichier /opt/bacula/lib64/libbaccats-9.6.7.so entre en conflit avec les 
tentatives d'installation de bacula-postgresql-9.6.7-1.el7.x86_64 et 
bacula-mysql-9.6.7-1.el7.x86_64


...


You can install postgresql or mysql, but not both.

I don't remenber if i make something a few years ago, i don't think. But today i 
can t reinstall with this version ( and perhaps another so ).


I still in production envionnement with 9.6.7 until my backup server EOL.

Another way, perhaps use GiT.

Thx for the works


Stick with packages, they are pretty fine. Do a backup of the catalog and the 
configuration file, you can perhaps remove packages and install the new ones

if the upgrade procedure doesn't work (but it should).

Once done, you need to update the catalog structure with the 
update_bacula_tables + grant_bacula_privileges scripts.


Hope it helps!

Best Regards,
Eric




Le 15/06/2022 à 14:34, Eric Bollengier a écrit :

Hello,

On 6/15/22 14:26, Olivier Delestre wrote:

Hi,

Still in v 9.6.7 with the repo https://bacula.org/packages/5

an idea of the return of the site ?

Before i use Git but it's down too.


You can clone the repository from
https://www.bacula.org/git

The previous URL should work, but apparently not. Packages will be re-imported
in the next days.

Best Regards,
Eric


Thanks for your works.

A+

Le 03/06/2022 à 16:35, Eric Bollengier a écrit :

Hello Olivier,

On 6/3/22 15:51, OLIVIER DELESTRE (Personnel) wrote:

Hi,

What's the difference between 11.3.4 and 11.0.6 ? no, I would like to know 
if it is in beta for 11.0.6 ?


11.0.6 is the current *stable* version of Bacula.

11.3.4 is the last beta version of the next major release 13.0.0.

9.6.7 is the previous stable version of Bacula.

Hope it helps!

Best Regards,
Eric


I still with 9.6.7 in a production environnement.

Thanks for work.

Bye.

Le 03/06/2022 à 15:00, Eric Bollengier via Bacula-users a écrit :

Hello,

We are pleased to announce the new BETA release of the next major Bacula
version 11.3.4 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.4

This is the last 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.

We had a service outage this week and some of the bacula services are 
still not

fully recovered (cdash, wiki, packages). It should be resolved next week.

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.4

 - Fix #9127 About incorrect handling of the new Accurate 'o' option with
  multiple incremental jobs. Add support for ACL u

[Bacula-users] Package repository

[Eric Bollengier via Bacula-users]

Dear Bacula Community users,

We have not yet completed our maintenance of the bacula.org services and we have 
encountered some issues with it that slow us down to get back with all services 
to the community. We are very sorry for this inconvenience.


We expect to get the 11.0.6 RPM/Deb repository back this week.

Best Regards,
Eric



___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Beta Release 11.3.4

[Eric Bollengier via Bacula-users]

Hello,

On 6/15/22 14:26, Olivier Delestre wrote:

Hi,

Still in v 9.6.7 with the repo https://bacula.org/packages/5

an idea of the return of the site ?

Before i use Git but it's down too.


You can clone the repository from
https://www.bacula.org/git

The previous URL should work, but apparently not. Packages will be re-imported
in the next days.

Best Regards,
Eric


Thanks for your works.

A+

Le 03/06/2022 à 16:35, Eric Bollengier a écrit :

Hello Olivier,

On 6/3/22 15:51, OLIVIER DELESTRE (Personnel) wrote:

Hi,

What's the difference between 11.3.4 and 11.0.6 ? no, I would like to know if 
it is in beta for 11.0.6 ?


11.0.6 is the current *stable* version of Bacula.

11.3.4 is the last beta version of the next major release 13.0.0.

9.6.7 is the previous stable version of Bacula.

Hope it helps!

Best Regards,
Eric


I still with 9.6.7 in a production environnement.

Thanks for work.

Bye.

Le 03/06/2022 à 15:00, Eric Bollengier via Bacula-users a écrit :

Hello,

We are pleased to announce the new BETA release of the next major Bacula
version 11.3.4 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.4

This is the last 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.

We had a service outage this week and some of the bacula services are still not
fully recovered (cdash, wiki, packages). It should be resolved next week.

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.4

 - Fix #9127 About incorrect handling of the new Accurate 'o' option with
  multiple incremental jobs. Add support for ACL updates
 - Fix #9116: copy job missuses the client->FdStorageAddress directive
 - Fix org#2658 About segfault with bsdjson with incorrect parameters
 - Skip storage daemon detection if the information is not available in the BSR

 - snapshot: Adapt for BTRFS 5.17
 - snapshot: Fix snapshot delete/prune command
 - snapshot: Fix #9143 About snapshot not properly stored in the catalog
 - snapshot: Add support for new LVM 2.03.15

 - Fix org#2659 Install dbcheck and bsmtp in 755
 - Fix org#2662 About SQLite migration script issue

 - Fix query SQL provided in sample-query.sql
 - Fix compilation on s3 driver
 - Fix ./configure error with test-cpp.c
 - win32: Update to OpenSSL 1.1.1o

 - 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: Fix #2667 keep original fileset options order
 - baculum: Add to install wizard pre-defined b*json tool paths for FreeBSD 
and older Debian/Ubuntu

 - baculum: Fix #2661 required parameter PHP error on PHP 8.0
 - baculum: Fix error calling method_exists() with non-objects on PHP 8

Bugs fixed/closed since last release:
2633 2658 2659 2661 2662 2667 9116 9125 9127 9143




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 i

Re: [Bacula-users] Beta Release 11.3.4

[Eric Bollengier via Bacula-users]

Hello,

On 6/8/22 17:47, Bill Arlofski via Bacula-users wrote:

On 6/6/22 07:37, Josh Fisher wrote:


Why does this choice happen only at job start? I have always thought it
should occur at each volume selection, which might alleviate some of the
issues with concurrent jobs writing to multi-drive autochangers,
particularly when writing to the same pool. Much of the volume shuffling
between drives is simply because the job's storage device cannot be
reassigned. This would basically be assigning volume and device as an
atomic pair, meaning volume and device would always be assigned from
within a single critical section, probably where the volume selection
code is now. That pairing would persist as long as it was assigned to
one or more jobs.



Hello Josh!

I am not a developer, so can only answer your question with something along the 
lines of "this functionality was probably
decided and designed from the beginning, and some pretty major code changes 
would be required to make it as flexible as you

are describin
g."

I'd love to hear Eric or another of the developers voice their opinions from a 
technical and design point of view here,
including if there are any thoughts or plans to make such changes at any point 
in the future.




The feature described by Josh is indeed very exciting, however, the resource
are allocated/reserved at the job creation, and such dynamic allocation would
require a good amount of changes. Not impossible, but not part of the new 
version.

I don't know if I would be too happy to see my job spread over multiple places
within a single session, but that's true, if a storage resource becomes full,
it would be nice to continue elsewhere automatically (and maybe fill-up all
resources everywhere !)

Thanks for sharing the idea, thanks Bill for the answer!

Best Regards,
Eric


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Bacula Community packages repo, wiki and cdash are offline

[Eric Bollengier via Bacula-users]

Hello Wanderlei,

On 6/6/22 18:49, Wanderlei Huttel wrote:

Hello Eric

Have you ever think about create a git repository in https://github.com?


Git is distributed and can have multiple locations, so, github is interesting. I
have setup a gitlab project last month, but the project cannot apply to the
Open Source gitlab initiative (resources to run CI, to build packages etc...).
I'm not sure to continue with them, github is the next one to try. It might be
an opportunity to merge the code and the issue tracking.

Thanks for the input,
Eric


Best regards

*Wanderlei Hüttel*



Em seg., 6 de jun. de 2022 às 13:02, Eric Bollengier via Bacula-users <
bacula-users@lists.sourceforge.net> escreveu:


The git service is available on http://www.bacula.org/git/bacula but we

will

update the configuration with some redirect to stay compatible with what

it was

before. Thanks for the pointer.


Sorry, it's http://www.bacula.org/git or https://www.bacula.org/git for
the
moment.

Best Regards,
Eric


___
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 Community packages repo, wiki and cdash are offline

[Eric Bollengier via Bacula-users]

The git service is available on http://www.bacula.org/git/bacula but we will
update the configuration with some redirect to stay compatible with what it was
before. Thanks for the pointer.


Sorry, it's http://www.bacula.org/git or https://www.bacula.org/git for the
moment.

Best Regards,
Eric


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Bacula Community packages repo, wiki and cdash are offline

[Eric Bollengier via Bacula-users]

Hello Bill,

On 6/6/22 15:54, Bill Arlofski via Bacula-users wrote:

On 6/6/22 01:55, Eric Bollengier via Bacula-users wrote:

Hello,

We had a server outage with bacula.org last Friday and since then the server is
under heavy maintenance. We were able last week-end to bring back most of the
services, except:
- Bacula Community package repo
- the Bacula wiki
- cdash for regression tests

It will take us more days to have those services back online, we are sorry. We
will write back to the mailing list when available.

Best Regards,
Eric



Hello Eric,

Just in case you were not aware, git.bacula.org is also 'out' as it does not 
resolve:


8<---
$ git pull
fatal: unable to access 'http://git.bacula.org/bacula.git/': Could not resolve 
host: git.bacula.org

8<---



The git service is available on http://www.bacula.org/git/bacula but we will
update the configuration with some redirect to stay compatible with what it was
before. Thanks for the pointer.

Best Regards,
Eric


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

[Bacula-users] Bacula Community packages repo, wiki and cdash are offline

[Eric Bollengier via Bacula-users]

Hello,

We had a server outage with bacula.org last Friday and since then the server is 
under heavy maintenance. We were able last week-end to bring back most of the 
services, except:

- Bacula Community package repo
- the Bacula wiki
- cdash for regression tests

It will take us more days to have those services back online, we are sorry. We 
will write back to the mailing list when available.


Best Regards,
Eric


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Beta Release 11.3.4

[Eric Bollengier via Bacula-users]

Hello Olivier,

On 6/3/22 15:51, OLIVIER DELESTRE (Personnel) wrote:

Hi,

What's the difference between 11.3.4 and 11.0.6 ? no, I would like to know if it 
is in beta for 11.0.6 ?


11.0.6 is the current *stable* version of Bacula.

11.3.4 is the last beta version of the next major release 13.0.0.

9.6.7 is the previous stable version of Bacula.

Hope it helps!

Best Regards,
Eric


I still with 9.6.7 in a production environnement.

Thanks for work.

Bye.

Le 03/06/2022 à 15:00, Eric Bollengier via Bacula-users a écrit :

Hello,

We are pleased to announce the new BETA release of the next major Bacula
version 11.3.4 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.4

This is the last 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.

We had a service outage this week and some of the bacula services are still not
fully recovered (cdash, wiki, packages). It should be resolved next week.

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.4

 - Fix #9127 About incorrect handling of the new Accurate 'o' option with
  multiple incremental jobs. Add support for ACL updates
 - Fix #9116: copy job missuses the client->FdStorageAddress directive
 - Fix org#2658 About segfault with bsdjson with incorrect parameters
 - Skip storage daemon detection if the information is not available in the BSR

 - snapshot: Adapt for BTRFS 5.17
 - snapshot: Fix snapshot delete/prune command
 - snapshot: Fix #9143 About snapshot not properly stored in the catalog
 - snapshot: Add support for new LVM 2.03.15

 - Fix org#2659 Install dbcheck and bsmtp in 755
 - Fix org#2662 About SQLite migration script issue

 - Fix query SQL provided in sample-query.sql
 - Fix compilation on s3 driver
 - Fix ./configure error with test-cpp.c
 - win32: Update to OpenSSL 1.1.1o

 - 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: Fix #2667 keep original fileset options order
 - baculum: Add to install wizard pre-defined b*json tool paths for FreeBSD 
and older Debian/Ubuntu

 - baculum: Fix #2661 required parameter PHP error on PHP 8.0
 - baculum: Fix error calling method_exists() with non-objects on PHP 8

Bugs fixed/closed since last release:
2633 2658 2659 2661 2662 2667 9116 9125 9127 9143




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

[Bacula-users] Beta Release 11.3.4

[Eric Bollengier via Bacula-users]

Hello,

We are pleased to announce the new BETA release of the next major Bacula
version 11.3.4 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.4

This is the last 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.

We had a service outage this week and some of the bacula services are still not
fully recovered (cdash, wiki, packages). It should be resolved next week.

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.4

 - Fix #9127 About incorrect handling of the new Accurate 'o' option with
  multiple incremental jobs. Add support for ACL updates
 - Fix #9116: copy job missuses the client->FdStorageAddress directive
 - Fix org#2658 About segfault with bsdjson with incorrect parameters
 - Skip storage daemon detection if the information is not available in the BSR

 - snapshot: Adapt for BTRFS 5.17
 - snapshot: Fix snapshot delete/prune command
 - snapshot: Fix #9143 About snapshot not properly stored in the catalog
 - snapshot: Add support for new LVM 2.03.15

 - Fix org#2659 Install dbcheck and bsmtp in 755
 - Fix org#2662 About SQLite migration script issue

 - Fix query SQL provided in sample-query.sql
 - Fix compilation on s3 driver
 - Fix ./configure error with test-cpp.c
 - win32: Update to OpenSSL 1.1.1o

 - 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: Fix #2667 keep original fileset options order
 - baculum: Add to install wizard pre-defined b*json tool paths for FreeBSD and 
older Debian/Ubuntu

 - baculum: Fix #2661 required parameter PHP error on PHP 8.0
 - baculum: Fix error calling method_exists() with non-objects on PHP 8

Bugs fixed/closed since last release:
2633 2658 2659 2661 2662 2667 9116 9125 9127 9143




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 

Re: [Bacula-users] query.sql

[Eric Bollengier via Bacula-users]

Hello Phil and Giuseppe,

Thanks for the fix and the review, I will fix the current query file.

It will be included in the next beta 11.3.4 that is almost ready.

Best Regards,

Eric

On 25.05.22 21:24, Phil Stracchino wrote:

On 5/25/22 13:23, SO Giuseppe - COMAE via Bacula-users wrote:

SELECT count(*) AS Jobs,sum(JobFiles) AS Files,sum(JobBytes) AS Bytes,VolumeName
FROM (SELECT DISTINCT Jobmedia.JobId, JobFiles, JobBytes, VolumeName
       FROM Job,JobMedia,Media
       WHERE JobMedia.JobId=Job.JobId
       AND JobMedia.MediaId=Media.MediaId) AS f
GROUP BY VolumeName
ORDER BY VolumeName;



MySQL 127.0.0.1> SELECT count(*) AS Jobs,sum(JobFiles) AS Files,sum(JobBytes) 
AS Bytes,VolumeName

    -> FROM (SELECT DISTINCT Jobmedia.JobId, JobFiles, JobBytes, VolumeName
    ->   FROM Job,JobMedia,Media
    ->   WHERE JobMedia.JobId=Job.JobId
    ->   AND JobMedia.MediaId=Media.MediaId) AS f
    -> GROUP BY VolumeName
    -> ORDER BY VolumeName;
ERROR 1054 (42S22): Unknown column 'Jobmedia.JobId' in 'field list'

Straightforward typo in line 3.  You have Jobmedia instead of JobMedia.


With the typo fixed, yes, this yields much more reasonable and correct-looking 
results.






___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

[Bacula-users] Beta Release 11.3.3

[Eric Bollengier via Bacula-users]

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] Error when compiling Bacula 11.3

[Eric Bollengier via Bacula-users]

Hello,

On 4/22/22 04:49, Wanderlei Huttel wrote:

Hello Eric!

Thanks for your fix. Now it worked.
Taking advantage of this email, is the documentation for version 11.3
complete on the site or has it not been updated yet?


The documentation is available in the tar.bz2 file for the moment and
in the git repository. It is not yet published on the web site.

Best Regards,
Eric


Best regards

*Wanderlei Hüttel*



Em qui., 21 de abr. de 2022 às 06:39, Eric Bollengier <
e...@baculasystems.com> escreveu:


Hello Wanderlei,

I have just pushed a fix for this compilation issue,

can you update and retry?

Thanks,

Best Regards,

Eric

On 21.04.22 01:47, Wanderlei Huttel wrote:

Hello
I'm trying to compile Bacula as I always do, now in Debian GNU/Linux 11
(bullseye), and I'm getting an error.

config.out
==
Configuration on Wed Apr 20 20:33:26 -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: /var/run
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 support:  yes
LZO support:   yes
S3 support:yes
enable-smartalloc: yes
enable-lockmgr:no
bat support:   no
client-only:   no
build-dird:yes
build-stored:  yes
Plugin support:yes
LDAP support:  no
LDAP StartTLS support: no
AFS support:   no
ACL support:   yes
XATTR support: yes
GPFS support:  no
systemd support:   yes /lib/systemd/system
Batch insert enabled:  PostgreSQL

Plugins:
- Docker:  no
- Kubernetes:
- LDAP BPAM:   no
- CDP: auto
==

make -j 8

==
LT Compiling org_libsd_filemedia.c
LT Compiling org_libsd_quota.c
LT Compiling org_libsd_sir.c
LT Compiling cloud_parts.c
LT Compiling cloud_transfer_mgr.c
LT Compiling cloud_dev.c
LT Compiling file_driver.c
make[1]: *** Sem regra para processar o alvo 'bee_s3_cloud_glacier.lo',
necessário por 'bacula-sd-cloud-glacier-s3-driver.la
' .  Pare.
make[1]: ** Esperando que outros processos terminem.
LT Compiling s3_driver.c
make[1]: Saindo do diretório '/usr/src/bacula/bacula/src/stored'

   == Error in /usr/src/bacula/bacula/src/stored ==

make: *** [Makefile:162: all] Erro 1
root@debian:/usr/src/bacula/bacula# git status
On branch Branch-11.3
Your branch is up to date with 'origin/Branch-11.3'.
==



Best regards

*Wanderlei Hüttel*



___
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] Error when compiling Bacula 11.3

[Eric Bollengier via Bacula-users]

Hello Wanderlei,

I have just pushed a fix for this compilation issue,

can you update and retry?

Thanks,

Best Regards,

Eric

On 21.04.22 01:47, Wanderlei Huttel wrote:

Hello
I'm trying to compile Bacula as I always do, now in Debian GNU/Linux 11 
(bullseye), and I'm getting an error.


config.out
==
Configuration on Wed Apr 20 20:33:26 -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:             /var/run
   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 support:              yes
   LZO support:               yes
   S3 support:                yes
   enable-smartalloc:         yes
   enable-lockmgr:            no
   bat support:               no
   client-only:               no
   build-dird:                yes
   build-stored:              yes
   Plugin support:            yes
   LDAP support:              no
   LDAP StartTLS support:     no
   AFS support:               no
   ACL support:               yes
   XATTR support:             yes
   GPFS support:              no
   systemd support:           yes /lib/systemd/system
   Batch insert enabled:      PostgreSQL

   Plugins:
   - Docker:                  no
   - Kubernetes:
   - LDAP BPAM:               no
   - CDP:                     auto
==

make -j 8

==
LT Compiling org_libsd_filemedia.c
LT Compiling org_libsd_quota.c
LT Compiling org_libsd_sir.c
LT Compiling cloud_parts.c
LT Compiling cloud_transfer_mgr.c
LT Compiling cloud_dev.c
LT Compiling file_driver.c
make[1]: *** Sem regra para processar o alvo 'bee_s3_cloud_glacier.lo', 
necessário por 'bacula-sd-cloud-glacier-s3-driver.la 
' .  Pare.

make[1]: ** Esperando que outros processos terminem.
LT Compiling s3_driver.c
make[1]: Saindo do diretório '/usr/src/bacula/bacula/src/stored'

  == Error in /usr/src/bacula/bacula/src/stored ==

make: *** [Makefile:162: all] Erro 1
root@debian:/usr/src/bacula/bacula# git status
On branch Branch-11.3
Your branch is up to date with 'origin/Branch-11.3'.
==



Best regards

*Wanderlei Hüttel*



___
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

[Bacula-users] Beta Release 11.3.2

[Eric Bollengier via Bacula-users]

Hello,

We are pleased to announce the first BETA release of the next major Bacula
version 11.3.2 to both the Bacula website (www.bacula.org) and to SourceForge.

https://www.bacula.org/downloads/Beta-Bacula-11.3.2

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



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 tools duing loadPlugins()
 - Fix reload issue when a Job doesn't have a Pool defined
 - Fix Copy job with SelectionType=PoolUncopiedJobs selects jobs from wrong pool
 - Fix about checking for Storage being used for job restart/resume
 - Fix about incorrect variable substitution with the query command
 - Fix org#2579 About incorrect JSON generated from empty Messages resource
 - alist: Fix for memory overflow access

Please see the New Features chapter of the manual for documentation on
the new features.

https://www.bacula.org/downloads/Beta-Bacula-11.3.2/bacula-11.3.2-main.pdf


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

[Bacula-users] Release 11.0.6

[Eric Bollengier via Bacula-users]

Hello,

We are pleased to announce the release of Bacula version 11.0.6. This is
animportant bug and security fix release  of the stable version. We advise
all users of 11.0.x to upgrade to this version.

The 11.0.x series of Bacula uses a new catalog format.  We provide a set of
scripts that permit to convert a 9.x and earlier versions to the new
11.0 format (1023).  Normally, it is automatic, though this is a big
change that takes longer than usual. The upgrade process will require
more or less twice the size of the actual database on disk.

Please see the ReleaseNotes for how to build Bacula 11.0.6 with the
correct libs3 for use with the Amazon Cloud.

The binaries (rpm, deb) should be ready in a week or two.

The next beta cycle for 13.0 will start soon, I will keep you
updated.

Thank you for using Bacula,
Eric



Release 11.0.6 10 March 2022

11.0.6 is an important bug fix and security fix release.
We advise all 11.0.x users to upgrade to this version.

 - Adjust sample-query.sql file for new catalog schema
 - Fix #2654 About compilation issue on Alpine Linux
 - Fix #2656 About segfault in XATTR code for FreeBSD
 - Fix #7776 About FD error not correctly reported in the job log
 - Fix #7998 About dir crashing for client intiated backup
 - Fix #8126 About strange ouput for the .status client command
 - Fix MySQL default connection in the grant_mysql_privileges script
 - Fix db_get_accurate_jobids() with concurrent queries on the same jobs
 - Fix issue with MySQL 8 in src/cats/grant_mysql_privileges
 - Fix detection of PSK
 - Fix org#2622 About incorrect behavior of the MaxDiffInterval directive
 - Fix org#2623 About .ls/estimate command not printing files correctly
 - Fix org#2627 About DIR crashing for copy jobs and resource rename

 - win32: Upgrade OpenSSL to 1.1.1m

 - Got regression testing working correctly on FreeBSD

 - Update depkgs version to use latest libs3

 - baculum: Add API endpoints for basic user management
 - baculum: Add JSON output parameter to show client(s), show job(s), show 
pool(s) API endpoints
 - baculum: Add capability to assign dedicated bconsole config file to API 
basic users
 - baculum: Add capability to close modal windows on clicking gray shadow
 - baculum: Add capability to provide translated directive documentation file
 - baculum: Add capability to use pre-defined paths in API config wizard - idea 
proposed by Heitor Faria
 - baculum: Add console page to configure consoles
 - baculum: Add copy resource function to enable duplicating resources
 - baculum: Add director show API endpoint
 - baculum: Add documentation for directives
 - baculum: Add interface to manage basic users API from Web component side
 - baculum: Add jump to previous/next error navigation in messages window
 - baculum: Add new columns to job list page - idea proposed by Sergey Zhidkov
 - baculum: Add option to enable/disable messages log window - idea proposed by 
Bill Arlofski
 - baculum: Add password generator added to password fields
 - baculum: Add time range filters to job history page - idea proposed by 
Heitor Faria
 - baculum: Add to API deleting volume from the catalog endpoint
 - baculum: Add to config API endpoint parameter to apply jobdefs in results
 - baculum: Add to directive controls option to hide reset button and remove 
button
 - baculum: Add warning to running job status if job needs media
 - baculum: Apply PRADO framework patches to support PHP 8
 - baculum: Backup job wizard improvements
 - baculum: Change buttons on dasboard page - reported by Sergey Zhidkov
 - baculum: Do not require using some job resource values to ease using jobdefs 
- idea proposed by Heitor Faria
 - baculum: Enlarge boxes with resource count in status director - reported by 
Sergey Zhidkov
 - baculum: Fix #2642 add tool to re-assigning volumes from one pool to another
 - baculum: Fix #2646 apply new user permissions immediately instead of after 
logging out and logging in
 - baculum: Fix #2647 PHP warning about headers already sent on storage view 
page
 - baculum: Fix #2653 create new resource by copying configuration from other 
resource
 - baculum: Fix auto-scrolling in windows with configuration
 - baculum: Fix component autochanger schemas in OpenAPI documentation
 - baculum: Fix displaying directive sections in resouce configuration
 - baculum: Fix displaying documentation for jobdefs directives
 - baculum: Fix displaying issue in restore browser - reported by Sergey Zhidkov
 - baculum: Fix error about expected port number when writing component main 
resource
 - baculum: Fix legend in job status pie chart on job view page
 - baculum: Fix loading dashboard page if job status is created but not yet 
running
 - baculum: Fix missing texts in translation files - reported by Sergey Zhidkov
 - baculum: Fix opening job details in job table on main dashboard page - 
reported by Sergey Zhidkov
 - baculum: Fix problem with listing 

Re: [Bacula-users] Too Big? 11.0.5/FreeBSD Ports

[Eric Bollengier via Bacula-users]

Hello Larry,

It usually comes from a protocol error between the two hosts, here can you be a 
bit more precise on the os/cpu of the storage daemon and the FileDaemon. If one 
is little endian and the other one bigendian for example, it might show a 
problem. The filedaemon has sent a packet that was not correct for the SD, maybe 
some debug at the low level with the "setdebug level=1900 tag=network trace=1 
client" can identify the faulty message. It will generate a lot of output, so 
you might open a bug request on bugs.bacula.org and post the traces that are 
around the error.


Hope it helps!

Best Regards,

Eric


On 08.02.22 23:26, Larry Rosenman wrote:

Greetings,

Any ideas why a full backup got the following?

08-Feb 13:39 borg-dir JobId 4941: Start Backup JobId 4941, 
Job=thebighonker.2022-02-08_13.39.45_07

08-Feb 13:39 borg-dir JobId 4941: Using Device "FileStorage-2" to write.
08-Feb 15:14 thebighonker-fd JobId 4941:  Could not stat 
"/var/db/solr/dovecot/data/index/_1c68n.fdt": ERR=No such file or directory
08-Feb 15:14 thebighonker-fd JobId 4941:  Could not stat 
"/var/db/solr/dovecot/data/index/_1c68m_Lucene84_0.tip": ERR=No such file or 
directory
08-Feb 15:18 thebighonker-fd JobId 4941:  Could not stat 
"/var/db/solr/dovecot/data/index/_1c68r_Lucene84_0.pos": ERR=No such file or 
directory
08-Feb 15:18 thebighonker-fd JobId 4941:  Could not stat 
"/var/db/solr/dovecot/data/index/_1c68n.fdm": ERR=No such file or directory
08-Feb 15:18 thebighonker-fd JobId 4941:  Could not stat 
"/var/db/solr/dovecot/data/index/_1c68p.nvd": ERR=No such file or directory
08-Feb 15:19 thebighonker-fd JobId 4941:  Could not stat 
"/var/db/solr/dovecot/data/index/_1c68m.nvm": ERR=No such file or directory
08-Feb 15:19 thebighonker-fd JobId 4941:  Could not stat 
"/var/db/solr/dovecot/data/index/_1c68p_Lucene84_0.doc": ERR=No such file or 
directory
08-Feb 15:19 thebighonker-fd JobId 4941:  Could not stat 
"/var/db/solr/dovecot/data/index/_1c68n_Lucene84_0.doc": ERR=No such file or 
directory
08-Feb 15:19 thebighonker-fd JobId 4941:  Could not stat 
"/var/db/solr/dovecot/data/index/_1c68p.fdx": ERR=No such file or directory
08-Feb 15:19 thebighonker-fd JobId 4941:  Could not stat 
"/var/db/solr/dovecot/data/index/_1c68r_Lucene84_0.tmd": ERR=No such file or 
directory

08-Feb 15:28 borg-sd: ERROR in bget_msg.c:97 bget_msg: unknown signal -915791891
08-Feb 15:28 borg-sd JobId 4941: Fatal error: bsock.c:530 Packet 
size=314127059 too big from 
"client:[2001:470:1f0f:3ad:a2ea:ea0f:f8f7:65ac%2347267648]:9103". Maximum 
permitted 100. Terminating connection.
08-Feb 15:28 borg-sd JobId 4941: Elapsed time=01:48:53, Transfer rate=5.675 M 
Bytes/second
08-Feb 15:28 thebighonker-fd JobId 4941: Error: bsock.c:391 Write error 
sending 58003 bytes to Storage daemon:borg.lerctr.org:9103: ERR=Broken pipe
08-Feb 15:28 thebighonker-fd JobId 4941: Fatal error: backup.c:912 Network 
send error to SD. ERR=Broken pipe
08-Feb 15:28 thebighonker-fd JobId 4941: Error: bsock.c:276 Socket has 
errors=1 on call to Storage daemon:borg.lerctr.org:9103

08-Feb 15:29 borg-dir JobId 4941: Error: Bacula borg-dir 11.0.5 (03Jun21):
  Build OS:   amd64-portbld-freebsd14.0 freebsd 14.0-CURRENT
  JobId:  4941
  Job:    thebighonker.2022-02-08_13.39.45_07
  Backup Level:   Full
  Client: "thebighonker-fd" 11.0.5 (03Jun21) 
amd64-portbld-freebsd13.0,freebsd,13.0-STABLE

  FileSet:    "Full Set ZFS" 2021-12-05 23:05:00
  Pool:   "Default" (From Job resource)
  Catalog:    "MyCatalog" (From Client resource)
  Storage:    "File" (From Job resource)
  Scheduled time: 08-Feb-2022 13:39:39
  Start time: 08-Feb-2022 13:39:52
  End time:   08-Feb-2022 15:28:59
  Elapsed time:   1 hour 49 mins 7 secs
  Priority:   10
  FD Files Written:   45,478
  SD Files Written:   45,478
  FD Bytes Written:   37,073,692,075 (37.07 GB)
  SD Bytes Written:   37,079,274,728 (37.07 GB)
  Rate:   5662.7 KB/s
  Software Compression:   61.7% 2.6:1
  Comm Line Compression:  None
  Snapshot/VSS:   no
  Encryption: no
  Accurate:   yes
  Volume name(s): LERCTR-0202
  Volume Session Id:  3
  Volume Session Time:    1644296781
  Last Volume Bytes:  55,996,413,364 (55.99 GB)
  Non-fatal FD errors:    12
  SD Errors:  1
  FD termination status:  Error
  SD termination status:  Error
  Termination:    *** Backup Error ***


this is NOT a version mismatch.




___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] windows AD & NTFS acls restore

[Eric Bollengier via Bacula-users]

Hello Lionel,

On 18.01.22 10:27, Lionel PLASSE wrote:

Ok

The file daemon : 9.6.6 (20Sep20) Microsoft Standard Edition (build 9200), 
64-bit,Cross-compile,Win64
  is under windows server 2012-r2.
I backup the entire  c:\ (wilddir certain non essential directory)

I then restore the c: drive on a NTFS partitioned drive  on the  linux  Bacula 
server (directly on a ntfs drive mounted  on a /restore dir)  and I after plug 
the drive onto my windows server (for disaster recovery),
It does not recovered NTFS acls

I've made a script which backup acls with iacls  prior the backup (results in  
a txt file into the backup that I restore  after with ialcs in safe mode). It 
works and I have a procedure to rebuild manually the bootloader, so I can deal 
with it.

Maybe  my mount point interferes during the restore job?
I will retest later, And check all the steps. It is a bit complex but it works, 
waiting I find the time to study this  case in details (sorry for my English)


You have raised the reason why it is not working. If you restore on a Windows, 
you will get the attributes back. If you restore on a CIFS mount, it will not be 
restored, and even some parameters like the user/group will depend on the user 
used to mount the share. It's very primitive. Recent versions of Samba can map 
windows attributes to extended attributes, but I think you need to backup & 
restore from the same CIFS share, and it's not your goal.


The solution to the problem is to dump attributes and restore them afterward, 
well done.


Best Regards,

Eric



___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] windows AD & NTFS acls restore

[Eric Bollengier via Bacula-users]

Hello Lionel,

On 12/24/21 11:15, Lionel PLASSE wrote:

Hello,

For backup/restoration of windows systems.

Is it possible to backup all ACLS for the NTFS partitions. I activated
ACLSupport & XattrSupport in FileSets but when restoring I only have
Everybody Full Control for all files and directory. ? What is the correct
manner for backing up ntfs acls infos? It is really a problem for disaster
restoring a windows server domain controller. I achieve it (for test) and
recreate the UEFI Bootloader manually   but the c:\ system files don't have
the correct permissions. It could be great if it were possible



It is not very clear how you are trying to backup the NTFS partition. If your
file daemon is running on Windows, the backup of the ACLs is automatic (unless
you have set the portable=yes option in the fileset). You have nothing special
to do. The ACL and Xattr support options are for Linux/Unix systems.

Hope it helps,

Best Regards,
Eric


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Postgres table named "Filename"

[Eric Bollengier via Bacula-users]

Hello Serge,

On 1/14/22 15:15, UGE Serge (FR2010) wrote:



Hello,

I was running Bacula 9.6.5-1 on Centos 8.4 since July 2020, and in the 
"make_postgresql_tables" script there was this table in particular:

CREATE TABLE Filename

which was described in the Catalog Schema in the document Bacula Community API.

Now I run Bacula 11.0.5-1 since August 2021 and the table "Filename" does not 
appear any more in the installation scripts.

I checked the new docs but I did not found anything about this.
Can you indicate me if a replacement table exists or if it is a new structure of the 
catalog, or if there is a miss in my distribution "make_postgresql_tables" 
script ?


This table no longer exists in the catalog, you need to run the upgrade 
procedure described in the manual with update_bacula_tables + 
grant_bacula_privileges. Depending on the catalog size, it can take some time.


If you had custom queries using this table, you need to update them. The 
Filename information is now directly in the File table. (FilenameId -> Filename)


Hope it helps!

Best Regards,
Eric


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Why isn't bacula recycling these volumes?

[Eric Bollengier via Bacula-users]

Hello Larry,

On 12/8/21 15:08, Larry Rosenman wrote:
I have a bunch of volumes that bacula seems to have forgotten about. Can you 
explain why?


Also, what SQL/etc can I do to fix it?

Attached are a DB list for the volumes, and the ls -l.


Normally the information about the pruning/recycling is printed in the
debug trace file, something with

 setdebug trace=1 level=100 tags=volume,sql dir

It should give give you the different traces and SQL commands that
are used to list volumes and jobs and prune them. You might look them
and check why the records are not properly sent back. (Recycle=No,
VolumeRetention=0, incorrect Pool, incorrect status, etc...)

Then it depends on your different settings, for example, I have seen
that you are using a Volume Retention = 0, that means the recycling
algorithm is disabled for your volume, it might explain why you cannot
achieve what you want. In recent Bacula versions, the pruning
algorithm has bee reviewed to not prune jobs that are necessary to
restore to the last restore point. So, you might need to run a Full
or a Differential backup to get rid of a chain of Incremental jobs
for example. If you don't want to use that feature, the Volume Retention
is the last variable that is checked for a volume, set it to 2 hours,
and after 2 hours, a Full/Used volume in a Pool A should be recycled
when a new job in Pool A requires a volume.


Hope it helps!

Best Regards,
Eric


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Low performance with file daemon version 11.0.5

[Eric Bollengier via Bacula-users]

Hello Marcio,

On 12/6/21 19:24, Márcio (Departamento de Informática - PMI) wrote:

Hello everyone

Investigating a little more about what might be happening, I compared the 
records (from the Bacula catalog in the database) of a file that was backed up 
by 9.6.7 and 11.0.5, without having changed during these two jobs .
I noticed that the "lstat" field of the "filename" table is calculated 
differently between the two versions, although the file hashes, stored in the 
"md5" field are the same, see:


  jobid | pathid |  filename |   lstat | md5
---++++- 

  14469 |  83108 | BPAGAR.DBF | A BAQCz IH/ B A A A Iu A A BOk0Kn xxyqA 
BQdcaU A A M g | TYUkCmxYjmRvmCoTaOBDO+CRJx8
  14749 |  83108 | BPAGAR.DBF | A A IH/ B A A A Iu A A BOk0Kn xxyqA xxyqA A A M 
g  | TYUkCmxYjmRvmCoTaOBDO+CRJx8


Now, why is this field calculated differently?


I'm not sure that part of the code changed a lot on Linux, however on Windows it 
has been updated to use the snapshot to get file attributes and handle some 
specific Windows files and corner cases. I don't know if your filedaemon is a 
linux or a windows one.


The .bvfs_decode_lstat bconsole function can be used to decode this field, and
we can see in your example a lot of "funny" values

*.bvfs_decode_lstat lstat="A BAQCz IH/ B A A A Iu A A BOk0Kn xxyqA BQdcaU A 
A M g"

st_nlink=1
st_mode=33279
perm=-rwxrwxrwx
st_uid=0
st_gid=0
st_size=558
st_blocks=0
st_ino=281474976776371
st_ctime=1349895828
st_mtime=835136128
st_atime=1318273703
st_dev=0
LinkFI=0

*.bvfs_decode_lstat lstat="A A IH/ B A A A Iu A A BOk0Kn xxyqA xxyqA A A M g"
st_nlink=1
st_mode=33279
perm=-rwxrwxrwx
st_uid=0
st_gid=0
st_size=558
st_blocks=0
st_ino=0
st_ctime=835136128
st_mtime=835136128
st_atime=1318273703
st_dev=0
LinkFI=0


One time the ino value is 0, and other time it's probably -1, the mtime does not 
correspond to the ctime. You can get these attributes with the shell command 
stat and compare with what Bacula has computed.


Hope it helps!

Best Regards,
Eric


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Bacula Client Behind NAT

[Eric Bollengier via Bacula-users]

Hello Josh,

On 12/2/21 18:12, Josh Fisher wrote:

3) In bacula-dir.conf on client-XXX I've configured the option:
Allow FD Connections = yes
Should I include "FD Storage Address = mydomain.com"  to backup when the
employee is remote?


If the Address directive specified in the Storage resource of the Director 
configuration file can be resolved by your clients, it's ok. If the address is 
different or cannot be resolved, you can use the FD Storage Address directive, 
but when the clients are in the local network, it will probably not work.



Why not? As long as the storage daemon's public IP is reachable from the local 
LAN, it shouldn't make a difference where the client is.


Yes of course, you are right. The DNS/hosts trick is pretty nice when the 
Storage Daemon has multiple ip addresses in different VLAN, all systems are

referring to it with a single name "bacula-sd", and the name resolution is
pointing to the local address of the SD.

Best Regards,
Eric


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Bacula Client Behind NAT

[Eric Bollengier via Bacula-users]

Hello Wanderlei,

On 12/2/21 15:56, Wanderlei Huttel wrote:

I'm trying to configure the new feature in in Bacula, but manual is not
clear about it.
https://www.bacula.org/11.0.x-manuals/en/main/New_Features_in_11_0_0.html#SECTION00230
In the company have some employees that sometimes are working at home with
their laptops and the most of time are working internal

So, I've thought include "Client Behind Nat" to backup their laptops when
they are remote

1) I've create 2 rules in Firewall to forward ports 9101 and 9103 from FW
Server to Bacula Server (The connection it looks OK)

2) I've configured the laptop client (bacula-fd.conf)
Director {
   Name = bacula-dir
   Password = "mypassword"
   Address = mydomain.com
   Connect To Director = yes
}

3) In bacula-dir.conf on client-XXX I've configured the option:
Allow FD Connections = yes
Should I include "FD Storage Address = mydomain.com"  to backup when the
employee is remote?


If the Address directive specified in the Storage resource of the Director 
configuration file can be resolved by your clients, it's ok. If the address is 
different or cannot be resolved, you can use the FD Storage Address directive, 
but when the clients are in the local network, it will probably not work.



4) If I want to modify the ports from client behind NAT connect, how to do?
Is possible?


Yes, of course, the DirPort of the Director resource in the FileDaemon 
configuration file should be used.



5) This Kind of configuration will work when the employee is in the local
network or in remote network?


I have never tried and I'm not sure it will work out of the box. The code
around connect_to_filedaemon() might have to be adapted a bit (try the direct
connection after the unsuccessful try with the local cache).

The best would probably to play with the DNS records, internally, you resolve 
the local director, from outside, you resolve with the outside address of the 
director.


Hope it helps!

Best Regards,
Eric


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Restoring from a copy job

[Eric Bollengier via Bacula-users]

Hello,

On 11/30/21 22:31, Phil Stracchino wrote:

On 11/30/21 14:54, Josip Deanovic wrote:

On Tuesday 2021-11-30 12:07:37 Phil Stracchino wrote:


The question then ceases to be "I have twenty possible volumes from
which your restore could be performed, which five of the twenty volumes
do you want to use?", and instead becomes, "I have four possible SOURCES
to perform this restore from, please pick *one restore source*."


The restore command of the bconsole tool already has the "pool" command
line argument which could be used for volume selection.

In my case with Bacula 9.6.7 it didn't work with copy jobs. It would be
nice to make it work with newer Bacula versions (e.g. 11.x).

Eric mentioned that MediaType might potentially be used in the selection
algorithm. I am not sure if this is necessary if we get a working "pool="
argument.



Indeed, and Pool is probably a better discriminator in this case than 
MediaType.  In my case, the two relevant pools for Full backups are Full-Disk 
and Full-Archive, and both are Media Type = File.  In any random hypothetical 
environment with copy jobs, I would expect it to be far more likely that Copy 
jobs will be in a different Pool than that they will have a different media type.


I don't know, personally, I'm using different pools to have different retention,
so, we have a simple case where all jobs are in one pool (from Full to the last 
Incr), but it's a corner case as well.


We can add a pool= or a mediatype= kind of keyword in the restore command line,
however, it's far from being very friendly as what we can find in Baculum for 
example. I will think about it and your ideas are welcome.


Thanks,
Best Regards,
Eric



___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Restoring from a copy job

[Eric Bollengier via Bacula-users]

Hello,

On 11/30/21 04:52, Bill Arlofski via Bacula-users wrote:



So far, so good... BUT it gets better because Bacula notices that I have copies 
of these five jobs! Excellent!

So it prints:

These JobIds have copies as follows:
++---+---+---+
| jobid  | job   | copyjobid | mediatype |
++---+---+---+
| 43,803 | Speedy.2021-11-29_03.15.00_39 |43,813 | Synology-File |
| 43,777 | Speedy.2021-11-28_03.15.00_39 |43,788 | Synology-File |
| 43,751 | Speedy.2021-11-27_03.15.00_39 |43,762 | Synology-File |
| 43,725 | Speedy.2021-11-26_03.15.00_39 |43,736 | Synology-File |
| 43,699 | Speedy.2021-11-25_03.15.00_08 |43,710 | Synology-File |
++---+---+---+

But then this is where the breakdown is...

Bacula ignores those five copy jobids, and reports that it is building the 
restore tree from the original backups jobids:

You have selected the following JobIds: 43699,43725,43751,43777,43803

Building directory tree for JobId(s) 43699,43725,43751,43777,43803 ...  
+
554,180 files inserted into the tree.


So, I think I need to report this. (or amend the Mantis if one exists :)



The command prints the alternative to the different jobs, I don't think it can 
choose for you, here in this example, we have 2^5 different possibilities to 
restore the files, I'm not sure Bacula can guess automatically which one do

you want in the mix.

The basic idea is that the original job is usually stored on fast and available 
disks, the copy is more likely stored on tape or cloud kind of slow access device.


When the original job is purged (usually you have a smaller retention), then the
copy job is "promoted", and the next restore command will select it 
automatically.

Note, that it's also possible to have multiple copies of each job, on different 
kind of devices, and some jobs involved may not have copies. Now, if we can 
determine a selection algorithm (via MediaType?), we can probably implement it.


Bconsole is not the best tool for advanced selection screens, however Baculum 
GUI has an excellent supports the copy job selection and can also display the 
different versions of a file, and let you restore the one you want for example.


Best Regards,
Eric


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Connect to Director Schedule Not Working

[Eric Bollengier via Bacula-users]

Hello Richard,

On 11/25/21 14:31, Richard Laysell wrote:

Hello,

I am using the Connect To Director feature to backup a system behind a
NAT.  This system has only intermittent connectivity to the backup
server so I am using a schedule to connect only at certain times.  The
backups are working fine but the connection schedule does not seem to
be working.


It is quite interesting, I would suggest to enable the debug on your FD,
it should log when we start to connect and when we stop.

The "-d0,schedule -T" option can be used when you start the FD, or you can
do a setdebug level=0 trace=1 client=xxx (but of course, it may not be 
connected).

For the command line version, you can start the daemon manually, or modify the 
service file for example to add the options.


Hope it helps!

Best Regards,
Eric


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Packet size too big (NOT a version mismatch)

[Eric Bollengier via Bacula-users]

Hello,

On 11/15/21 21:46, David Brodbeck wrote:

To do that I'd have to upgrade the director and the storage first, right?
(Director can't be an earlier version than the FD, and the SD must have the
same version as the director.)


In general yes, the code is designed to support Old FDs but can have problems
with newer FDs. In your case it may work.

At least, you can try a status client to see if the problem is solved and
if you can run a backup & a restore.

Best Regards,
Eric


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Packet size too big (NOT a version mismatch)

[Eric Bollengier via Bacula-users]

Hello David,

On 11/12/21 23:14, David Brodbeck wrote:

I'm getting this error trying to back up a macOS client. I recently
re-installed bacula from macports on this client, after an upgrade to macOS
Big Sur.

| russell.math.ucsb.edu-sd JobId 80985: Fatal error: bsock.c:520 Packet
size=1387166 too big from "client:128.111.88.29:62571". Maximum permitted
100. Terminating connection. |

Normally when I've seen this it's because of a version mismatch between the
client and the director or storage daemon, but that's not the case here;
the director, sd, and fd are all running the same version:

1000 OK: 103 self-help.math.ucsb.edu-dir Version: 9.4.4 (28 May 2019)
russell.math.ucsb.edu-sd Version: 9.4.4 (28 May 2019) x86_64-pc-linux-gnu
redhat (Core)
noether.math.ucsb.edu-fd Version: 9.4.4 (28 May 2019)
  x86_64-apple-darwin20.6.0 osx 20.6.0


I would recommend to retry with a more recent version of the FD, I remember
to have seen something similar to that in the past.

Best Regards,
Eric


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] bsnapshot tool, API docs

[Eric Bollengier via Bacula-users]

Hello Mark,

On 08.11.21 19:28, mark.berg...@pennmedicine.upenn.edu wrote:

In explaining the "bsnapshot" tool, the Bacula manual states:
The bsnapshot tool should be installed on the Client

What's the download location for that tool?

The tool is inside the Bacula source tree, under src/tools

I'm interested in doing backups of a GPFS filesystem, and using GPFS snapshots. The Linux 
"snapshot" feature in Bacula doesn't list GPFS as a supported OS, but I'd be 
willing
to try writing a compatible utility, to release to the community, so that 
Bacula could create/list/remove GPFS snapshots.

Is there documentation on the bsnapshot API?


The interesting parts are documented inside the bsnapshot.c and the 
src/filed/fd_snapshot.c/h files.


You should find an implementation for ZFS, BRTFS and LVM (quite complicated)

You can ask questions to the dev list if you need help.

Best Regards,

Eric



___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Catalog backup failed

[Eric Bollengier via Bacula-users]

Hello Robert,

On 9/11/21 01:31, Robert Earl wrote:
> Why is bacula-fd looking for the SQL database on the client? There is no
> database running there, only the fd. The database is on the director
> machine.

Very likely you have started the BackupCatalog job on a client "matthew-fd"
instead of the client "aten-fd". Look the configuration of the Job (around
the Client directive, or on the JobDefs Client directive if you have one),
or it might also be what you did to run the job (client=matthew-fd on the
command line, or in the Backup menu).

Hope it helps!

Best Regards,
Eric


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Overlapping scheduled jobs

[Eric Bollengier via Bacula-users]

Hello Marcio,

On 8/23/21 21:22, Márcio (Departamento de Informática - PMI) wrote:
> Hi Heitor, thanks for helping
> 
> I saw the link you mentioned, but I haven't found something that helps me.

The exact link is more
https://www.bacula.org/11.0.x-manuals/en/main/Configuring_Director.html#Director:Job:AllowDuplicateJobs

You will see a diagram on how to configure the Allow Duplicate Jobs that Heitor
has mentioned. It will basically cancel the Differential Job at the end.

The other tricks based on MaximumConcurrentJobs (in your Job resource), or on 
the
Priority (in your Schedule run line) can also do the work to prevent the two 
jobs
to run concurrently.

Hope it helps!

Best Regards,
Eric
 
> Márcio
> 
> Em 23/08/2021 15:28, Heitor Faria escreveu:
>>> Hi, greetings everyone.
>> Hello Marcos,
>>  
>>> I searched for this subject in other posts in this list, but I didn't
>>> find something that was similar, so I decided to post my question.
>>> Is there any way to prevent jobs scheduled on a certain day from
>>> overlapping jobs that were previously scheduled and are still in the
>>> execution queue, even if the priority number of new jobs is lower?
>>> On Friday the FULL backups are started, and often the differential
>>> backup that starts on Saturday is merged with the one on Friday.
>>> Grateful for any help.
>> Please refer to Allow Duplicate Jobs =  and next directives: 
>> https://www.bacula.org/11.0.x-manuals/en/main/Configuring_Director.html#SECTION002120
>> Our company provides Bacula Community training, deployment and support, 
>> specially for the government and under the elicitation dismissal price, if 
>> you need a more professional support to your environment. 
>>
>>> Márcio
>>> Prefeitura Municipal de Indaiatuba
>>> Telefone: (19) 3834-9000
>>> Site: http://www.indaiatuba.sp.gov.br/
>> Atte.
> 



___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Prolems with Bacula 11..05 encryption

[Eric Bollengier via Bacula-users]

Hello Kelly,

On 04.08.21 21:14, Kelly Price wrote:

Hello
    I am having a problem getting encryption working in Bacula 11.0.5. I have 
looked at the problem until I am almost blind, but I don’t see a configuration 
error. Could someone take a look and see if it is something obvious I am 
missing? I apologize for the length of this post; hopefully I’ve included all 
the required information.


If I'm not mistaken, to use TLS, you don't have any directive to configure in 
11.0.5, it is turned automatically and the password is used as the shared secret 
key. This is far less complex to setup. A "status dir" should display somewhere 
that you are connected with TLS. (same for status dir and status client).


The message written in your log seems to indicate that the DIR requires TLS and 
the SD doesn't have it. It is sometime a bit tricky to setup the TLS with 
certificates specially with hostname, the certificate might use a name, and an 
other name is used in the connection.


Fatal error: Authorization problem: SD "Storage daemon:storage.xxx.yyy" did not 
advertise required TLS support.


Maybe the compilation of the SD is incorrect (lack of support of TLS), or the 
configuration is not done, or you need to restart it in some way to apply your 
changes.


Hope it helps!

Best Regards,

Eric



___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Log table so big

[Eric Bollengier via Bacula-users]

Hello Guilherme,

On 8/4/21 20:06, Guilherme Santos wrote:
> Hey Eric, thanks to reply. Sorry, I said that the table has a about a
> million lines... but it has more then 156 million lines.

So, we are more around 7.8 million jobs in your catalog if you have
only standard Bacula log lines, congratulation! :-)

> So, I did a query at table Log and it has information about the first
> log (LogId = 1, JobId = 1). It indicates that no maintenance was done
> yet. What do you suggest?
> 
> The Bacula is configured do a prune at expired volumes everyday after
> complete all backups.

You can run a couple of queries to determine where the problem is, for
example, list the number of lines per job

SELECT JobId, count(1) Nb FROM Log GROUP BY JobId ORDER BY Nb DESC LIMIT 100;

The second step would be to read the logs for these jobs and identify
the pollution source.

list joblog jobid=x

or still via SQL

SELECT LogText from Log WHERE JobId=x;

Once you know the kind of line, you can reduce the verbosity of your
procedures or correct the configuration.

Hope it helps!

Best Regards,
Eric

> Thanks!
> 
> ____________ De: Eric Bollengier via Bacula-users
>  Enviado: quarta-feira, 4 de
> agosto de 2021 11:56 Para: bacula-users@lists.sourceforge.net
>  Assunto: Re: [Bacula-users] Log
> table so big
> 
> Hello,
> 
> On 8/4/21 15:37, Guilherme Santos wrote:
>> Hello! First, thanks to suport.
>> 
>> I'm using Bacula for a consider time and my Log table is about
>> 19GB. What's the best solution to "solve" this? This table has more
>> than a million lines. I'm using Bacula 9.4.4.
>> 
> 
> 19GB for 1,000,000 records is a lot, you might double check if you
> run the database maintenance tools properly.
> 
> Then, I would suggest to have a look to the table content, the last
> time I saw this problem, a couple of runscripts were generating 95%
> of the content of the table.
> 
> If you list the files you backup or something like that in the
> Messages resource, it can be also very verbose, but you can configure
> what you want to see or not.
> 
> A regular job is probably around 20 lines, if you have more than
> 50,000 jobs in your Job table, it might be normal as well. You can
> prune your Jobs or also not use the catalog as a Messages
> destination.
> 
> Hope it helps!
> 
> Best Regards, Eric
> 
> 


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Log table so big

[Eric Bollengier via Bacula-users]

Hello,

On 8/4/21 15:37, Guilherme Santos wrote:
> Hello!
> First, thanks to suport.
> 
> I'm using Bacula for a consider time and my Log table is about 19GB.
> What's the best solution to "solve" this? This table has more than a million 
> lines. I'm using Bacula 9.4.4.
> 

19GB for 1,000,000 records is a lot, you might double check if you run the
database maintenance tools properly.

Then, I would suggest to have a look to the table content, the last time I saw
this problem, a couple of runscripts were generating 95% of the content of the 
table.

If you list the files you backup or something like that in the Messages 
resource,
it can be also very verbose, but you can configure what you want to see or not.

A regular job is probably around 20 lines, if you have more than 50,000 jobs in 
your
Job table, it might be normal as well. You can prune your Jobs or also not use 
the
catalog as a Messages destination.

Hope it helps!

Best Regards,
Eric


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] LTO backup not run smooth

[Eric Bollengier via Bacula-users]

Hello,

On 7/4/21 13:31, War Nings wrote:
> Hello,
> 
> I'm new to LTO backup and Bacula usage so may be not enough knowledge.
> 
> My LTO7 or even LTO3 media not run smooth during backup. Not know if
> it's shoe shining effect but seem something like that.
> You can hear it media stop and restart each some seconds or view on
> file/network monitoring than bandwidth stop and restart some seconds
> later.
> I try to remove MD5 checksum but seem change nothing always the same
> issue with signature None or MD5. Spool parameter seem to change
> nothing too with 50go or 900go spool size is the same issue.
> 
> I try directly from a network share with enough bandwidth after I try
> to use a SSD spool 1tb with ~400mo/sec read capabilities when I copy
> file to the memory or on /dev/null so can sustain without issue a LTO7
> drive. The bandwidth speed reach something like ~200mo/sec drop and
> return to ~200mo/sec.
> 
> If I use tar cvf command to copy the same folder directly to lto drive
> seem run smooth without any interrupt. Bandwidth is stable at
> ~118mo/sec seem low for a LTO7 media but not have any stop and
> restart.  It's the same with LTO3 media with less bandwidth usage.
> 
> What can be the issue if it's not normal with Bacula ?
> Database too slow to write entries but stored on a old SSD so not a
> lot of bandwidth but 50mo/sec without issue for record md5 checksum
> should be enough.
> CPU who calculate checksum files too slow Bacula wait on CPU and
> restart with next file ?
> One missed parameter for keep some gb in a memory buffer ?
> I check PCIe bandwidth with 5Gb/s at 8x.
> 
> 
> I not want to destroy my LTO drive or media due to all of these stops
> each some seconds.
> 

I would recommend to run the btape utility to find the best parameters
for your drive.

In addition, make sure that:
 - you use a recent version of Bacula
 - the Batch Mode is enabled (by default)
 - Spooling of the attributes is enabled (by default)
 - the Storage/Device/Maximum File Size parameter is set to 5-15G (default to 
1G)

Each time the Maximum File Size parameter is reached, Bacula will put a mark
on the tape and produces a JobMedia that may need to be inserted in the catalog
before to continue the backup (it depends on the version you use).

Hope it helps!

Best Regards,
Eric


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] bacula backup 11.0.2 - Problem save

[Eric Bollengier via Bacula-users]

Hello Eric,

On 23.06.21 16:23, JANOWSKI ERIC via Bacula-users wrote:

23-Jun 14:18 bacula-dir JobId 47: Error: Could not open WriteBootstrap file:
/var/lib/bacula/SRV-MASTER-fd.bsr: ERR=No such file or directory


I believe that this directive can cause you a problem, check that the directory 
exists and can be used by your Director unix user.


Hope it helps!

Best Regards,

Eric



___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] How to configure Bacula with S3

[Eric Bollengier via Bacula-users]

Hello,

I would suggest to play with ld.so.conf and LD_LIBRARY_PATH, it seems that new 
systems are not very fan of having things in /usr/local.


Best Regards,

Eric

On 16.06.21 14:01, Wanderlei Huttel wrote:

Hello

Finally I'm trying to run Bacula with S3 Cloud (Wasabi), but I'm not getting 
to configure.
In the Whitepaper and Manual is not so clear (would be interesting have more 
information  and examples about it).


What I'm doing wrong?

I followed this bacula video:
https://www.youtube.com/watch?v=WCsgtl--ZHA 



root@debian:/usr/src/libs3-20200523# DESTDIR=/usr/local make clean
build: Cleaning

root@debian:/usr/src/libs3-20200523# DESTDIR=/usr/local make
build/obj/bucket.do: Compiling dynamic object
build/obj/bucket_metadata.do: Compiling dynamic object
build/obj/error_parser.do: Compiling dynamic object
build/obj/general.do: Compiling dynamic object
build/obj/object.do: Compiling dynamic object
build/obj/request.do: Compiling dynamic object
build/obj/request_context.do: Compiling dynamic object
build/obj/response_headers_handler.do: Compiling dynamic object
build/obj/service_access_logging.do: Compiling dynamic object
build/obj/service.do: Compiling dynamic object
build/obj/simplexml.do: Compiling dynamic object
build/obj/util.do: Compiling dynamic object
build/obj/multipart.do: Compiling dynamic object
build/lib/libs3.so.4: Building shared library
build/obj/bucket.o: Compiling object
build/obj/bucket_metadata.o: Compiling object
build/obj/error_parser.o: Compiling object
build/obj/general.o: Compiling object
build/obj/object.o: Compiling object
build/obj/request.o: Compiling object
build/obj/request_context.o: Compiling object
build/obj/response_headers_handler.o: Compiling object
build/obj/service_access_logging.o: Compiling object
build/obj/service.o: Compiling object
build/obj/simplexml.o: Compiling object
build/obj/util.o: Compiling object
build/obj/multipart.o: Compiling object
build/lib/libs3.a: Building static library
build/obj/s3.o: Compiling object
build/bin/s3: Building executable
build/include/libs3.h: Linking header
build/obj/testsimplexml.o: Compiling object
build/bin/testsimplexml: Building executable


root@debian:/usr/src/libs3-20200523# DESTDIR=/usr/local make install
/usr/local/bin/s3: Installing executable
/usr/local/lib/libs3.so.4.1.bac: Installing shared library
/usr/local/lib/libs3.so.4: Linking shared library
/usr/local/lib/libs3.so: Linking shared library
/usr/local/lib/libs3.a: Installing static library
install: AVISO: ignorando a opção --strip-program, pois a opção -s não foi 
especificada

/usr/local/include/libs3.h: Installing header
install: AVISO: ignorando a opção --strip-program, pois a opção -s não foi 
especificada



When I run S3 I've receive this error.
root@debian:/usr/src/libs3-20200523# s3
s3: error while loading shared libraries: libs3.so.4: cannot open shared 
object file: No such file or directory




bacula-sd.conf

Storage{
  Name = bacula-sd
  SDPort = 9103
  WorkingDirectory = "/etc/bacula/working"
  Pid Directory = "/etc/bacula/working"
  Maximum Concurrent Jobs = 50
  Heartbeat Interval = 300 seconds
  PluginDirectory = "/etc/bacula/plugins"
}

Cloud {
  Name = "Wasabi"
  Driver = "S3"
  HostName = "s3.wasabisys.com "
  Region = "us-east-1"
  BucketName = "my-bucket-name"
  AccessKey = "MY_KEY"
  SecretKey = "MY_SECRET_KEY"
  Protocol = HTTPS
  UriStyle = path
  Truncate Cache = No #AfterUpload
  Upload = EachPart
  # MaximumUploadBandwidth = 5MB/s # Optional
}

Device {
  Name = "RemoteBucket"
  Device Type = Cloud
  Cloud = "Wasabi"
  Archive Device = "/backup/wasabi" # local volume cache
  Maximum Part Size = 500 MB # important: it is the object upload granularity
  Media Type = Cloud
  LabelMedia = yes
  Random Access = yes
  AutomaticMount = yes
  RemovableMedia = no
  AlwaysOpen = no
}



bacula-dir.conf

Storage {
  Name = "Wasabi"
  Address = 192.168.1.87
  SDPort = 9103
  Password = "XXX"
  Device = "RemoteBucket"
  Media Type = Cloud
  Maximum Concurrent Jobs = 1
  Heartbeat Interval = 300 seconds
#  Autochanger = "Wasabi"
}


Best regards

*Wanderlei Hüttel*



___
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 11 - where's my Filename table? :-)

[Eric Bollengier via Bacula-users]

Thanks Wanderlei, I have applied your patch to the current 11.0

Best Regards,

Eric

On 15.06.21 13:05, Wanderlei Huttel wrote:

Hello Uwe

I've made a patch to fix queries in "bacula/examples/sample-query.sql"
Basically is necessary to remove the table Filename and replace 
"Filename.Name" by "File.FileName"


Best regards

*Wanderlei Hüttel*



Em ter., 15 de jun. de 2021 às 04:54, Uwe Schuerkamp 
mailto:uwe.schuerk...@nionex.net>> escreveu:


Hi folks,

I just started upgrading a few instances from 9.6.x to 11.0.5 compiled
from source. Following the db upgrade and trying out a "list files for
a selected jobid" query, I noted an error about the query referencing
the no-longer-existing table "Filename". I'm pretty sure that's noted
in the release notes somewhere, but I didn't see any messages here so
I thought I'd better make sure that the upgrade process went smoothly.

The backups & restores are running fine on the version, it's just that
both bweb / bacula web and my old query.sql files are borked (I
usually copy over the query.sql file from my previous version).

Thanks in advance & all the best,

Uwe

-- Uwe Schürkamp | email: mailto:uwe.schuerk...@nionex.net>>



___
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



___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] [Bacula-devel] Release 11.0.5

[Eric Bollengier via Bacula-users]

Hello,

The release process takes a couple of hours to process, in my current procedure, 
I'm pushing the tags at the end when emails are sent and everything is tested 
and uploaded.


This is not the best practice, so, I will push the tags sooner in the process.

Best Regards,

Eric

On 04.06.21 18:50, Sven Hartge wrote:

On 04.06.21 17:18, Dan Langille wrote:

On Fri, Jun 4, 2021, at 8:19 AM, Sven Hartge wrote:

On 04.06.21 08:46, Eric Bollengier via Bacula-users wrote:



If something is wrong, a new release is made and tagged as well.



Same goes for the provided archives. Please don't remove existing ones
and replace them with other archives with the same version.



A project should never do this.

As a packager, you have now made my job much bigger than it needs to be.
This is a non-trivial situation. If there is a problem with the release,
create another release. Your downstream will have much more respect for you
than if you do otherwise.

Please, never do this.


You *can* remove releases, if there are broken or dangerous, I have no 
problems with that.


But please, please, please, do not reuse the version when you create the next 
unbroken release.


Also please tag the exact point that the released archives where made in GIT 
immediately. There may be a time where we need to examine the contents of the 
archives and compare them to the code in GIT.


Grüße,
Sven.



___
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] Fatal error: MD5 digest not same FileIndex

[Eric Bollengier via Bacula-users]

Hello Elias,

On 04.06.21 00:39, Elias Pereira wrote:

Hello,

I am having this error Fatalerror: MD5 digest not same FileIndexin a backup to 
aws S3. This backup is of files from a fileserver.

Is there any way to disable this check or something like that?


Your issue is not very precise, but I have seen this problem with 
Copy/Migration jobs trying to work with jobs that have a cycle in their volume 
list (not a very common situation, and rather easy to avoid). Maybe you can 
give us some more details.

Best Regards,

Eric



___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] [Bacula-devel] Release 11.0.5

[Eric Bollengier via Bacula-users]

Hello Wanderlei,

On 6/3/21 23:06, Wanderlei Huttel wrote:
> Hello Eric
> 
> Is the code updated in the bacula git? There's no tag 11.0.5.

It seems that the release process is very attractive these days,
the tags are usually pushed at the end of the procedure (after
few days or when preparing the next release. It's better to
be sure that everything is ok because we cannot overwrite tags
once they are cloned on other git repositories.

Of course, I can push them now, it seems that the release
is correct this time.

Best Regards,
Eric
 
> Best regards
> 
> *Wanderlei Hüttel*
> 
> 
> 
> Em qui., 3 de jun. de 2021 às 15:05, Eric Bollengier via Bacula-devel <
> bacula-de...@lists.sourceforge.net> escreveu:
> 
>> Hello,
>>
>> We are pleased to announce the release of Bacula version 11.0.5. This is
>> a minor release of the new stable version.
>>
>> The new release 11.0 has 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.
>>
>> This release of Bacula uses a new catalog format.  We provide a set of
>> scripts that permit to convert a 9.x and earlier versions to the new
>> 11.0 format (1023).  Normally, it is automatic, though this is a big
>> change that takes longer than usual. The upgrade process will require
>> more or less twice the size of the actual database on disk.
>>
>> Please see the ReleaseNotes for how to build Bacula 11.0.5 with the
>> correct libs3 for use with the Amazon Cloud.
>>
>> The binaries (rpm, deb) should be ready in a week or two.
>>
>> Thank you for using Bacula,
>> Eric
>>
>> 
>> Release 11.0.5 03 June 2021
>>
>> 11.0.5 is a minor bug fix release.
>>
>>  - Fix compilation
>>  - Fix org#2427 About incorrect handling of empty files with Accurate=yes
>> on Windows
>>  - Update MySQL update procedure for 5.6
>>
>> Bugs fixed/closed since last release:
>> 2427
>>
>>
>> ___
>> Bacula-devel mailing list
>> bacula-de...@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bacula-devel
>>
> 



___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

[Bacula-users] Release 11.0.5

[Eric Bollengier via Bacula-users]

Hello,

We are pleased to announce the release of Bacula version 11.0.5. This is
a minor release of the new stable version.

The new release 11.0 has 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.

This release of Bacula uses a new catalog format.  We provide a set of
scripts that permit to convert a 9.x and earlier versions to the new
11.0 format (1023).  Normally, it is automatic, though this is a big
change that takes longer than usual. The upgrade process will require
more or less twice the size of the actual database on disk.

Please see the ReleaseNotes for how to build Bacula 11.0.5 with the
correct libs3 for use with the Amazon Cloud.

The binaries (rpm, deb) should be ready in a week or two.

Thank you for using Bacula,
Eric


Release 11.0.5 03 June 2021

11.0.5 is a minor bug fix release.

 - Fix compilation
 - Fix org#2427 About incorrect handling of empty files with Accurate=yes on 
Windows
 - Update MySQL update procedure for 5.6

Bugs fixed/closed since last release:
2427


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Update of Bacula MySQL tables from 16 to 1017 failed. [Help!]

[Eric Bollengier via Bacula-users]

Hello,

On 6/1/21 05:50, Phil Stracchino wrote:
> Actually, there is no point to that DROP INDEX operation, because the
> entire table is going to be dropped after its replacement is rebuilt anyway.
> 
> What you can (and probably should) do is find the following two lines:
> 
> DROP INDEX IF EXISTS JobId on File;
> DROP INDEX IF EXISTS JobId_2 on File;
> 
> And, frankly, just delete them.  They serve no purpose.

As I wrote previously, this major catalog update will consume a very
large amount of disk space, and these commands are here to drop the
biggest indexes of the database. This is useful for most users.
 
> If you prefer to have those indexes dropped anyway in the script, then
> just delete the words 'IF EXISTS' from these two lines ONLY.  The reason
> they are there is probably a copy-paste error on my part.
> 

So, what is the correct syntax? Or maybe it is not available on all recent
MySQL & co distribution?

I'm almost ready to release 11.0.5, and such kind of fixes would be helpful.

I can drop the IF EXISTS and add a comment for users that want to run the
procedure multiple times.

Best Regards,
Eric




___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

[Bacula-users] Release 11.0.4

[Eric Bollengier via Bacula-users]

Hello,

We are pleased to announce the release of Bacula version 11.0.4. This is
a minor release of the new stable version.

The new release 11.0 has 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.

This release of Bacula uses a new catalog format.  We provide a set of
scripts that permit to convert a 9.x and earlier versions to the new
11.0 format (1023).  Normally, it is automatic, though this is a big
change that takes longer than usual. The upgrade process will require
more or less twice the size of the actual database on disk.

Please see the ReleaseNotes for how to build Bacula 11.0.4 with the
correct libs3 for use with the Amazon Cloud.

The binaries (rpm, deb) should be ready in a week or two.

Thank you for using Bacula,
Eric



Release 11.0.4 28 May 2021

11.0.4 is a minor bug fix release.

 - baculum: Update script version
 - Fix org#2618 Disable fix on bvfs_get_jobids() temporarily
 - Improve MySQL upgrade procedure

Bugs fixed/closed since last release:
2618



___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

[Bacula-users] Release 11.0.3

[Eric Bollengier via Bacula-users]

Hello,

We are pleased to announce the release of Bacula version 11.0.3. This is
a minor release of the new stable version.

The new release 11.0 has 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.

This release of Bacula uses a new catalog format.  We provide a set of
scripts that permit to convert a 9.x and earlier versions to the new
11.0 format (1023).  Normally, it is automatic, though this is a big
change that takes longer than usual. The upgrade process will require
more or less twice the size of the actual database on disk.

Please see the ReleaseNotes for how to build Bacula 11.0.3 with the
correct libs3 for use with the Amazon Cloud.

The binaries (rpm, deb) should be ready in a week or two.

Thank you for using Bacula,
Eric



Release 11.0.3 21 May 2021

11.0.3 is a minor bug fix release.

 - Check if char **jobid parameter is NULL before modifying it in 
bvfs_parse_arg_version()
 - Enhance the update_mysql_tables script
 - Fix compilation of check_bacula.c reported by Dan
 - Fix org#2442 About the check of the Control Device during startup
 - Fix org#2500 .bvfs_get_jobids jobid=X must return X in the list
 - Fix org#2604 About column alignment of 'Terminated Jobs' section
 - Fix org#2605 About incorrect messages in restore command
 - Fix stored/Makefile.in to install cloud driver object with cloud targets
 - Fix various default permissions

 - baculum: Add autochanger management section and improve few other texts
 - baculum: Add component action (start/stop/restart) buttons to client and 
  storage pages
 - baculum: Add example working directory path in API install wizard
 - baculum: Add new device interface definition to Baculum OpenAPI documentation
 - baculum: Fix #2592 logout button on Safari web browser
 - baculum: Fix double device error code number
 - baculum: Fix opening update slots window reported by Hector Barrera
 - baculum: Fix sub-tabs on client and on storage pages
 - baculum: Implement autochanger management
 - baculum: Implement support for assigning multiple API hosts to one user
 - baculum: Restore wizard improvements
 - baculum: Update Portuguese translations
 - baculum: Update Russian translations
 - baculum: Update documentation chapter and screenshots
 - baculum: Use catalog access in changer listall endpoint only if it is 
configured on API host

 - docs: Add information about the git branch used with Bacula
 - docs: Fix #7657 Enhance the FSType description
 - docs: Fix #7659 About EnhancedWild fileset directive documentation
 - docs: Fix org#2578 About missing "restore directory=xxx" keyword 
documentation

Bugs fixed/closed since last release:
2442 2500 2578 2592 2604 2605 7657 7659


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Race condition creating volumes on two different NASes

[Eric Bollengier via Bacula-users]

Hello Andrea,

I would recommend to use the latest git version of Branch-9.6 or to switch
to 11.0 where the SQL issue has been fixed. (The PostgreSQL backend doesn't
report such error as well).

Best Regards,
Eric



___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] S3 "Driver" Doesn't Work 11.0.2

[Eric Bollengier via Bacula-users]

Hello,

I found out that the cloud driver library is not installed properly 
with "make install", it is needed to do "make -C src/stored install-cloud"
to get the object correctly installed. Only the cloud S3 driver was
installed automatically. (the cloud library is loading the cloud S3
library).

By default, some permissions are also a bit too strict when we use
a non-root user (and we use the root account to build and install
the files).

These items are now fixed in the current git repository, and it will
be available in the next release.

On Ubuntu Focal, one catalog library needed to start the Director
cannot be loaded properly by default, with a LD_LIBRARY_PATH, it
works... I think it's due to a recent change to the linking system.
I don't know how yet to fix that.

I have published a small video that shows how to setup a Ubuntu focal
system with 11.0.2 and the Cloud S3 driver.

https://youtu.be/WCsgtl--ZHA

Best Regards,
Eric

On 5/7/21 13:15, Martin Simmons wrote:
> OK, so either there is an additional S3-specific package that you need to
> install or bacula.org needs to fix their build.
> 
> __Martin
> 
> 


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

[Bacula-users] Release 11.0.2

[Eric Bollengier via Bacula-users]

Hello,

We are pleased to announce the release of Bacula version 11.0.2. This is
a minor release of the new stable version.

The new release 11.0 has 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.

This release of Bacula uses a new catalog format.  We provide a set of
scripts that permit to convert a 9.x and earlier versions to the new
11.0 format (1023).  Normally, it is automatic, though this is a big
change that takes longer than usual. The upgrade process will require
more or less twice the size of the actual database on disk.

Please see the ReleaseNotes for how to build Bacula 11.0.2 with the
correct libs3 for use with the Amazon Cloud.

The binaries (rpm, deb) should be ready in a week or two.

Thank you for using Bacula,
Eric


Release 11.0.2 26 March 2021

11.0.2 is a minor bug fix release.

 - Add functions to unittests library
 - Add support for store_alist_str() in plugin configuration items
 - Enhance bdelete_and_free() macro
 - Update baculabackupreport script

 - Fix #7286 DIR segfault when doing a "dir" command in a restore
 - Fix #7321 About issue when stopping jobs waiting for resources
 - Fix #7396 GRANT command error in granting privileges script for MySQL
 - Fix #7449 About incorrect JSON output with 'TLS Allowed CN' directive
 - Fix #7451 About deleted files incorrectly kept in Virtual Full
 - Fix S3 compilation
 - Fix Verify job issue with offset stream and compressed blocks
 - Fix bug #2498 - Wrong mode for /etc/logrotate.d/bacula
 - Fix check_bacula.c to ignore daemon events
 - Fix possible memory corruption in the label process
 - Fix reload issue when a Job doesn't have a Pool defined
 - Possible fix for SD high memory usage problem
 - Remove suspicious debug line on setdebug()

 - baculum: Add Craig Holyoak to AUTHORS
 - baculum: Fix #2597 LDAP login with LDAPS option
 - baculum: Fix cancel button in new job wizard
 - baculum: Fix displaying warning messages in messages window
 - baculum: Fix undefined property error in run job API endpoint if
level value
   is not provided
 - baculum: Implement API version 2
 - baculum: Improve updating asset files after upgrade
 - baculum: Unify jobs/{jobid}/files endpoint output for detailed and
normal
   modes
 - baculum: Update Polish translations
 - baculum: Update Portuguese translations
 - baculum: Update Russian translations
 - baculum: Use new APIv2 status client request on job history view page

 - rpms: Fix bacula.spec for Fedora 31
 - rpms: Fix bacula.spec for rhel8 / centos 8
 - rpms: Fix missing query.sql
 - rpms: Update bacula.spec for rhel8

 - win32: Fill the version information as CFLAGS
 - win32: Fix #7373 binaries are tagged with correct resource
 - win32: Fix error message when labeling volume on Windows SD
 - win32: Update openssl version to 1.1.1k


Bugs fixed/closed since last release:
2498 2597 7286 7321 7373 7396 7449 7451


Release 11.0.1 04 February 2021

11.0.1 is a minor bug fix release.

 - Add PGSQL detection for macOS and MacPorts.
 - BEE Backport bacula/src/tools/dbcheck.c
 - Fix #7079 About a segfault in a copyjob when the fileset is no longer
defined
 - Fix #7168 About incorrect start time displayed for canceled jobs not yet
  running
 - Fix #7207 About 'dbcheck -n' not working properly
 - Fix #7214 Adapt mtx-changer.conf for GNU cpio mt version
 - Fix #7247 About incorrect variable substitution with the query command
 - Fix MySQL update procedure with incorrect handling of the FileIndex type
 - Fix compilation warnings with Solaris Studio
 - Fix copy/migration job selection
 - Fix org#2579 About incorrect JSON generated from empty Messages resource
 - Fix org#2587 Improve btraceback output
 - Fix org#2588 About incorrect Object/ObjectId type in
update_postgresql_tables
 - Fix update_sqlite3_tables to upgrade from 9.6 to 11.0
 - Initialize StartTime in db_create_job_record()
 - Remove deprecated sbrk in macOS and Windows.
 - Use PKG_PROG_PKG_CONFIG macro to search for pkg-config. It is
cross-compile
  safe.
 - alist: Fix for memory overflow access.

 - baculum: Add capability to create filedaemon console and schedule on new
  resource page
 - baculum: Add console messages log API endpoint
 - baculum: Add console messages log envelope
 - baculum: Add job status weather on job list page
 - baculum: Add new icons for job status weather purpose
 - baculum: Add to Bvfs lsdirs and lsfiles API endpoints pathid parameter
 - baculum: Browser paths in restore browser using pathid
 - baculum: Fix #2560 in restore wizard display names encoded in non-UTF
encoding
 - baculum: Fix finding jobs by filename in restore wizard if filename
contains
  whitespace characters
 - baculum: Fix problem with setting hourly schedule - reported by Elias
Pereira
 - baculum: Remove excanvas.js dependency
 - 

Re: [Bacula-users] Problem with autoloader

[Eric Bollengier via Bacula-users]

Hello William,

On 2/18/21 16:28, William Muriithi wrote:
> Hello
> 
> I have a problem where bacula seem to be rejecting most of my tapes.  I had 
> lapsed using tapes for a couple of months as I was working remote due to 
> covid.   Recently, I re-started my tape backups and struggling as some tapes 
> are working fine, but others are a pain.
> 
> For example, or jobs in the queue need tape 06L6.   I mounted it through 
> bacula, it came online, went into initializing, but bacula unmount it and 
> them mount tape 000118L6.
> 
> 
> That don't work out too and leave bacula in usable state as seen below:
> 
> Device status:
> Autochanger "SuperLoader3" with devices:
>"ULTRIUM-HH7" (/dev/nst0)
> 
> Device Tape is "ULTRIUM-HH7" (/dev/nst0) waiting for:
> Volume:  000118L6
> Pool:eng_father
> Media type:  LTO-6
> Total Bytes Read=64,512 Blocks Read=1 Bytes/block=64,512
> Positioned at File=0 Block=0
>Device is BLOCKED waiting for mount of volume "06L6",
>Pool:eng_father
>Media type:  LTO-6
>Slot 7 is loaded in drive 0.
> 
> What would be the best way to work around this?
> 
> Regards,
> William
> 
> 18-Feb 00:07 bacula-dir JobId 137: Using Device "ULTRIUM-HH7" to write.
> 18-Feb 00:07 eng-backup01-sd JobId 137: Warning: Director wanted Volume 
> "06L6".
> Current Volume "000118L6" not acceptable because:
> 1998 Volume "000118L6" catalog status is Purged, not in Pool.
> 18-Feb 00:07 eng-backup01-sd JobId 137: 3307 Issuing autochanger "unload 
> Volume 06L6, Slot 7, Drive 0" command.
> 18-Feb 00:08 eng-backup01-sd JobId 137: 3304 Issuing autochanger "load Volume 
> 06L6, Slot 7, Drive 0" command.
> 18-Feb 00:09 eng-backup01-sd JobId 137: 3305 Autochanger "load Volume 
> 06L6, Slot 7, Drive 0", status is OK.
> 18-Feb 00:09 eng-backup01-sd JobId 137: Warning: Director wanted Volume 
> "06L6".
> Current Volume "000118L6" not acceptable because:
> 1998 Volume "000118L6" catalog status is Purged, not in Pool.
> 18-Feb 00:09 eng-backup01-sd JobId 137: 3307 Issuing autochanger "unload 
> Volume 06L6, Slot 7, Drive 0" command.
> 

It looks that Bacula has tried to load the slot 7 with the tape
06L6, and he got the tape 000118L6. I would suggest to run the
"update slots" command to make sure that the Slot information is
properly set for each Media.

Hope it helps!



___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Error on despooling attributes in catreq.c: wanted xxx bytes, maximum permitted 10000000 bytes

[Eric Bollengier via Bacula-users]

Hello Uwe,

On 2/15/21 09:56, Uwe Schuerkamp wrote:
> Hi folks,
> 
> during a largish backup job (3,8TB windows fileserver, about 5m files
> & directories) I'm seeing this error when the attributes are being
> despooled once the job completes:
> 
> Fatal error: catreq.c:762 fread attr spool error. Wanted 1969368434
> bytes, maximum permitted 1000 bytes

It seems that an invalid message was found in the spool file, this size
is the expected size of the message, that is rarely more than few
hundred bytes. It can be some error message for example (low disk space?).

You might want to diagnose in the Storage daemon when we write to
thespool file and track when the msglen is > 100 for example. (Display
the packet in the trace file for example.

Hope it helps!

Best Regards,
Eric


> I've searched the mailing list and the documentation for a possible
> variable related to attribute spooling, but I can only find options
> that regulate disk / job spooling.
> 
> I'd be most grateful if someone could direct me to the correct
> configuration parameter.[1]
>
> We're using bacula 9.6.5 compiled from source on CentOS7.
> 
> Thanks in advance & all the best, 
> 
> Uwe
> 
> [1] I'd also have no problem with patching catreq.c and recompiling,
> but hopefully there's a supported way of adjusting this variable.
> 


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Release 11.0.1

[Eric Bollengier via Bacula-users]

Hello Chris,

On 2/9/21 23:52, Chris Wilkinson wrote:
> I’m sorry if this has been answered before but what is the location for the 
> Debian 10 Bacula repository?

In general, you can find packages on
https://www.bacula.org/bacula-binary-package-download/

For Debian 10, we don't have yet this distribution, I think that debian
folks have build procedures that we can use to publish packages on
bacula.org, but it's not available for the moment.

Best Regards,
Eric


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

[Bacula-users] Release 11.0.1

[Eric Bollengier via Bacula-users]

Hello,

We are pleased to announce the release of Bacula version 11.0.1. This is
a minor release of the new stable version.

The new release 11.0 has 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.

This release of Bacula uses a new catalog format.  We provide a set of
scripts that permit to convert a 9.x and earlier versions to the new
11.0 format (1023).  Normally, it is automatic, though this is a big
change that takes longer than usual. The upgrade process will require
more or less twice the size of the actual database on disk.

Please see the ReleaseNotes for how to build Bacula 11.0.1 with the
correct libs3 for use with the Amazon Cloud.

The binaries (rpm, deb) should be ready in a week or two.

Thank you for using Bacula,
Eric



Release 11.0.1 04 February 2021

11.0.1 is a minor bug fix release.

 - Add PGSQL detection for macOS and MacPorts.
 - BEE Backport bacula/src/tools/dbcheck.c
 - Fix #7079 About a segfault in a copyjob when the fileset is no longer
defined
 - Fix #7168 About incorrect start time displayed for canceled jobs not yet
  running
 - Fix #7207 About 'dbcheck -n' not working properly
 - Fix #7214 Adapt mtx-changer.conf for GNU cpio mt version
 - Fix #7247 About incorrect variable substitution with the query command
 - Fix MySQL update procedure with incorrect handling of the FileIndex type
 - Fix compilation warnings with Solaris Studio
 - Fix copy/migration job selection
 - Fix org#2579 About incorrect JSON generated from empty Messages resource
 - Fix org#2587 Improve btraceback output
 - Fix org#2588 About incorrect Object/ObjectId type in
update_postgresql_tables
 - Fix update_sqlite3_tables to upgrade from 9.6 to 11.0
 - Initialize StartTime in db_create_job_record()
 - Remove deprecated sbrk in macOS and Windows.
 - Use PKG_PROG_PKG_CONFIG macro to search for pkg-config. It is
cross-compile
  safe.
 - alist: Fix for memory overflow access.

 - baculum: Add capability to create filedaemon console and schedule on new
  resource page
 - baculum: Add console messages log API endpoint
 - baculum: Add console messages log envelope
 - baculum: Add job status weather on job list page
 - baculum: Add new icons for job status weather purpose
 - baculum: Add to Bvfs lsdirs and lsfiles API endpoints pathid parameter
 - baculum: Browser paths in restore browser using pathid
 - baculum: Fix #2560 in restore wizard display names encoded in non-UTF
encoding
 - baculum: Fix finding jobs by filename in restore wizard if filename
contains
  whitespace characters
 - baculum: Fix problem with setting hourly schedule - reported by Elias
Pereira
 - baculum: Remove excanvas.js dependency
 - baculum: Update debian files to latest version
 - baculum: Update spec files

 - win32: Backport signing procedures to 11.0
 - win32: Fix #7094 bypass random pwd generation when pwd is provided
 - win32: Fix conditional #define's
 - win32: Fix #7256 Update Windows version detection with latest versions
  (Windows 10).


Bugs fixed/closed since last release:
2560 2579 2587 2588 7079 7094 7168 7207 7214 7247 7256



Release 11.0.0 12 December 2020

11.0.0 is a major release.

New Features:
-
 - New catalog format
 - Automatic TLS PSK encrypted communication
 - Support for Client behind NAT
 - Continious Data Protection (CDP) Plugin
 - Global Director Autoprune flag
 - Events/Audit features
 - New Baculum features
 - Support for GPFS

Misc:
-
 - New Prune Command Option
 - Dynamic Client Address Directive
 - Ability to disable Volume Retention
 - Ask to mount/create volume when the disk space is low
 - Simplification of the Windows FileSet with File=/
 - Use of QT5 for Bat on Windows
 - Support for Windows files with non-UTF16 names
 - Windows Snapshot management has been improved
 - Support for the system.cifs_acl extended attribute backup with Linux CIFS
 - Built-in Client Scheduler
 - Reload command improvements (Keep IP address, Maximum Concurrent
value, ...)
 - Support for GLOB pattern in Console ACL directives
 - Faster CRC32 algorithm

Please see the New Features chapter of the manual for documentation on
the new features.


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] How to remove 6 days duration limit ? (Bacula 9.2)

[Eric Bollengier via Bacula-users]

Hello Dan,

On 1/18/21 16:06, Dan-Gabriel CALUGARU wrote:
> Hello Eric,
> 
> Thank you for your quick answer.
> 
> My version of the Bacula install that I "inherited" is 9.2.1 and I
> thought I can use it as it didn't seem to me really that old  (it dates
> from autumn 2018).
> 
> Indeed, concerning MaxRunTime, by comparing the Bacula Main Reference
> guides for the last stable versions (9.2.x, 9.4.x, 9.6.x), I saw that it
> is was when passing from 9.4.x to 9.6.x that "6 days" has been replaced
> by "200 days" as the time period after which watchdog thread will kill
> any Job.
> 
> Therefore, if there is no other suggestion, I think I will consider the
> upgrade to the last stable version (9.6.7) to solve my problem (the
> other alternative would be to split each volume in several FileSets and
> launching several jobsin order to not exceed 6 days per job)

It is an other possibility that can be very nice, long jobs has the
tendency to be difficult to manage (anything can happen during this 6
days), if you can have 7 parts that you backup individually, you would
reduce the total data to something like 1/7 * total + 6/7 * incr_size.
If the incremental size is about 10% of the total, it becomes very
interesting.

Best Regards,
Eric


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] How to remove 6 days duration limit ? (Bacula 9.2)

[Eric Bollengier via Bacula-users]

Hello Dan,

I believe that this limit was removed few years ago (it is more 
something like 200 days), but I don't think you can control it via a 
directive. I would suggest to install a recent version of the 
Director/SD to handle the situation.


Thanks,

Best Regards,

Eric

On 1/18/21 11:37 AM, Dan-Gabriel CALUGARU wrote:


Hello list,

I'am recent user in Bacula soft and very recent on this list.

I have to perform some large backups for archiving purposes (at least 
4 volumes, each of them with  ~50 TB).


With a rate of about 350 Mbit/s (limited by the network), each job 
should be finished in 2 weeks.


I tried to run the first job, but after 6 days of running, it failled 
with the error :


    13-janv. 14:21 bacula-dir JobId 1156: Error: Watchdog sending kill 
after 518411 secs to thread stalled reading File daemon.
    13-janv. 14:21 bacula-dir JobId 1156: Fatal error: Network error 
with FD during Backup: ERR=Appel système interrompu
    13-janv. 14:21 bacula-sd JobId 1156: Elapsed time=143:53:03, 
Transfer rate=41.99 M Bytes/second
    13-janv. 14:21 bacula-dir JobId 1156: Error: Director's comm line 
to SD dropped.
    13-janv. 14:21 bacula-dir JobId 1156: Fatal error: No Job status 
returned from FD.
    13-janv. 14:21 bacula-dir JobId 1156: Error: Bacula bacula-dir 
5.2.13 (19Jan13):


I saw in the Main Reference Guide v9.2.2  (corresponding to version of 
the Bacula installed software) that  "By default, the the watchdog 
thread will kill any Job that has run more than 6 days" and that the 
default 6 days could be specified by using in the job ressource 
definition :


    Max Run Time =  The time species the maximum allowed time 
that a job may run


Therefore, I prescribed Max Run Time = 0, supposing that this will 
mean no limit for job duration, but the same error occured.


Coud you please help me to know how is the correct manner to remove 6 
days duration limit ?


1) is the value of Max Run Time the only modification to do ?

(some older threads in this forum indicates to make some modifications 
in Bacula source code to remove 6 days duration, since this limit was 
hardcoded in older versions)


2) I have to use Max Run Time or MaxRunTime for the name of this 
variable ?


3) setting it to 0 is a correct way or I must to introduce some large 
integer value (in seconds ?)


Thank you very much for your help !

Dan





___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Bacula fails to purge volume, backup hangs with "waiting for appendable volume"

[Eric Bollengier via Bacula-users]

Hello Uwe,

On 1/8/21 10:09 AM, Uwe Schuerkamp wrote:

Hi folks,

I'm experiencing a weird issue with one of our bacula servers (9.6.5
on ubuntu 18.04 compiled from source).

Most of the backups work just fine, however for one client they fail /
hang consistently as bacula fails to complete purging of a volume from the pool
(I use separate storages & pools for fulls and incrementals, both disk-based).

I'm seeing this message in bconsole under these circumstances:

08-Jan 07:13 director-dir JobId 3988: Purging oldest volume "clientXXX-0284"
08-Jan 07:18 director-dir JobId 3988: Purging oldest volume "clientXXX-0284"
08-Jan 07:23 director-dir JobId 3988: Purging oldest volume "clientXXX-0284"
08-Jan 07:28 director-dir JobId 3988: Purging oldest volume "clientXXX-0284"
08-Jan 07:33 director-dir JobId 3988: Purging oldest volume "clientXXX-0284"
08-Jan 07:38 director-dir JobId 3988: Purging oldest volume "clientXXX-0284"
08-Jan 07:43 director-dir JobId 3988: Purging oldest volume "clientXXX-0284"
08-Jan 07:48 director-dir JobId 3988: Purging oldest volume "clientXXX-0284"
08-Jan 07:53 director-dir JobId 3988: Purging oldest volume "clientXXX-0284"
08-Jan 07:58 director-dir JobId 3988: Purging oldest volume "clientXXX-0284"
08-Jan 08:03 director-dir JobId 3988: Purging oldest volume "clientXXX-0284"
08-Jan 08:08 director-dir JobId 3988: Purging oldest volume "clientXXX-0284"
08-Jan 08:13 director-dir JobId 3988: Purging oldest volume "clientXXX-0284"
08-Jan 08:18 director-dir JobId 3988: Purging oldest volume "clientXXX-0284"
08-Jan 08:23 director-dir JobId 3988: Purging oldest volume "clientXXX-0284"
08-Jan 08:28 director-dir JobId 3988: Purging oldest volume "clientXXX-0284"
08-Jan 08:33 director-dir JobId 3988: Purging oldest volume "clientXXX-0284"
08-Jan 08:38 director-dir JobId 3988: Purging oldest volume "clientXXX-0284"
08-Jan 08:43 director-dir JobId 3988: Purging oldest volume "clientXXX-0284"
08-Jan 08:48 director-dir JobId 3988: Purging oldest volume "clientXXX-0284"
08-Jan 08:53 director-dir JobId 3988: Purging oldest volume "clientXXX-0284"
08-Jan 08:58 director-dir JobId 3988: Purging oldest volume "clientXXX-0284"
08-Jan 09:03 director-dir JobId 3988: Purging oldest volume "clientXXX-0284"
08-Jan 09:08 director-dir JobId 3988: Purging oldest volume "clientXXX-0284"

The volume isn't too big and purging it manually takes only a few seconds.


I would recommend to check the volume content on the catalog side (JobMedia

mostly), I think that I have seen and fixed a similar issue few months 
ago. (in 11.0) It


was a loop, the volume was not purged because some orphan jobmedia still 
present


were blocking the recycling, and the volume was always selected by the 
Purge Oldest algorithm.


Hope it helps!

Best Regards,

Eric



___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Data loss with Hard Links

[Eric Bollengier via Bacula-users]

Hello,

On 2020-12-18 15:16, Andrea Venturoli wrote:
> On 12/15/20 6:49 PM, Martin Simmons wrote:
> 
>> What is the fileset definition?
> 
> Quite huge, both in terms of size (a full backup is around 400GB) and in
> terms of lines (more than 40 ZFS datasets).
> I'm pasting here the relevant parts:
> 
> FileSet {
>   Name="Xx"
>   Include {
>     Options {
>   signature = MD5
>   Accurate=yes

Here you have a mistake (maybe not so big) in your fileset, the Accurate
directive you want to use is inside the Job definition. At the FileSet
Options level, this is used to control which parameter you want to use
to control if a file should be backed up or not. It is something like
"pins" by default ("yes" or "no" have no meaning). New 11.0 version
should control this field and report an error. You should probably also
have the directive like hardlinks=yes, else, they are not controlled.

Hope it helps!

Best Regards,
Eric


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users