On 12/02/2015 03:08 PM, Rich Otero wrote:
> Thanks, Dimitri. I am backing up shared data. I've done some testing with
> independent bacula-fd instances running at the same time with identical
> configuration on both nodes. Bacula-dir is configured to connect to the
> client at the floating IP addre
On 12/2/2015 1:22 PM, Rich Otero wrote:
Hello,
I have a system where the Bacula File Daemon must run on a
high-availability pair of servers. I have some services managed by
Pacemaker, but I have not configured this yet for the Bacula services.
If I configure bacula-fd identically and start
Thanks, Dimitri. I am backing up shared data. I've done some testing with
independent bacula-fd instances running at the same time with identical
configuration on both nodes. Bacula-dir is configured to connect to the
client at the floating IP address. It seems to work well. I have failed
over the
On 12/02/2015 12:22 PM, Rich Otero wrote:
...
> configure Pacemaker to start and stop bacula-fd on the HA servers so that
> only one has it running at a time. If it is the latter scenario, then I can
> setup init to start bacula-fd on both servers and simply configure
> bacula-dir to find its clien
Hello,
I have a system where the Bacula File Daemon must run on a
high-availability pair of servers. I have some services managed by
Pacemaker, but I have not configured this yet for the Bacula services. If I
configure bacula-fd identically and start it on both servers in the HA
pair, will there
