I installed 3.0.3 a month or so prior to 5.0.0 being released, with a view to using bat for restores, as it made life much easier for commandline-phobes, and it performed very well.
It was then updated to 5.0.1 and restores of anything more than a handfull of files became unusably slow. I noted all the discussion from others seeing similar effects which largely seemed to be caused by extra mysql indexes having been added - something I had not done. Incorrect mysql tuning was also blamed. I then saw a comment by someone who said that it was slow in bat but OK using bconsole and I have just completed the following tests: The director is on the same machine as the mysql database - a default, untuned Fedora 11 mysql 5.1.37. Using bat from a Gb connected machine to restore a tree containing 72,684 files, the progress bar on the GUI takes two minutes to complete Stage 1 -"Processing Checked Directories". Stage 2 - "Filling Database Table" takes about 80 minutes. During this mysql resource usage on the database machine is less than 1% CPU and RAM and bat resource usage is moderate. Switching to bconsole on the Gb connected machine and restoring the same job, it takes about 1 second at the "Building directory tree" stage and 0.5 second at the "72,684 files marked" stage. While I did not spend a lot of time on 3.0.3, I am quitre sure this problem was not apparent then. Regards, Richard ------------------------------------------------------------------------------ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
