VRx

I don't know if it makes sense. This is a hobby project developed in my free time. Bacularis delivers the application in Docker, including the entire Bacula stack, including the Postgresql database engine. https://bacularis.app/doc/brief/installation.html#install-using-docker You don't need to run the database in a separate container. I don't think this is a good solution, as containers for different applications use their own database servers, which creates a significant resource overhead for multiple applications. I also believe that Docker wasn't designed to package entire application stacks into a single container. This makes diagnostics and maintenance more difficult, but that's just my opinion, and I know that many users find this convenient. Docker file is here https://github.com/vrx-666/bacula-server/tree/master if You want to play...

@pk1057 thx for info, I will check entrypoint

@pk1057 try to backup configuration files (move to different place on disk), and try to run container without any configuration files. If it go correctly You could stop Container, and move configuration files back on place, should work without problems (but one thing: user/password/name/host for database should be the same) btw. there is posibility to restore database from bacula backup, but this is more difficult, and can take some time

@murkus I don't know if it is stiil relevant but I found some important info in bacula docs: 1. Maximum Part Size This directive allows specification of the maximum size for each part of any volume written by the current device. Smaller part sizes will reduce restore costs, but will cause additional but small overhead to handle multiple parts. The maximum number of parts permitted per Cloud Volume is 524,288. The maximum size of any given part is approximately 17.5TB. 2. it is useful to set the Maximum File Size to a value smaller than or equal to the configured Maximum Part Size BUT You have to remember that Bacula is not small app, and is was not designed to work inside container, this is my small project to backup content of virtual machines on homelab. Maybe it will never work inside container like it could on physical server.

You can do anything, could be "/mnt/cache2" inside docker container. Next you need to add same Path to monitoring (zabbix webui)

Here is docs which I used with testing configuration. https://docs.baculasystems.com/BEDedicatedBackupSolutions/StorageBackend/cloud/cloud-backup.html#cloud-accounts You must do like a ceph endpoint in the exapmle. I've found somewere that for other cloud storage than amazon You must use: UriStyle = Path Default is Virtualhost.

Yes it is different, I can find manual if You need, I found it previous for testing, but I'm not using cloud backup. I must test it one more time. I thought I had already improved it

What data? Zabbix is monitoring system which needs minimum three parts: zabbix-server - to put it simply: it collects data zabbix-webinterface - is responsible for the ability to display data in the browser zabbix-agent - must be installed on the host from which it collects monitoring data and sends it to zabbix-server (active or passive) it depends on what data you want to monitor, templates are related to the operating system, application or other parameters that can be collected and monitored

Today's image have amazon cloud driver added.

@murkus There is a bug while compilation Amazon Cloud Driver plugin building Bacula from src. I've made an issue for Bacula developers.

@murkus thanks for feedback. Yes, the cloud/s3 driver is not working yet Due to the version change and potentially reported problems, I wanted to stabilize this version. I would like to launch the cloud/s3 driver as soon as possible, but at the moment it is difficult to promise a specific date.

@trashit You must set "cache disks" path were You have mounted cache on Unraid, for example if You have /mnt/cache1234 You must set /mnt/cache1234 Container path can remain unchanged, but You must set at Zabbix Web what You want to monitor as container path, not Unraid path. Monitoring physical disks is tricki, You could mount /proc/diskstats to the container as new "virtual" path, and then prepare Zabbix to monitor diskstats from mounted file instead default /proc/diskstats (by default it will be diskstats from container, not Unraid)

I don't understand what @RBK-Serwer wants to tell. @RBK-Serwer could You please make a thread on Polish Support Forum? https://forums.unraid.net/forum/82-polish-polski/

