Re: [Bacula-users] Volume errors since update to 2.0.3

The algorithm used by the "simple" LabelFormat is "simple" :-) It uses the NumVols to choose the next name, so will not work if you delete volumes. __Martin > On Thu, 31 May 2007 10:42:48 +0200, le dahut said: > > I've read with attention the doc about Automatic volume recycling and my >

Re: [Bacula-users] Volume errors since update to 2.0.3

Hi, On 5/31/2007 10:42 AM, le dahut wrote: > I've read with attention the doc about Automatic volume recycling and my > configuration seems to be exactly what's described in this doc. > > On the backup disk, there are volumes from ScribeVol0001 to > ScribeVol0109 with 10 missing numbers (which

Re: [Bacula-users] Volume errors since update to 2.0.3

I've read with attention the doc about Automatic volume recycling and my configuration seems to be exactly what's described in this doc. On the backup disk, there are volumes from ScribeVol0001 to ScribeVol0109 with 10 missing numbers (which makes a total of 99 volumes). Those 10 missing volume

Re: [Bacula-users] Volume errors since update to 2.0.3

Bacula recycles "purged" volumes, so I'm not sure what you mean by "pruned" here. What is their volstatus? Note that a volume is not purged until its volume retention period expires, even if all the jobs have been pruned. See "Recycling Algorithm" in

Re: [Bacula-users] Volume errors since update to 2.0.3

I've set LabelMedia = yes and Recycle = yes and there are pruned volumes on my backup media so why doesn't bacula use those volumes instead creating new ones ? My objective is to make backup totally automatic using a USB hd. It's to make users able to backup their server without having a root a

Re: [Bacula-users] Volume errors since update to 2.0.3

Hmm, you are right, Bacula does set the NumVols itself. So the problem is that you have less that 109 volumes in the media table (i.e. some missing in the sequence 1...109). The "simple" LabelFormat with no variable expansion characters expects NumVols to match the pool. There is a hack to allow

Re: [Bacula-users] Volume errors since update to 2.0.3

As you can see below, when I update NumVols to reflect the reality from 99 to 109, NumVols value is updated by Bacula : when it starts it's put back to 99. I really don't understand why Bacula rewrites the value of NumVols and so then generates errors about already existing volume Bacula tries t

Re: [Bacula-users] Volume errors since update to 2.0.3

I tried but : [EMAIL PROTECTED] bacula]# /usr/lib/bacula/sqlite/sqlite /var/bacula/bacula.db sqlite> select * from pool; 1|Default|99|0|0|1|1|864|518400|0|0|20|1|1|Backup|0|ScribeVolume|1|0|0|0|0|0|0 sqlite> UPDATE Pool SET NumVols=109 WHERE Name='Default'; sqlite> select * from pool;

Re: [Bacula-users] Volume errors since update to 2.0.3

> On Thu, 24 May 2007 09:35:18 +0200, le dahut said: > > Here are some additional informations : > > *list volumes > Pool: Default > ... > | 108 | ScribeVolume0108 | Full | 1 | 149066 | 0 > | 5184000 | 1 | 0| 0 | File | 2007-05-06 > 02:01:3

Re: [Bacula-users] Volume errors since update to 2.0.3

Here are some additional informations : *list volumes Pool: Default ... | 108 | ScribeVolume0108 | Full | 1 | 149066 | 0 | 5184000 | 1 | 0| 0 | File | 2007-05-06 02:01:39 | | 109 | ScribeVolume0109 | Full | 1 | 136408 | 0

[Bacula-users] Volume errors since update to 2.0.3

Hello, I used bacula-1.38, since I updated it to 2.0.3, it backuped 4 times ok and then it errors with : """ 23-May 15:53 127.0.0.1-dir: Client1.2007-05-23_15.32.54 Warning: Wanted to create Volume "ScribeVolume0109", but it already exists. Trying again. 23-May 15:53 127.0.0.1-dir: Client1.2007-