On 4/25/24 3:17 AM, gaston.gloesener--- via Bacula-users wrote: >
Until now I did run bacula in a virtual machine running the director and storage deamon. The storage daemon was stroing data to files on a shared directory as the storage is on a NAS.Now I have build bacula-sd for the NAS to avoid this duplicate transfer. I have configured one client to use the new storage but while it uses it, it claims to still contact the “old” storage daemon on the bacula node.
Hello Gaston, A bconsole `show job=xxxx` will show what the Director knows about this job. It is quite possible, and my guess that one of two possible things has happened: #1: You forgot to issue the bconsole reload command #2: The Director has reached its default configuration reload limit of 32 and is no longer reloading You can check with: * status director ...and look at the header line: `Daemon started 24-Apr-24 18:55, conf reloaded 24-Apr-2024 18:55:27` If the `conf reloaded` time is not recent, then you have hit #2 above and simply need to restart the Director. Hope this helps, Bill -- Bill Arlofski w...@protonmail.com
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
