On 20 Feb 2006 at 20:06, Boniforti Flavio wrote: > In data Mon, 20 Feb 2006 19:56:07 +0100 > Boniforti Flavio <[EMAIL PROTECTED]> scriveva: > > > I just discovered this: > > > > 19-Feb 18:43 dropbox-fd: RestoreFiles.2006-02-19_18.43.22 Error: > > attribs.c:339 File size of restored file > > /tmp/bacula-restores/var/lib/mysql/bacula/File.MYD n > > ot correct. Original 115936, restored 116236. > > > > 19-Feb 18:43 dropbox-fd: RestoreFiles.2006-02-19_18.43.22 Error: > > attribs.c:339 File size of restored file > > /tmp/bacula-restores/var/log/mysql/mysql-bin.000007 > > not correct. Original 662506, restored 663027. > > > > What could the problem be? > > OK, I "self-answer" me: maybe those files where "in use" when backup > started, and in the restore process something (WHAT?) went wrong?
My theory: When the FD took the file size, it was X. While backing the FD was backing the file it, the file size changed to size Y. My advice: Don't backup files that can change. Use mysqldump instead. Then backup the output of that. You can invoke MySQL dump in the RunBefore job. -- Dan Langille : Software Developer looking for work my resume: http://www.freebsddiary.org/dan_langille.php ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
