On 4/19/19 11:56 AM, Radosław Korzeniewski wrote: > When you implement Bacula in the shared storage cluster, you can failover > backup service from node to node in any direction in just a seconds. Your > shared storage cluster can do it for you automatically as soon as it check > that a service is unavailable.
...as long as you are not actually using it, as in you don't have a backup running. When you fail over during (per Murphy's Law: 99% into) a running backup, the above is no longer entirely correct. You have to restart the backup, from scratch, at a different point in time, and probably having wasted the tapes written by this point as well. If you define your service as "having a usable backup, on schedule", you can't fail that service over "in seconds". Don't get me wrong, I have any number of HA pairs that work exactly as you describe, with configs, spools, and upload areas on DRBD, and so on. Just not bacula. -- Dimitri Maziuk Programmer/sysadmin BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
