On 02.02.2010 00:46, Timo Neuvonen wrote:
> "Thomas Schweikle" <t...@vr-web.de> kirjoitti viestissä
[...]
>>Does this mean volumes aren't created automatic? I do have to create
>>them manually?
>
> At first, I didn't notice there was a recycle=yes option in the conf.
I was sure I had put it in ;-)
> The volumes can be (if configured so) created automatically, until the
> configured limit for maximum number of volumes is reached. Limiting the
> number (and the size) of the volumes as you did is a good idea on file
> storage, because otherwise you would run out of disk space sooner or later.
> But the automatic creation will stop when the maximum number is reached.
I have limited the number of allowed volumes, volume size, volume
jobs. Volume retention is set to an useful value (14d). Automatic
pruning is on.
AutoPrune = yes
Volume Retention = 20 days
Maximum Volumes = 14
Maximum Volume Jobs = 6
Maximum Volume Bytes = 4.3g
> Now you have specified recycle=yes, which means the existing volumes will
> then be used again starting from the oldest expired one - so the old ones
> will not be deleted but re-used. What this means, is that your volume names
> that include (old) timestamps will become very misleading since they'll
> contain data that is newer than the volume name could make one think. But no
> technical problem there so far.
That is an argument. I have changed volume labelling to use simple
counts. Might be less confusing.
Label Format = "${Client}_Inc_${Count}"
> So, is the problem now that
> - not a single volume gets created (there aren't 20 volumes yet)
> -- if so, then there is a bug in the conf I didn't notice
This is the case: not a single volume is created automatically. I
have to create the volume manually. But I do not see any error I've
made with my configuration.
> or
> - no new volume names appear after there already exists 20 volumes?
> -- if so, this is propably due to possible misunderstanding I tried to
> explain above
Since there are no volumes at first start with this configuration,
the limit isn't reached jet. The volume shall be created.
> btw, maybe you are aware of this, but any changes to pool definition need to
> "be taken into use" with update pool command in bconsole.
I have tried this too, but it did not change anything. Volumes are
just not created. I can create them manually, but this is not really
an option :-(
Maybe it could help if one has a running configuration with
autocreating volumes as needed? Maybe it is more easy to compare my
configuration against a working one?!
--
Thomas
------------------------------------------------------------------------------
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
