On 2018-04-11 01:59, Kern Sibbald wrote:
I have never used two Client definitions to backup the same machine, but
in principle it would work fine.
The closest I have is a "cluster ip" floating between two machines, with
3 client/job definitions: one for each physical machine (backing up /etc
and crontabs) and one for the cluster ip (backing up DRBD filesystem
mounted on the host that has cluster ip).
The only thing non-obvious to me was that bacula-fd running as
FileDaemon {
name = nodea-fd
...
}
will happily answer to (bacula-dir)
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 = cluster-drbd
client = cluster-fd
fileset = drbd
...
}
(I.e there is no FileDaemon named "cluster-fd" running anywhere but the
Job and Client definitions for it work just fine.)
Dima
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
