Please, send to the list. It's quite likely I skip over mails sent to me 
directly which originated from the mailing list, and, depending on my 
mood, I might even decide to ignore them.

On 8/29/2006 10:09 PM, Dave wrote:
> Hi Arno,
>    Thanks. I'm not sure i understand all of this, but it does sound like 
> my retention periods are my problem. It sounds like the simplest 
> solution is to set all retention periods in my pools to 27 days would 
> you agree with this?

That would be simple enough, right, and I guess it should solve your 
current problem. You will have situations where you only have one valid 
backup available, though.

> I'm trying to keep this setup as simple as 
> possible, even though i'm adding in modularized client configs, it seems 
> like adding longer retention periods over two months isn't the answer. I 
> think though there is a problem, 27 days *2 is 54, that's not two months 
> exactly, so wouldn't i need to have maximum volume jobs three?

Putting more jobs on a volume will probably not solve this problem (if I 
understand that correctly), because it will keep the volumes active for 
longer. Only after the volume is full, in this case the pre-determined 
number of jobs is stored in it, will the retention time start.

(In most cases, BTW, setting the maximum volume jobs is not the best 
idea; it breaks as soon as a job is not run or jou add another job.)

Personally, I prefer to limit the maximum number of volumes so that I 
can always rely on having two full backup valid, one volume that can be 
recycled (or is purged) and ne that can be active.

I think trying to get schedules which refer to weeks of months in sync 
with fixed retention periods is too much trouble because you can't 
easily decide if your jobs run again after four or five weeks. Which is 
the underlying problem - we need a more systematic calendar :-)

Arno

