Hello everybody. Last friday when ran into a problem with the FileId attribute of the File table. Using Bacula for some years now the FileId reached its maximum of 4294967295 and Bacula wasnt able to backup any more files.
I found a recent post concerning such an issue. The solution was to alter the File table and change the FileId to BigInt(12). After doing this backups are working again as expected but I'm a bit concerned about the internal handling of the FileId field. Are the Bacula daemons able to handle bigger numbers or may we run into loss of data with that solution? Is there any other solution than that to solve that problem? Restarting with a blank catalog is only an option if we somehow can restore data from jobs stored in the old catalog. Is it possible to simply configure two catalogs in the bacula-dir.conf and reference just one to the client(s)? Is the bacula-dir able to find data in the second (old + full) catalog? What about duplicate JobIds? Thanks for any help. Greetings, Michael PS: The Bacula-Website still looks pretty good. ;^) -- Every time you install Ubuntu God kills a penguin ... ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
