Bacula-users

Re: [Bacula-users] Volumes getting reused before meeting retention

2009-12-15 06:46:32
Subject: Re: [Bacula-users] Volumes getting reused before meeting retention
From: vishal veerkar <vishalveerkar AT gmail DOT com>
To: bacula-users <bacula-users AT lists.sourceforge DOT net>
Date: Tue, 15 Dec 2009 17:13:03 +0530
Hi Timo.


Thanks for  quick response.

Yes, the problem occurred because initial retention was changed and these volumes were present from start and hence using the same old config. After goggling i came to know that whenever retention is configured, the first volume created is used as prototype for the next volumes and hence inherits the same characteristics.

For resolving the problem i have gone to bat and manually edited all the problematic volumes and set the retention to new configuration policy and i think this will resolve my problem.


Regards,

Vishal Veerkar

On Tue, Dec 15, 2009 at 2:54 PM, Timo Neuvonen <timo-news AT tee-en DOT net> wrote:
"vishal veerkar" <vishalveerkar AT gmail DOT com> kirjoitti viestissä
news:d495389e0912142254u174d4e80h53c499b3379d64b8 AT mail.gmail DOT com...
> Hi All,
>
> I am using Bacula 2.2.8 and now in phase of migration for latest version
> but in mean time i have to run the current setup. Recently i have noticed
> that the Volumes are getting reused before the retention period is met.
> The problem persist with some of the volumes and not all. The Job and File
> retentions also set for 12days.
>

Are you aware that changing pool specs does NOT affect directly to the
existing volumes? Sounds like your volumes had different retention periods,
since some of them have this problem and the others don't.

a) you may use "llist media" (note the double-l like 'long') to view current
retention periods

b) if necessary, use bconsole "update" command to update the existing
volumes to follow the conf

Also remember that after altering the conf file you'll need to either
restart the director, or 'reload' the new conf before it takes control


> Below is the example for illustrating the situation.
>
> 05-Dec 03:55 bacula-dir JobId 17183: There are no more Jobs associated
> with Volume "Vol0048". Marking it purged.
> 05-Dec 03:55 bacula-dir JobId 17183: All records pruned from Volume
> "Vol0048"; marking it "Purged"
>
> 2009-12-14 10:10:35 bacula-dir JobId 17822: There are no more Jobs
> associated with Volume "Vol0048". Marking it purged. 2009-12-14 10:10:35
> bacula-dir JobId 17822: All records pruned from Volume "Vol0048"; marking
> it "Purged"
>
>
> Pool {
>   Name = Pool_8
>   Pool Type = Backup
>   Recycle = yes                         # Bacula can automatically recycle
> Volumes
>   AutoPrune = yes                       # Prune expired volumes
>   Volume Retention = 12 days            # 12 days
>   Maximum Volume Bytes = 32212254720    #30GB
>   LabelFormat = "Vol"
> }



------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users



--
With regards,

Vishal Veerkar
------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users