Re: [Bacula-users] Re-2: Re-2: Sending spooled attrs to the Director takes a long time
Zitat von Carsten Pache pa...@vgr-gruppe.de: An additional option is that after upgrading the database server it returned to the default database config file which in a lot of cases is optimized for machines with a few MB (yes MB) of memory. I do not remember that I had to change the defaut database configuration when I installed Bacula 5.0.3 two years ago. So which config file do you mean? Can you give me some hints what I should change in this file? My Bacula server has 2 GB RAM. For a high insert rate you normaly have to extend the size or number of redo logs. For MySQL this might be possible in /etc/my.cnf or the like but i don't use MySQL so you have to RTFM. What confuses me is that the part of the backup job that fetches the files from the server takes nearly as long as before, but the sending of the spooled attributes to the Director takes extremely long (Bacula 5.0.3: 3 minutes, Bacula 5.2.5: 7 hours 45 minutes). If the current (new) config of MySQL is not suitable, then I would expect that everything slows down. I will take a look into the MySQL manual, but as the Bacula server is responsible for backup only, it might be faster to setup the server from scratch. If you can afford do a setup from scratch. There was at least one bug in the upgrade process of Ubuntu/Debian regarding the database. I really doubt that tunning the database will get you down from more than 7 hours to something useable, so something other must be horrible wrong. Regards Andreas -- LogMeIn Central: Instant, anywhere, Remote PC access and management. Stay in control, update software, and manage PCs from one command center Diagnose problems and improve visibility into emerging IT issues Automate, monitor and manage. Do more in less time with Central http://p.sf.net/sfu/logmein12331_d2d ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Re-2: Re-2: Sending spooled attrs to the Director takes a long time
Only applicable to InnoDB tables, but then you ARE using InnoDB, not MyISAM right? *Right?* Sorry that I have to ask this, but: How do I know if my MySQL installation is using InnoDB tables? Edit /etc/my.cnf to change innodb_log-file-size and innodb_log_files_in_group. Current values are: - innodb-log-file-size = 5242880 - innodb-log-files-in-group = 2 Do you have a recommendation which values I should use? That said, unless your Bacula catalog is on a separate machine from your Director, 2GB isn't very much RAM for a machine that's running both your Director and your catalog DB. Especially since in my experience, most servers running 2GB of RAM or less are also usually running a 32-bit OS even if they're on 64-bit-capable hardware. In my case it is a 64-bit Ubuntu Linux. Carsten -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Re-2: Re-2: Sending spooled attrs to the Director takes a long time
An additional option is that after upgrading the database server it returned to the default database config file which in a lot of cases is optimized for machines with a few MB (yes MB) of memory. I do not remember that I had to change the defaut database configuration when I installed Bacula 5.0.3 two years ago. So which config file do you mean? Can you give me some hints what I should change in this file? My Bacula server has 2 GB RAM. For a high insert rate you normaly have to extend the size or number of redo logs. For MySQL this might be possible in /etc/my.cnf or the like but i don't use MySQL so you have to RTFM. What confuses me is that the part of the backup job that fetches the files from the server takes nearly as long as before, but the sending of the spooled attributes to the Director takes extremely long (Bacula 5.0.3: 3 minutes, Bacula 5.2.5: 7 hours 45 minutes). If the current (new) config of MySQL is not suitable, then I would expect that everything slows down. I will take a look into the MySQL manual, but as the Bacula server is responsible for backup only, it might be faster to setup the server from scratch. Carsten -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
