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.
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

Reply via email to