Hi, I have been using bacula for a few months now. I recently ran into the mysql table (File) size limitation (on the default myisam table format). I chose to convert the db to innodb format. All this went through okay, but I have started noticing some weird problems with the backups.
Large backup jobs take abnormally long times. Trying to narrow down the problems I could reduce it to this case. All my backups run over encrypted ssh connections to the clients. I spool data to the local disk on the server before I move it to tape. Large backup jobs start off just fine, but after about 45 GB of data is transferred to the server from the client, the tranfer rate drops (from about 20 Mb/s to about 0.2 Mb/s). I have also noticed that the bacula-sd process starts to use upto 99% of the CPU on the server when this happens and stays that way for the remaining duration of the job. I would appreciate any input on this. If I have to, I can go back to MySQL - MyISAM format, but I'd rather not. Smaller backup jobs seem to be working just fine. Aravind. ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
