Hi There!
This is my first mail to this list, so please be patient, if I'm missing
a point.
We're using Bacula for several months now. As "Backup Drive" we
configured three pools. One pool for Monthly Backups within the months
1,3,5,...11, one pool for Monthly Backups within the months 2,4,6,...12
and one pool for daily backups.
The Monthly Storages are two HDDs with a capacity of 1 TB for each month
and the Daily Pool is a NAS System with a Capacity of 3 TB.
For the monthly Backups there is a maximum of 230 Volumes configured,
each 4 GB in size. This is a total capacity of 920 GB.
This week, the backup stopped, because the currently running job "is
waiting for an appendable Volume".
Our Volumes in that Pool/Storage are named
Monatssicherung_gerade_VolumeNr.000 through
Monatssicherung_gerade_VolumeNr.229 . The Volumes
Monatssicherung_gerade_VolumeNr.001 through
Monatssicherung_gerade_VolumeNr.029 didn't exist. Neither within the
Filesystem, nor in the "list media pool=Monatssicherung_gerade_Pool"
listing.
In the past, bacula created these new Volumes itself, since this is the
(so far as I understood the Config's Syntax while I set it up)
configured behavior. But this time it just didn't. It hung and waited
for ME to label a new Volume for it manually.
I did so for 2 Volumes, hoping this "kickstarts" bacula's Auto-Labeling
function, but it didn't.
Here is my Config for the concerned Pool and Device setup:
Pool {
Name = "Monatssicherung_gerade_Pool"
Pool Type = "Backup"
Maximum Volume Bytes = 4294967296 # 4 GB
Maximum Volumes = 230 # 4 GB * 230 Volumes = ca. max
920 GB
Label Format =
"Monatssicherung_gerade_VolumeNr.${NumVols:p/3/0/r}"
AutoPrune = "yes"
Volume Retention = 55 days
Recycle = "yes"
}
Device {
Name = "monatsbackup_gerade_device"
Device Type = "File"
Media Type = "Wechselfestplatte"
Autochanger = "no"
Archive Device = "/server/data/backup/bacula_wechselrahmen"
LabelMedia = "yes"
Random Access = "Yes"
AutomaticMount = "yes"
RemovableMedia = "no"
AlwaysOpen = "yes"
}
As far as I know, the "LabelMedia" Option within the Device's Definition
should create Volumes if they are needed up to a limit of 230 Volumes
with a size of 4 GB each.
Further, bacula should try to preserve Data as long as it's possible.
So, labeling a new volume should be preferred to recycling pruned Volumes.
I lowered the Volume Retention Time from 60 to 55 days. This I did,
because there once were a Retention time of 60 Days configured, later
lowered to 55 Days, but the existing Volumes never have been updated
with these settings. So I did, using the update command to "clean" the
Config.
This pruned some Volumes, wich were older than 55 days, but not older
than 60 days. So bacula used these pruned Volumes to recycle them and
finish the Backup. The Volumes *.003 through *.029 are still missing.
I know that I can label them manually, but I want to Know why bacula
stopped doing it automatically.
Further, I want to know, why bacula recycles Volumes (which destroys
data) instead of creating new ones and if this is a Bug which should be
reported.
Thank you for your help!
greetings,
Marc
--
Marketing Factory Consulting GmbH * mailto:mr AT marketing-factory DOT de
Stephanienstrasse 36 * Tel.: +49 211-361176-44
D-40211 Duesseldorf, Germany * Fax : +49 211-361176-45
Amtsgericht Duesseldorf HRB 53971 * http://www.marketing-factory.de/
Geschaeftsfuehrer: Peter Faisst | Katja Faisst
Karoline Steinfatt | Christoph Allefeld | Markus M. Kimmel
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|
