On 2020-01-28 11:06, Thomas Lohman wrote: >> Hello >> >> I am used to this principle with Linux but I don't understand why it just >> takes it when Bacula is working and it slows down the server so much that I >> can no longer access it in ssh. > > How is your storage allocated on the server? i.e. how are things > partitioned with regard to your backup disks and your database? If your > DB is located on the same physical disks as your OS and/or your actual > backup data then you could see such "freeze ups" while Bacula is running > due to I/O limitations. I find it helps to separate the OS, DB data and > any Bacula storage volumes so they are all on separate disk devices if > possible - separate controllers even better.
In particular it is a VERY BAD IDEA to have your catalog DB and your Bacula backup storage on the same physical devices. Both of those are high-I/O operations. You can EASILY saturate your I/O with a configuration like this, especially if you're writing to RAID5 where every write requires a parity calculation. -- 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