Hi MattB!

In the Bacula on-line manual

http://www.bacula.org/rel-manual/Automatic_Volume_Recycling.html

you can find the recycling algorithm, that Bacula uses. I quote the
relevant part here too:

"The full recycling algorithm that Bacula uses when it needs a new
Volume is:

    * Search the Pool for a Volume with VolStatus=Append (if there is
more than one, the Volume with the oldest date last written is chosen.
If two have the same date then the one with the lowest MediaId is
chosen).

    * Search the Pool for a Volume with VolStatus=Recycle (if
there is more than one, the Volume with the oldest date last written is
chosen. If two have the same date then the one with the lowest MediaId
is chosen).

    * Prune volumes applying Volume retention period (Volumes
with VolStatus Full, Used, or Append are pruned).

    * Search the Pool for a Volume with VolStatus=Purged

    * Attempt to create a new Volume if automatic labeling enabled

    * Prune the oldest Volume if RecycleOldestVolume=yes (the Volume
with the oldest LastWritten date and VolStatus equal to Full, Recycle,
Purged, Used, or Append is chosen). This record ensures that all
retention periods are properly respected.  

    * Purge the oldest Volume if PurgeOldestVolume=yes (the Volume with
the oldest LastWritten date and VolStatus equal to Full, Recycle,
Purged, Used, or Append is chosen). We strongly recommend against the
use of PurgeOldestVolume as it can quite easily lead to loss of current
backup data.

    * Give up and ask operator."

I suggest you, that go through these steps, and try to find out, why
your configuration does not choose one (the right one for your needs)
from these steps.

It may be important for you too the following paragraph:

"The Volume Retention period takes precedence over any Job Retention
period you have specified in the Client resource. It should also be
noted, that the Volume Retention period is obtained by reading the
Catalog Database Media record rather than the Pool resource record. This
means that if you change the VolumeRetention in the Pool resource
record, you must ensure that the corresponding change is made in the
catalog by using the update pool command. Doing so will insure that any
new Volumes will be created with the changed Volume Retention period.
Any existing Volumes will have their own copy of the Volume Retention
period that can only be changed on a Volume by Volume basis using the
update volume command."

Hope, this helps you resolving your problem.

Szaszka

On Wed, 25 May 2005 12:55:50 -0400
"Matthew Butt" <[EMAIL PROTECTED]> wrote:

> I'm having a tough time trying to get Bacula to recycle volumes
> properly.  I'm trying to backup a Windows server with a full backup on
> Sunday and incrementals Monday to Saturday.  Backup is to a removable
> USB disk and I want the filenames to be automatically created in the
> format ProductionVol001, ProductionVol002 etc through to
> ProductionVol007, after which it will go back to 001 again.
> 
> My relevant config entries are:
> 
> Pool {
>   Name = Production
>   Use Volume Once = yes
>   Pool Type = Backup
>   LabelFormat = "ProductionVol"
>   AutoPrune = yes
>   Volume Retention = 7 days
>   Maximum Volumes = 7
>   Recycle = yes
> }
> 
> Client {
>   Name = production-fd
>   Address = production
>   FDPort = 9102
>   Catalog = MyCatalog
>   Password = "password"          # password for FileDaemon
>   File Retention = 30 days            # 30 days
>   Job Retention = 6 months            # six months
>   AutoPrune = yes                     # Prune expired Jobs/Files
> }
> 
> Job {
>   Name = "ProductionFiles"
>   JobDefs = "DefaultJob"
>   Client = production-fd
>   Write Bootstrap = "/var/bacula/ProductionFiles.bsr"
>   FileSet = "ProductionFiles"
>   Pool = Production
> }
> 
> The problem is that every time the schedule runs I'm getting the
> all-too-familiar error (below).  All other backup jobs then stop
> completely.
> 
> 25-May 08:43 backup-sd: Job ProductionFiles.2005-05-25_08.43.07
> waiting. Cannot find any appendable volumes.
> Please use the "label"  command to create a new Volume for:
>     Storage:      FileStorage
>     Media type:   File
>     Pool:         Production
> 
> 
> If I use label (which in my reckoning I should never need to do as
> Bacula should automatically create the label for me) then it works for
> that time, but next time it'll halt again with the same error.
> 
> Can anyone throw me any pointers?
> 
> Thanks,
> 
> MattB


-------------------------------------------------------
SF.Net email is sponsored by: GoToMeeting - the easiest way to collaborate
online with coworkers and clients while avoiding the high cost of travel and
communications. There is no equipment to buy and you can meet as often as
you want. Try it free.http://ads.osdn.com/?ad_id=7402&alloc_id=16135&op=click
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to