On Tuesday 2019-04-16 12:28:45 Dimitri Maziuk via Bacula-users wrote: > On 4/16/19 10:27 AM, Josh Fisher wrote: > > Running jobs will fail, but the automated "Reschedule On Error" > > feature > > allows restarting them after the fail-over. Also, fail-over doesn't > > affect scheduled jobs that haven't started yet at the time of > > fail-over. Putting the OS on DRBD and running in a VM (or container) > > allows continuation of backup services without operator intervention. > > What is wrong with that? > > Nothing, I just doubt migrating the VM itself is all that seamless and > stable without operator intervention. Admittedly, I have not played with > that in years... but last I looked if you actually *failed* without an > orderly VM shutdown, booting it up on the other node was a crap shoot.
It's working just fine even with opensource technology for years. I used live migration of KVM virtual machines in 2010 and it worked without problems. While working in the virtual machine using ssh, a user wouldn't even notice that the virtual machine was migrated. The only problem for was a particular cluster component that was unstable. RHEV (RedHat Enterprise Virtualization) or oVirt solved that by introducing a solution that didn't relay on complex and unstable cluster components. Regards! -- Josip Deanovic _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
