On Fri, 13 Sept 2024 at 21:00, Rui Loureiro <
ruilou...@gmail.com> wrote:
> That solved the problem!
Hi Rui,
Thanks for the confirmation that it started working and for describing
us the way how you use Bacula and Bacularis.
> I didn't realize I changed it. My goal was to create a "restore" user that has only access to the restore view. But so that this user could see the progress of the restore, I also gave access to the RestoreFiles job, which in my case is the generic job for file recovery. The problem is that in the Job Detail view the user also has access to modify the job, and I tried to restrict this with ACLs. Something went wrong and I must have done something wrong along the way. Furthermore, I noticed that these settings are also saved by the ConfigBacula class, and because of the modifications I made to the write() function, there was an error because the extension is cfg and not conf. To add to the problem, I don't want to change the organization of bacula-dir.conf. We mainly make backups of video files that are related to productions. We have Pools that contain the volumes of these productions so that we can recycle the volumes when the productions end. That's why we organize the various jobs for each production in bacula-dir.conf into sections that are related to the productions. We do the same for Pools and FileSets. Therefore, when Bacularis generates resources for the Director, I try to reorganize the file. That's where the problem must have arisen.
The restore user, that you mentioned, can be configured in Bacularis
that it will have access to restore function and only to selected
backup jobs. For start I would propose to watch these three video
guides, that show how to do it. Specially the first one might be
useful:
1) Bacularis - configure custom interface for selected users
https://www.youtube.com/watch?v=9HbEh1P4b6w
2) Bacularis Web - new user wizard
https://www.youtube.com/watch?v=dFJ13xzWda8
3) Bacularis - set user access to selected Bacula resources
https://www.youtube.com/watch?v=OFaLBJ_n8a0
> As the organization of files and production projects is always the same, we have templates that we use to create resources manually in bacula-dir.conf. Then we replace the text in the resources, e.g. "ProductionName" is the text in the template is replaced by "RealProductionName". Bacularis Configs can be used for this type of task if, for example, in the Job resource we can use a Config that has a Pool resource instead of an already existing Pool resource. That could be a good improvement, I think.
Yes, Bacularis configs can be useful for repeatable and automated
tasks on the Bacula configuration.
> We would always have to do the replacement manually (e.g. in VS Code), but we could use Bacularis filtering features to remove the resources at the end of productions.
>
> One more time, thank you very much for your help and advice.
>
> Bacula and Bacularis rules together!
:-D