Hi all,
is anyone backing up clusters w/ shared filesystems?
Specifically, I have a number of active-passive pairs where shared
storage is on drbd, mounted on active node only. There is the third
("cluster" aka "floating") ip that is up on active node. So the setup is
- on node A @ 1.2.3.4 : bac
> Hi all,
>
> is anyone backing up clusters w/ shared filesystems?
>
> Specifically, I have a number of active-passive pairs where shared
> storage is on drbd, mounted on active node only. There is the third
> ("cluster" aka "floating") ip that is up on active node. So the setup is
>
> - on nod
On 10/24/2016 03:12 PM, Heitor Faria wrote:
> Hello, Dimitri: perhaps, setip command is what you are looking for
It's 404-compliant so who knows... perhaps.
;)
(I'm talking about "Bacula Console chapter" link under Console Commands
at
http://www.bacula.org/7.0.x-manuals/en/main/Console_Configur
On 10/24/2016 3:28 PM, Dimitri Maziuk wrote:
> Hi all,
>
> is anyone backing up clusters w/ shared filesystems?
>
> Specifically, I have a number of active-passive pairs where shared
> storage is on drbd, mounted on active node only. There is the third
> ("cluster" aka "floating") ip that is up on
On 10/24/2016 04:15 PM, Josh Fisher wrote:
... snipped ...
Yes, this is more or less what I've been doing up until now. The good
news is, it seems I don't have to anymore. Here's what I have working now:
corosync/pacemaker cluster with node A @ 1.2.3.4, node B @ 1.2.3.5, and
cluster ip @ 1.2.3.1
Hello Dimitri,
In your case cluster active/passive with shared storage replicated by
DRBD I think you need to use only one Bacula FD config, the same on
both nodes.
In your cluster in the same time the File Daemon will be running on
the only one node (A or B), not on both. It is the cluster way t
On 10/26/2016 04:13 PM, Marcin Haba wrote:
> Hello Dimitri,
> In your cluster in the same time the File Daemon will be running on
> the only one node (A or B), not on both.
Ah, but this is the point: I *want* it on both. There's "node-local"
data worth backing up on each node as well as "cluster"
Hello Dimitri,
OK, I understood your need wrongly.
That's fine that you solved the FD naming issue.
On 26 October 2016 at 23:13, Marcin Haba wrote:
> You have to be careful when you switch active/passive after failover
> because there can be miliseconds when your cluster can be splitted (it
He
On 10/26/2016 05:14 PM, Marcin Haba wrote:
> Hello Dimitri,
>
> OK, I understood your need wrongly.
no worries
> On 26 October 2016 at 23:13, Marcin Haba wrote:
>> You have to be careful when you switch active/passive after failover
>> because there can be miliseconds when your cluster can be s
On Wednesday 2016-10-26 14:46:25 Dimitri Maziuk wrote:
[...]
> Which is great, if not checking FD name is a bug, *please* don't fix it.
> :)
>
> So all you need is start FDs at boot listening on * and the director
> will automagically get the shared filesystem off of the node that
> happens to hav
10 matches
Mail list logo