Bacula-users

Re: [Bacula-users] Overwriting expired File Volume

2011-02-08 12:56:51
Subject: Re: [Bacula-users] Overwriting expired File Volume
From: Paulo Martinez <martinezino AT googlemail DOT com>
To: bacula-users <bacula-users AT lists.sourceforge DOT net>
Date: Tue, 8 Feb 2011 18:53:55 +0100
Am 07.02.2011 um 16:02 schrieb Josh Fisher:
> On 2/7/2011 6:53 AM, Dan Langille wrote:
>>
>> The answer depends on your Pool configuration directives.
>>
>> It is important to read and understand the volume recycling  
>> algorithm,
>> particularly the fact that Bacula will prefer to create a new volume
>> instead of overwriting a volume:
>>
>> http://www.bacula.org/5.0.x-manuals/en/main/main/Automatic_Volume_Recycling.html
>>
>> Strictly speaking, you do not *have* to delete/relabel, manually or
>> otherwise.
>
> Also note that setting ActionOnPurge=Truncate in the pool will only
> affect new volumes. Existing volumes have to have their ActionOnPurge
> set to Truncate by manually updating the volume in bconsole.


I have a labelformat with timestamps and want that the
volumes are truncated and new ones created if needed.


I was playing with "ActionOnPurge" and saw that "Recycle" needs
to be on/yes for

purge volume action=truncate storage=File allpools

doing the truncate.

(target volume has actiononpurge=Truncate and status=purged)

But why this dependency?

PM







------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users