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