Dear all, I'm usually not prone to responding to posts w/r to "DB religions", but OTOH I believe that most of the mysql problems may have resulted from historical issues, like using myisam as the storage backend, *not* using mariadb and so on.
We run 5 bacula instances, all backed by mariadb (5.x and 10.x), and they tick along just fine. The largest instance has 600 million rows in the File table (it had over one *billion* at some point in the past) with a total DB size of around 140GB, and backup performance is just fine (the db server which also runs the bacula processes has a mere 48GB of RAM, we've limited mariadb / innodb's buffer pool size to exactly half of that; it also serves as an smb / nfs share for other backup systems like Oracle Enterprise manager, Veeam and so on). Sure, restores can take a while when bacula pulls together all the needed information from fulls, incrementals, diffs and what not so you'll be able to get a coffee (and probably finish it) until you'll be greeted with the restore marker prompt in bconsole, but so what? Restores aren't needed all that often, and as long as backups (we run 16 parallel jobs to disk storage) run more or less maxxing out the disk / network throughput, I don't see any reason to change a running system. There's always brestore / bscan to help you restore stuff instantly from any given job if you don't have the 15 minutes it might take bacula to piece together a complete file list. I don't recall exactly when we switched from Amanda to Bacula, but I think we're probably approaching a decade of operating bacula in a production environment. The issues I've had with bacula that can be traced to having been caused by using MySQL / MariaDB as the db backend can be counted on one hand, and yes, that includes the artificial limbs of pirate captains too as the number is closer to zero than to one. ;-) Don't get me wrong, I love postgres and have used it successfully in other projects in the past, but I still prefer mysql / mariadb for its ease of installation and administration. One of these days I *will* get around to using pg for my bacula catalog, I promise ;-) As to the original poster's query: Maybe your problems aren't related to mysql, but some other issue like a network / disk / tape bottleneck? Some more information on the bacula version, director / db machine specs and backup media / tech used would be really helpful in tracking down your problem. All the best, Uwe -- Uwe Schürkamp | email: <uwe.schuerk...@nionex.net> Arvato Systems S4M GmbH | Sitz Köln | Amtsgericht Köln HRB 27038 ------------------------------------------------------------------------------ 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
