Hi all I have a problem with bacula deleting files from verify initdb jobs (i am using version 5.0.2-1 on CentOS 5.5 x86_64).
AFAIK, the file retention period can only be defined on the client resource. Moreover, bacula strictly purges all database entries after the retention period has expired, regardless of their origin (normal backup job or verify initdb job). It would be desirable to keep all entries (or, at least, have different retention periods) for database entries that belong to "verify initdb" jobs. As bacula works now, these initdb jobs get lost, and the next verify job gives lots of "new file" messages - hence it essentially reports failure without reason. The fileset of my verify job is not very large, so keeping these entries somewhat longer than ordinary files would not be a space problem (since these files are contained in each backup anyway). Is this a known problem, or is there already a solution? Regards --Marcel ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
