(Reposted with proper Subject) 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, shared storage mounted a /raid on the active node.
Bacula-fd is started at boot on both nodes and is left pretty much a the
default config. Cluster ip is managed by the pacemaker resource agent
and is up'ed on an existing physical interface that bacula-fd is already
bound to.
node A bacula-fd.conf:
FileDaemon {
name = nodea-fd
...
}
node B bacula-fd.conf:
FileDaemon {
name = nodeb-fd
...
}
bacula-dir config:
Client {
name = nodea-fd
address = 1.2.3.4
...
}
Client {
name = nodeb-fd
address = 1.2.3.5
...
}
Client {
name = cluster-fd
address = 1.2.3.1
...
}
Job {
name = nodea-etc
client = nodea-fd
fileset = etc
...
}
Job {
name = nodeb-etc
client = nodeb-fd
fileset = etc
...
}
Job {
name = cluster-raid
client = cluster-fd
fileset = raid
...
}
The trick is that there is no bacula-fd with the name "cluster-fd"
running anywhere. Yet the job "cluster-raid" Just Works(tm).
--
Dimitri Maziuk
Programmer/sysadmin
BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ The Command Line: Reinvented for Modern Developers Did the resurgence of CLI tooling catch you by surprise? Reconnect with the command line and become more productive. Learn the new .NET and ASP.NET CLI. Get your free copy! http://sdm.link/telerik
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
