Hello,
2014-05-23 17:30 GMT+02:00 Josh Fisher <jfis...@pvct.com>:
> At failover, there simply is no way for the node taking over the primary
> role to determine the state of the interface on the failing node. It is
> up to software to handle errors caused by the interface going up and
> down and reopen sockets. Bacula could be made more cluster friendly,
>
When you deploy bacula-fd on the cluster service then it will be a fully
cluster friendly solution. I do not understand why do you suggest something
different.
> (which btw would also make it more robust with regards to handling
> network problems),
It is the different problem. Yes, bacula could be a more robust regarding
network problems.
> but as it is, the only safe way I see to do this is
> to let the CRM start/stop bacula-fd dependent on the cluster IP
> resource. Another instance of bacula-fd can separately handle backing up
> any non-cluster resources on the node if needed.
>
Yes.
In real world bacula-fd can successfully handle both cluster and
non-cluster resources. I've deployed a lot of real clusters this way
including Linux, Unix and Windows solutions. You can ignore that, no
problem.
best regards
--
Radosław Korzeniewski
rados...@korzeniewski.net
------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
