On Wednesday 2019-04-24 22:39:01 Heitor Faria wrote: > Hello Radoslaw, > > > You cannot run two always on replicated directors. Why? Every single > > Bacula Director requires a separate copy of the catalog database. So, > > two always on directors require two separate databases, so you cannot > > setup online replication in this setup. It just won't work. > > This is not very accurate.
Not accurate but the conclusion is correct. > I was able to run several concurrent jobs using to Directors with the > same name, same Catalog and same clients: [ > https://pasteboard.co/IbHjY0J.png | https://pasteboard.co/IbHjY0J.png ] > I just used different Pools and Storage. The plugin jobs failed for And different job configurations. > obvious reason. The failed plugin Jobs and Load Balancing might be > solved using the Maximum Director Concurrent Jobs and not allowing > duplicated jobs. The Storage and Pools SPOF can be resolved using > Bacula Enterprise Shared SAN plugin or a NFS share for both SDs (disk > only). The Catalog SPOF Pgsql might be solved with Master - Master > replication. Configuration replication with rsync or any trivial > mechanism, that is very easy to manage. For bconsole and Web GUI, you > can even use a DNS failover as the cherry on the top. I will keep > testing. I very much dislike the use of rsync tool in HA projects. We should start thinking out of the usual sysadmin perspective and try to realize what change in the bacula as a system would be needed to make the things discussed in this thread possible rather than proving that we can make fragile and hard to maintain proof of concept. Regards! -- Josip Deanovic _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
