On Apr 23, 2007, at 6:25 AM, Damian Lubosch wrote: > I have a machine to backup with about 1-2 million small files (~1kb). > When I run a migration job for about 4 GB of such data the performance > is going down. The tape rewinds very often and the overall performance > is about 3MB/sec. I found out (with top) that the mysql is taking all > the processing power (together with bacula-sd) when migrating many > files. > On the other hand, when migrating only few large files -backups is > running fine with 20-30MB/sec.
Well, I trust you already know about "Spool data" job directive, but in addition you might try setting "Spool Attributes = yes". Since you're dealing with many small files (and attributes scale by filecount, not by data amount), it could help... although I'm not sure how it would work with a migration job. As the manual says: "[I]f you want to avoid the possibility that database updates will slow down writing to the tape, you may want to set the value to yes, in which case the Storage daemon will buffer the File attributes and Storage coordinates to a temporary file in the Working Directory, then when writing the Job data to the tape is completed, the attributes and storage coordinates will be sent to the Director." -- --Darien A. Hager [EMAIL PROTECTED] ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