> Thanks.
> Dave.
> 
> ----- Original Message ----- From: "Arno Lehmann" <[EMAIL PROTECTED]>
> To: <bacula-users@lists.sourceforge.net>
> Sent: Tuesday, August 29, 2006 3:11 PM
> Subject: Re: [Bacula-users] repost: no appendable volumes, bacula 1.38 
> and autolabel
> 
> 
>> Hello,
>>
>> On 8/29/2006 6:10 PM, Dave wrote:
>>
>>> Hi Arno,
>>>     Thanks for your reply. Below is the schedule:
>>>
>>> schedule {
>>> name = "ZeusCycle"
>>> run = full 1st sun at 1:05
>>> run = incremental mon-sat at 1:05
>>> }
>>>
>>> Basically my goal is to have automated disk management. I want a full 
>>> backup
>>> done once a month, incrementals all other times, and to keep two months
>>> worth of backups in my storage area.
>>
>>
>> Ok, then you should set the retention periods to more than two months,
>> and allow three volumes (assuming you use one per month).
>>
>> Not only to fix the problems arising from a (too) tight schedule of
>> pruning and needing new volumes, but also to make sure you actually do
>> have two valid backup sets.
>>
>> Concerning the retention problem, consider this simplified scenario:
>> A volume may be recycled after one month (30 days). It is written on the
>> first Sunday of month 1, being the sixth day in that month. Just what we
>> have this August :-)
>>
>> That volume is valid until 6th August plus 30 days, which is September 5
>> if I calculated correctly. The first Sunday in September, though, is the
>> third day in that month.
>>
>> The result is that this volume is not due for recycling when your job 
>> runs.
>>
>> Adding more months in-between and setting multiple months retention time
>> can even make this discrepancy worse.
>>
>> By the way, another approach would be to use a retention time of, say,
>> 27 days.
>>
>> And all this, of course, provided I've got my date-calculating right...
>>
>> Arno
>>
>>> Thanks.
>>> Dave.
>>>
>>> ----- Original Message ----- From: "Arno Lehmann" <[EMAIL PROTECTED]>
>>> To: <bacula-users@lists.sourceforge.net>
>>> Sent: Tuesday, August 29, 2006 3:34 AM
>>> Subject: Re: [Bacula-users] repost: no appendable volumes, bacula 
>>> 1.38 and
>>> autolabel
>>>
>>>
>>>
>>>> Hi,
>>>>
>>>> On 8/29/2006 4:18 AM, Dave wrote:
>>>>
>>>>> Hi,
>>>>>    I never saw this one go through, so i apologize for the repost.
>>>>
>>>>
>>>> Actually, I saw it, but was too lazy - or busy with other things, if 
>>>> you
>>>> prefer that term ;-) - to reply...
>>>>
>>>>
>>>>> Hello,
>>>>>    I'm using bacula 1.38.11 on a FreeBSD 6.1 box as a bacula 
>>>>> server. I'm
>>>>> having an issue with disk volumes, i'm using an altered example out of
>>>>> the
>>>>> manual for automatic disk volume management, yet i'm getting an
>>>>> inconsistent
>>>>> "no appendable volumes found. Please use the label command" error
>>>>> message.
>>>>> It seems to happen when near full, but i'm not getting rotation. 
>>>>> Here's
>>>>> an
>>>>> error fragment:
>>>>>
>>>>> 25-Aug 04:05 zeus-sd: Job backup_zeus.2006-08-25_01.05.00 waiting. 
>>>>> Cannot
>>>>> find any appendable volumes.
>>>>> Please use the "label"  command to create a new Volume for:
>>>>>    Storage:      "ZeusStorage" (/backup/bacula/zeus)
>>>>>    Media type:   File
>>>>>    Pool:         Zeus_Incremental
>>>>>
>>>>> And here's edited entries for this particular machine:
>>>>
>>>>
>>>> See inline for my observations.
>>>>
>>>>
>>>>> Job {
>>>>>  Name = "backup_zeus"
>>>>>  Type = Backup
>>>>> Level = Incremental
>>>>>  Schedule = "ZeusCycle"
>>>>>  Messages = Standard
>>>>>  Client = zeus-fd
>>>>>  FileSet = "fbsd_zeus"
>>>>>  Pool = Default
>>>>> Full Backup Pool = Zeus_Full
>>>>> Incremental Backup Pool = Zeus_Incremental
>>>>> Storage = ZeusStorage
>>>>>  Write Bootstrap = "/var/db/bacula/zeus.bsr"
>>>>>  Priority = 10
>>>>> }
>>>>>
>>>>> Client {
>>>>>  Name = zeus-fd
>>>>>  Address = zeus
>>>>>  FDPort = 9102
>>>>>  Catalog = MyCatalog
>>>>>  Password = "xxx"           # password for FileDaemon
>>>>>  File Retention = 62 days
>>>>>  Job Retention = 3 months
>>>>>  AutoPrune = yes                       # Prune expired Jobs/Files
>>>>> }
>>>>>
>>>>> Storage {
>>>>>  Name = ZeusStorage
>>>>>  Address = zeus
>>>>>  SDPort = 9103
>>>>>  Password = "xxx"
>>>>>  Device = ZeusStorage
>>>>>  Media Type = File
>>>>> }
>>>>>
>>>>> pool {
>>>>> Name = Zeus_Full
>>>>> Pool Type = Backup
>>>>> Maximum Volume Jobs = 1             # New file for each backup
>>>>
>>>>
>>>> * note this.
>>>>
>>>>
>>>>> Recycle = yes # Bacula can automatically recycle volumes
>>>>> AutoPrune = yes                     # Prune expired volumes
>>>>>  Volume Retention = 2 months
>>>>
>>>>
>>>> * Each volume should be kept for two months after being last used.
>>>>
>>>>
>>>>> Maximum Volumes = 2                 # Keep 2 fulls
>>>>
>>>>
>>>> * There will only ever be two volumes in that pool.
>>>>
>>>>
>>>>>  Accept Any Volume = yes             # write on any volume in the pool
>>>>
>>>>
>>>> * remove this line as it doesn't have any effect and will no longer be
>>>> understood with 1.39 upwards.
>>>>
>>>>
>>>>>    LabelFormat = zeus-full
>>>>> }
>>>>>
>>>>> pool {
>>>>> Name = Zeus_Incremental
>>>>> Pool Type = Backup
>>>>> Maximum Volume Jobs = 1             # New file for each backup
>>>>> Recycle = yes # Bacula can automatically recycle volumes
>>>>> AutoPrune = yes                     # Prune expired volumes
>>>>>  Volume Retention = 2 months
>>>>> Maximum Volumes = 10                 # Keep 10 incrementals
>>>>>  Accept Any Volume = yes             # write on any volume in the pool
>>>>>    LabelFormat = zeus-incremental
>>>>
>>>>
>>>> * similar, though not identical setup.
>>>>
>>>>
>>>>> }
>>>>>
>>>>> bacula-sd.conf fragment:
>>>>
>>>>
>>>> I don't think we need this.
>>>>
>>>>
>>>>> Any suggestions appreciated.
>>>>
>>>>
>>>> Ok, you didn't supply a schedule for the Zeus jobs, so I have to guess.
>>>>
>>>> The full jobs run each month.
>>>>
>>>> I guess it's simply a matter of the retention period not being over for
>>>> any of the volumes when the next jobs start. You can simply verify that
>>>> by doing a list or llist command and verify the volumes times:
>>>> LastWritten and and Retention. Bacula-Web displays a column with the
>>>> date a volume gets out of retention, by the way.
>>>>
>>>> You can easily "simulate" Baculas retention usage by looking at a
>>>> calender and counting the days - keep in mind that a month is 30 days
>>>> for Bacula.
>>>>
>>>> The usual suggestion would be to allow one more volume in the full 
>>>> pool,
>>>> or to shorten the retention period so that a volume that filled in a
>>>> previos month is allowed re recycling when the current job starts.
>>>>
>>>>
>>>>> Thanks.
>>>>> Dave.
>>>>
>>>>
>>>> I hope you can follow these hints - otherwise, post the schedule you 
>>>> use
>>>> and I'll see if it fits to the situation I assume.
>>>>
>>>> Arno
>>>>
>>>> -- 
>>>> IT-Service Lehmann                    [EMAIL PROTECTED]
>>>> Arno Lehmann                  http://www.its-lehmann.de
>>>>
>>>> ------------------------------------------------------------------------- 
>>>>
>>>> Using Tomcat but need to do more? Need to support web services, 
>>>> security?
>>>> Get stuff done quickly with pre-integrated technology to make your job
>>>> easier
>>>> Download IBM WebSphere Application Server v.1.0.1 based on Apache 
>>>> Geronimo
>>>> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 
>>>>
>>>> _______________________________________________
>>>> Bacula-users mailing list
>>>> Bacula-users@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/bacula-users
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------- 
>>>
>>> Using Tomcat but need to do more? Need to support web services, 
>>> security?
>>> Get stuff done quickly with pre-integrated technology to make your 
>>> job easier
>>> Download IBM WebSphere Application Server v.1.0.1 based on Apache 
>>> Geronimo
>>> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
>>> _______________________________________________
>>> Bacula-users mailing list
>>> Bacula-users@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/bacula-users
>>
>>
>> -- 
>> IT-Service Lehmann                    [EMAIL PROTECTED]
>> Arno Lehmann                  http://www.its-lehmann.de
>>
>> -------------------------------------------------------------------------
>> Using Tomcat but need to do more? Need to support web services, security?
>> Get stuff done quickly with pre-integrated technology to make your job 
>> easier
>> Download IBM WebSphere Application Server v.1.0.1 based on Apache 
>> Geronimo
>> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
>> _______________________________________________
>> Bacula-users mailing list
>> Bacula-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bacula-users 
> 
> 

-- 
IT-Service Lehmann                    [EMAIL PROTECTED]
Arno Lehmann                  http://www.its-lehmann.de

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to