Hello, the history is I have upgrade from 2.4.x to 5.0.1 step by step incl. the database. On 2.4.x I'd run some time the init catalog job for different fd's.
After upgrade I would do that now more like scheduled so I made first an init catalog and afterwards directly an Job Level Catalog. The problem looks like now that there files found from the init catalog job which has to been put in the catalog long time ago Here some messages from the catalog job: ... 19-Oct 00:43 backup-dir JobId 9426: Warning: The following files are in the Catalog but not on disk: 19-Oct 00:43 backup-dir JobId 9426: /var/lib/dpkg/info/libcurl3.postinst 19-Oct 00:43 backup-dir JobId 9426: /var/cache/man/pt/index.db 19-Oct 00:43 backup-dir JobId 9426: /var/cache/man/fr/index.db These files are really not on the disks, neighter at init catalog run nor at catalog run. So back to my question: Is it possible, there is a problem with the init catalog in bacula which do not delete old files from database at init catalog job? How can I fix them e.g. manually first? I think it is enough to cleanup something in the database to have an work around before I execute the next init catalog job, isn't it? The job and fileset definition for the job is the same. The level will be overriden by manually modification of the level or by the schedule. Cheers.... Pierre ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users