@Sinister Crayon@professeurx did You create database and database user before You installed Bacula-Server? I've checked on my lab and everything working ok. I've checked postgresql13 postgresql14 and postgresql15 (clean install) That was about curl-101 error with sqlite3 version, but could also happend in postgresql version. Not everything should work in the contenerized version. If you are aware of containerization, you probably know that its purpose is not to run multiple applications within one container and it should not be done. This is necessary here because Unraid out of the box does not support docker-compose. For the same reason, I did not include the Postgres database server in the image like most developers, and for a similar reason it has not been possible to use the MySQL database for a long time. Bacula is a large harvester and should not be run in a container, if it were fully supported Bacula developers would have released images for this purpose long ago. This solution was created for my own needs of backing up data from Unraid virtual machines and several raspberrypi. It was also an alpha project before implementing Bacula Web and later Bacularis in my production environment at work, moreover, it was also my professional development project, for my own satisfaction, and since I put some work into it I felt like sharing it, as you can see, I shared the code on github to which I shared a link, if you want to develop it, please go ahead. For myself and the needs of my Unraid Server, I would run bacula in Docker without UI, because I don't need it, it introduces unnecessary chaos in the configuration files. Of course, you can share ssh, move all configuration files outside the container, only then 90% of people can mess up more and expect help. Just like 90% of users will use 10% of this application's capabilities. What you may want to achieve with this image should be achieved by installing Bacula Server at least in a virtual machine, because then people are surprised that a some process has crashed.

You are doing something that containerization is not intended for. If you need to extend the image with additional functionalities, use the image as a source, install packages, configure and thus use a new image, or use the image creation code and modify it to suit your needs, the image code is published by me on github. Additionally, by modifying the API settings, you may corrupt your copy of the image and require help later (when creating the image, I cannot predict what you will modify, and after updating the image, your settings may be overwritten). Did you provide the ip or hostname by entering DB_Host in the Bacula-Server parameters? Found my mistake, it will be resolved at the next image update. Thanks for the feedback

I don't know what are You talking about. What You put before installing bacula? If You choose postgresql version, You need only to create database user and database in postgresql container/server, If You choose sqlite3 You do not need to do anything exept run bacula container. You must remember that if you tried to install the postgresql version and then want to install the sqlite version, I recommend clearing the paths on the unraid disk where the configuration files are installed. The container installed from scratch updates all passwords - user data, this was tested before releasing a new version of the image. If you want to connect the client to bacula, all you need to do is install the bacula client on the machine that is to be the client, usually called bacula-fd, and then add a new client in the WebUI Bacula-Server. Where do You install client, what are You talking about? What API deploying? What did You tried to do? You do not need to install any API on target machine. You need only bacula-fd. Everything You could configure from Bacule-Server WebUI panel. The exception is the backup of all types of databases, which requires writing a script on the client machine that will dump the database and Bacula will save the dump. The second option is to create remote access to the database and perform the dump from the Bacula server.

Google translate @JonathanM i don't know if there is anybody who can help about bacula image. @professeurx did You update from previous version or this was new installation? Which postgresql server version did You use?

which version did You use? postgresql vs sqlite3 and 11 or 13 maybe 15 ?

You can check if docker is showing unhealthy status and try this kill $(pidof php-fpm7.4) $(pidof apache2) Bacula15 will be available within 1 hour (without s3/amazon plugin yes) There is a problem with s3 plugin and AWS plugin need some additional work. postgresql13 or above is needed for Bacula15 postgresql edition.

@murkus sorry for the delay in replying. There are some known problems with compilation bacula v13.0.4 with S3 driver. Bacula released version 15.x Added Amazon Cloud driver (in replacement of libS3 cloud driver). After the first tests, it doesn't need many changes, but I still want to test the update process to avoid possible problems. Please be patient for a moment

There is no good solution. eth0 inside container is not the same as host interface. You could use host network with zabbix agent container, but macvlan not allow to connect from other vlans/subnets configured on Unraid server, if You use some.

czy polecenie zfs list pokazuje w/w udziały na liście ? jeśli nie to oznacza że to są zwykłe foldery, a nie datasety, musisz je przekształcić

There is an additional change, currently there is no need to define the "Apache log path". Web interface logs currently go to the container (docker) logs.

