Hi Giuseppe,
I think there is a misunderstanding here. You are talking about two different jobs. From your first post, you talked about the Job=Fs02Home.2014-10-13_21.00.00_33 and this last post you are talking about Job=MccwHome.2014-10-13_21.00.00_34.
13-Oct 21:00 bl13-dir JobId 1761: Start Backup JobId 1761, Job=Fs02Home.2014-10-13_21.00.00_33
13-Oct 21:00 bl13-dir JobId 1762: Start Backup JobId 1762, Job=MccwHome.2014-10-13_21.00.00_34
Maybe there is a previous error than these ones. I think that because of your "volume use duration = 7 days", bacula used the same volume for backup up these two jobs once, than one week later the volume was still for append (because of your 7 days volume use duration) and maybe bacula could run one of the two backup jobs on this same volume. I mean only one job and the other job was written in the other volume. This is confusing, but the problems begans before these two errors commented about you on your posts.
Bacula is doing it correctly and you should take care about your volume use duration configuration.
If I am correct about what you want, you have two volumes in a pool that you want to backup your jobs with a retention time of a week. You want bacula be using one of the two volumes for a week and change it to the other volume in the next week.
You just have to put in hours your volume use duration to a time less than 7 days to avoid what I commented above. Maybe 6 days and 22 hours (166 hours) should be fine. It should be a time just before the next scheduled job run. From your first post, your job started at 21 h one day and finished 12:58 the next day. So you have to set a time more than 6 days and 14 hours.
About Bacula losting your volume slot number in catalog, this could happen for many reasons. If you normally remove tapes from magazines or move them between slots. If you do that, you can configure an admin job to do an update slots frequently and your catalog will be always updated with the volumes and its slots.
Regards,
Ana
