Hi,
On 5/9/2007 4:17 PM, Joseph Wright wrote:
> On May 8, 2007, at 2:48 PM, Arno Lehmann wrote:
>
>> Hi,
>>
>> On 5/8/2007 11:27 PM, Sandro Mendes wrote:
>>> Hello people,
>>> I have backups configured to use file volume instead tapes. The
>>> backup are been saved in my HD, so I want to have a volume that
>>> must be erased every week to continue using that same volume (like
>>> a full job).
>>> Here is my config.:
>>> Pool {
>>> Name = MondayPool
>>> Pool Type = Backup
>>> Recycle = yes
>>> AutoPrune = yes
>>> Label Format="Catalog-"
>>> Volume Retention = 6d
>>>
>>> After some tests, the volume doesn't be erased and continue been
>>> incremented.
>>>
>>> What could be wrong?
>> Bacula doesn't erase volumes (that would be pointless for tapes, and
>> Bacula treast files similar to tapes).
>>
>> Instead, you reuse volumes. Bacula recycles a volume only when it has
>> to. To force it to recycle existing volumes, limit the amount of data
>> written to it, the number of jobs, or the time it may be appended to.
>>
>> In your config, you've got none of these settings.
>>
>> I suggest to limt the volume size to a reasonable amount of data,
>> allow
>> Bacula to create new volumes as needed, and limit the number of
>> volumes
>> in the pool.
>>
>> Thus, you can control how much of your disk Bacula uses.
>>
>> Arno
>
>
> If that's the case, then what is the point of having a volume
> retention period? It
> seems like you're saying that setting isn't even honored.
No, it is honored, but Bacula will only recycle a volume when it
absolutely has to. This is to make sure your data remains available as
long as possible.
> In my
> case, if I have to
> guess how many volumes I need in order to limit my disk space, and
> it's going to
> be different for each storage server, that's pretty inconvenient.
Personally, I don't think this is a serious inconvenience, but I either
use tapes - and these are automatically limited in number - or external
disks of limited size - also with an in-built hardware limit :-) - or I
don't use automatic labeleing but prepare the volumes manually.
In most setups I manage, the number of volumes needed becomes more or
less stable after a full backup cycle, and the remaining growth is
easily handled during regular maintenance work.
After all, when I set up a backup system, I do have some estimate of the
amount of data I will need to store.
Also, you can always manually or by script trigger pruning of volumes.
So, while I see your point, I also see a number of ways to prevent much
of the work of managing volume creation.
Arno
> (\_/)
> (o,o)
> ()_() Joseph Wright
> " "
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Bacula-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/bacula-users
--
IT-Service Lehmann [EMAIL PROTECTED]
Arno Lehmann http://www.its-lehmann.de
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