Application: Bacula - https://www.bacula.org/ Baculum App - https://www.baculum.app/ / Bacularis - https://bacularis.app/ Docker Hub: https://hub.docker.com/r/pwa666/bacula-server GitHub: https://github.com/vrx-666/bacula-server Bacula is a client / server backup application. Baculum/Bacularis is a web application that allows you to easily manage the bacula application. This container combines these applications to form a backup tool with a graphical interface. This container can be run in 5 different versions. Bacula server consists of several components: storage daemon - responsible for saving backups to disk or removable media (tape) bacula director - responsible for the entire backup process, contacts agents on client devices, indicates what resources should be backed up, how and where to send them (storage daemon) file daemon - is a bacula client available for many operating systems, responds to requests from bacula director. A relational database is necessary, where the bacula stores all information related to the performed backups. During installation, you can choose Bacula version 9.6 or 11. Version 9.6 allows you to use the mysql or postgresql database as well as sqlite3. Version 11 allows you to use the postgresql or sqlite3 database. The sqlite3-enabled version is not recommended for larger environments, but allows you to run this application without running mysql / postgresql as a separate container or server. If you already have postgresql or mysql running as your VM or docker application, I recommend choosing this version of the application. If you plan to use the PostgreSQL or MySQL version you should first create an empty database named "bacula", create a password user for that database and grant full privileges to this database for the created user.For mySQL: CREATE USER 'USERNAME' @ '%' IDENTIFIED BY 'PASSWORD'; CREATE DATABASE bacula; GRANT ALL PRIVILEGES ON `bacula`. * TO 'USERNAME' @ '%'; flush privileges; For postgreSQL: create user USERNAME with password 'PASSWORD'; create database bacula encoding 'SQL_ASCII' owner "USERNAME" template = template0; When running container there is some mandatory environment variables. Most important is to set up: SD_Host - should define the IP address at which the Bacula Server will be reachable for computers. If you are using a bridge network this parameter should be the ip of your UnRAID. If you set custom bridge, You shuld type in assigned IP. This variable is passed to the Bacula configuration and later during the backup it is passed to the clients so they can communicate with the Bacula server. The following are necessary when using an external database (postgreSQL, mySQL) DB_Host - database ip DB_Port - database port (could be omitted if default) DB_User - database user DB_Password In addition, there are two important ports that must be exposed: 9095 - Bacula Web 9103 - Bacula Storage The first allows access to the webUI Baculum App. The second is used to receive backups by the server from clients / computers. It can be changed, but you have to change the configuration of Storage Daemon and Bacula Director e.g. via webUI. I recommend that you leave these ports unchanged. There are also necessary paths to folders where configuration files, logs and backups will be saved, these variables are transparent in the UnRaid's docker form, I think that they do not need to be described here. If you have any questions, please ask below. [ Update 2022.05.30 ] End of development for Bacula 9.6 images versions! Older versions of the client work well with the newest server version. The last update of the bacula9.6 code was in December 2020. [ Update 2022.09.15 ] Email notification added. If You want Your's bacula could send emails, first of all You should set container hostname!!! Some of email providers could reject email, if sender will not introduce himself. Container hostname should be Your public reverse dns. Below You have environment variables that must be set to send bacula messages: EMAIL_Recipient - email address where You want bacula send notifications SMTP_Host - address of Your email provider's smtp server SMTP_Port - Your email provider smtp port (check provider documentation) SMTP_User - Email sender login (could be: user@domain or user, check Your email provider documentation) SMTP_Password - Password for email sender account SMTP_Port - smtp port for Your email provider smtp server (check provider documentation) - Yes this is ENV Variable not Docker Port Additionally, it is possible to set email log path pointing to container path /var/log/exim4 [ Update 2022.10.06 ] In the next image update, it will contain postgres client v14.5 (it gives possibility to use a newer version of the postgres server) [ Update 2024.01.02 ] Version 13 available. New Web UI interface Upgrade from version 11 requires change two params: 1. "Bacula WEB port" 9095 -> 9097 (container port) 2. "Baculum config" - path for persistent web configuration: there was /etc/baculum inside container at v11, in version 13 there is /etc/bacularis Be careful, configurations vary! You cannot map the same host folder for /etc/bacularis that was used for /etc/baculum. At the same time, this change forces to create any custom users if you created any in version 11. Unraid template will be updated soon, but it not update if You run it before. [ Update 2024.01.08 ] Postgresql Client v16 Bacularis/Baculum logs redirected to container (docker) logs - no need to bind path for apache (bacularis/baculum) logs [ Update 2025.01.06 ] Version 15: Bacularis updated to version 4.0