On 2020-01-27 10:38, Jean Mark Orfali wrote: > Hello, > > > > I have a Bacula server and 4 clients. The server has 8 cpu and 30 GIB of > ram. I don't know why, it's been 5 days since the first backup started > and they are still not finished. The ram on the server is still used at > almost 100%, 29.30GIB. Do you know why Bacula uses so much memory? > > thank you so much
This is not nearly enough information from which to diagnose the problem. What back-end catalog database are you running? How is it configured? Does it have enough memory? How much data are you backing up, and where are you backing it up to? What are the concurrency settings on ALL of your Bacula daemons? What is the Director currently *doing*? What jobs are running, what jobs are pending, what jobs are scheduled? This would probably be enough to start troubleshooting. Tell us how your system is set up, at high level, and give us an overview of your configuration (with passwords obscured, of course). One unfortunate beginner mistake that I have seen people run into is to run disk-to-disk backups stored on one of the filesystems that is backed up, leading to a job that will effectively run forever as it recursively backs up its own backups. Another common mistake is to put the catalog on a fresh-out-of-the-box, unconfigured, untuned MySQL instance. The only thing that can be said of the typical fresh-from-the-box default MySQL configuration file is that it's usually no longer actively harmful. Whichever database you are using for your catalog, make sure it is properly configured and tuned before you start. (And don't use SQLite as a production catalog DB. Seriously.) -- Phil Stracchino Babylon Communications ph...@caerllewys.net p...@co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
