I've been running Bacula for ~15 years (community/enterprise) and have identified a few areas which are in desperate of improvement:
For an "enterprise" grade backup system, it's amazingly fragile in a few areas (particularly in actual Enterprise networks!) Bacula DOES NOT LIKE and does not handle network interruptions _at all_ if backups are in progress. This _will_ cause backups to abort - and these aborted backups are _not_ resumable Similarly, if there's any kind of disruption between the director and database, the only fix is to restart the director What that means is that Bacula _cannot_ be used with a High Availability database because network interruptions (when switching servers) are part of the HA paradigm. It also means that operators have to be _extremely_ careful about allowing automated or other system upgrades In days of multi-TB backup sets, this is turning into a showstopping problem. As we are an Enteprise customer this has been raised with Baculasystems but been given _very_ low priority. I'd like to hear opinions from the wider community on this Opinion: I know bugs aren't sexy to work on but these need fixing, not being brushed off. This is the difference between LAN-quality and actual Enterprise grade software. _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
