On Tue, 24 Sept 2024 at 19:50, joseppe mayer <
joseppe...@gmail.com> wrote:
>
> Great. That worked.
>
> But the example jobs are not working. It is supposed to be like this?
>
> Termination: *** Backup Error *** Bacula-Ubuntu-24-dir JobId 1: Fatal error: No Job status returned from FD. Bacula-Ubuntu-24-dir JobId 1: Fatal error: Failed to start job on any of the storages defined! Bacula-Ubuntu-24-dir JobId 1: Storage daemon "File1" didn't accept Device "FileChgr1" because: 3924 Device "FileChgr1" not in SD Device resources or no matching Media Type or is disabled. Bacula-Ubuntu-24-dir JobId 1: Connected to Storage "File1" at localhost:9103 with TLS Bacula-Ubuntu-24-dir JobId 1: Start Backup JobId 1, Job=BackupClient1.2024-09-24_17.47.40_18
Hi Joseppe,
Thanks for your feedback. Good to hear that it started working.
Yes, on deb-based systems the pre-defined storage has defined
non-existing paths. This setting is provided in Bacula packages and it
requires adapting. You can adapt it or create new storage and devices.
The devices you can find in:
[Main menu] => [Page: Storage] => [Button: 'Details' for selected
storage] => [Tab: Configure storage daemon] => [SubTab: Device]
and there you need to edit all devices to set them existing paths.
After that you will need to restart the Bacula Storage Daemon. It can
be done in Bacularis or directly in the console.