> First let me thank you all for your responses, i really appreciate > them. As Joe, i think the problem here are the bacula jobids, ¿ is > there any way to say bacula to start from (let say) job id 9000000 ? > i think that's an easy way to fix all the problem as i will be able
I am not familiar enough with mysql and it's workings but with postgres, the jobid column in the job table is defined as a sequence - job_jobid_seq. When this is first created it can be seeded with whatever starting value that you wish. e.g. \d job_jobid_seq Sequence "public.job_jobid_seq" Column | Type | Value ---------------+---------+--------------------- sequence_name | name | job_jobid_seq last_value | bigint | 328864 start_value | bigint | 1 increment_by | bigint | 1 max_value | bigint | 9223372036854775807 min_value | bigint | 1 cache_value | bigint | 1 log_cnt | bigint | 31 is_cycled | boolean | f is_called | boolean | t So, you could have one server start at 1 and another start at some number that you know the first server will never reach (assuming you want them to have unique job id sets forever). hope this helps, --tom ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users