Re: [Bacula-users] Recycling problem.

Just a comment here. Since you have "volume use duration = 7 days" and your volume was used until 12:58 next day, I'm quite sure (don't know how is your schedule configured) that this volume will be available (append) for use in the next week by your backup jobs. Because of your "volume use duration" configuration, Bacula started to use the same volume two weeks sequentially.

13-Oct 21:08 bl13-sd JobId 1761: Committing spooled data to Volume "000529L4". Despooling 7,153,238,703 bytes ...

14-Oct 12:58 bl13-sd JobId 1761: Despooling elapsed time = 00:01:06, Transfer rate = 108.3 M Bytes/second

14-Oct 12:58 bl13-sd JobId 1761: Elapsed time=15:55:43, Transfer rate=124.6 K Bytes/second

14-Oct 12:58 bl13-sd JobId 1761: Alert: TapeAlert: OK

14-Oct 12:58 bl13-sd JobId 1761: Sending spooled attrs to the Director. Despooling 37,665 bytes ...

14-Oct 12:58 bl13-dir JobId 1761: Bacula bl13-dir 5.2.13 (19Jan13):

Do you have prefer mounted volume set to yes?

Regards,

Ana

On Sat, Oct 18, 2014 at 10:14 AM, Ana Emília M. Arruda <emiliaarruda AT gmail DOT com> wrote:

Yes, the default for "purge oldest volume" is no.

So you have just two volumes in this pool. As Kern said "Yes, there can be typically a few seconds delay between when a volume is chosen for use and when it expires." and this could be the issue you are facing.

Maybe another thing additionally Josh's suggestion that could help you to avoid this problem. I'm talking about having an admin job running after Th backup job to do the prune instead of having the "AutoPrune = yes" configured. Futhermore, this way can make your backups go faster.

I think Bacula's recycling volume algorithm is working correctly and you are facing this problem because of your "volume use duration" time configured. Try to set this value somewhat closer to the time that you want the volume be available for your backup jobs. You can do this based on your last time written values for these volumes.

Best regards,
Ana

On Sat, Oct 18, 2014 at 5:57 AM, Giuseppe Vitillaro <giuseppe AT vitillaro DOT org> wrote:

On Friday 17 October 2014 21:41:49 Ana Emília M. Arruda wrote:

> Hi Giuseppe,

>

> Yes, this could happen if bacula couldn't find a reciclable volume and you

> have the "purge oldest volume = yes" directive configured and this is, for

> Bacula, the oldest volume. The purge oldest volume doesn't respect the

> volume retention period.

>

> Best regards,

> Ana

I was almost sure, but I just "grepped" all

my bacula conf file.

I'm sure the directive "purge oldest volume" is not present

in my files, so the default, for what I can read, should be

a plain "no".

Correct?

This is the definition of my "Incr" pool

Pool {

Name = Incr

Pool Type = Backup

Recycle = yes

Recycle Oldest Volume = yes

Recycle Current Volume = no

AutoPrune = yes # Prune expired volumes

Maximum Volumes = 2

Volume Use Duration = 7 days # 1 week

Volume Retention = 6 days # 1 week - 1

}

G. Vitillaro.

------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users

------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho

_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users