Hi,
Doug Sampson wrote:
If I'm right, you can
a) safely ignore the message, or
b) exclude this file from the backup. This not only gets rid of the
message, it also saves space because this file would be useless to
restore. If you've got a catalog backup, of course.
How do I prevent Bacula from trying to 'stat' this file? The error message
doesn't pop up during the backup- only during the initialization of the
backup job to be performed.
The natural solution would be to exclude the file from the relevant fileset.
Arno
Guess I need to read sqlite man...
~Doug
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
--
IT-Service Lehmann [EMAIL PROTECTED]
Arno Lehmann http://www.its-lehmann.de
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
