Bacula-users

Re: [Bacula-users] Getting bacula to relabel (=rename) disk volumes when recycling

2008-06-02 14:32:49
Subject: Re: [Bacula-users] Getting bacula to relabel (=rename) disk volumes when recycling
From: Dan Langille <dan AT langille DOT org>
To: Pasi Kärkkäinen <pasik AT iki DOT fi>
Date: Mon, 02 Jun 2008 14:32:24 -0400
Pasi Kärkkäinen wrote:
> Hi list!
> 
> Bacula user manual says this:
> 
> http://www.bacula.org/en/dev-manual/Automatic_Volume_Recycling.html
> 
> "Recycling Algorithm
> 
> After all Volumes of a Pool have been pruned (as mentioned above, this
> happens when a Job needs a new Volume and no appendable Volumes are
> available), Bacula will look for the oldest Volume that is Purged (all Jobs
> and Files expired), and if the Recycle flag is on (Recycle=yes) for that
> Volume, Bacula will relabel it and write new data on it."
> 
> So, if I have my pool set up for example like this.. 
> 
> Pool {
>   Name = Pool1
>   Pool Type = Backup
>   Recycle = yes
>   AutoPrune = yes
>   Maximum Volume Jobs = 1
>   Use Volume Once = yes
>   Maximum Volume Bytes = 256M
>   Volume Retention = 1 min
>   Maximum Volumes = 8
>   Label Format = 
> "${Client}-${Level}-${NumVols:p/4/0/r}-${Year}_${Month}_${Day}-${Hour}_${Minute}"
>   Storage = FileStorage1
> }
> 
> I'd assume I get a single backup per volume (file), and the file is named
> always based on the client name, job level, and the date when the job is
> run.. based on the "Bacula will relabel" text above..
> 
> This is what happens when bacula recycles these volumes:
> 
> JobId 7: Start Backup JobId 7, Job=server1.2008-06-02_19.43.04
> JobId 7: There are no more Jobs associated with Volume 
> "server1-fd-Full-0001-2008_6_2-19_32". Marking it purged.
> JobId 7: All records pruned from Volume 
> "server1-fd-Full-0001-2008_6_2-19_32"; marking it "Purged"
> JobId 7: Recycled volume "server1-fd-Full-0001-2008_6_2-19_32"
> JobId 7: Using Device "FSDevice1"
> JobId 7: Recycled volume "server1-fd-Full-0001-2008_6_2-19_32" on device 
> "FSDevice1" (/mnt/backup1/pool1), all previous data lost.
> JobId 7: Volume used once. Marking Volume 
> "server1-fd-Full-0001-2008_6_2-19_32" as Used.
> 
> So.. bacula recycles the volume, but the name of the volume stays the same as 
> it was given
> when it was used for the first time.. 
> 
> Any tips for this? 

In short, give up on getting labels redone when recycling.

To do that is not recycling.

If you are absolutely dead keen on relabeling, delete the volumes 
yourself, via script or otherwise.  ignoring recycling.  i.e. Do not 
Recycle.

If it was me, I'd allow recycling and ignore the labels.  Labels are 
just labels and in my humble opinion, and your milage may vary, having 
the date in the volume name is not useful to me.  I can see the last 
written date for a given volume by inspecting the output of 'list media'.

-- 
Dan Langille

BSDCan - The Technical BSD Conference : http://www.bsdcan.org/
PGCon  - The PostgreSQL Conference:     http://www.pgcon.org/

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users