Hi,
I'm seeing some behaviour I can't readily explain, I'm guessing its my
configuration.
We have a pool of four tapes for Mon-Thu, reused every week. We have a
second pool of eight tapes for every Friday, recycled as soon as we've
finished using the last one. And we have an end of month tape thats
never reused.
Here are our schedule and pool definitions in bacula-dir.conf:
Schedule {
Name = "DefaultCycle"
Run = Level=Full Pool=Weekly mon-thu at 22:04
Run = Level=Full Pool=WeeklyFridays fri at 22:04
Run = Level=Full Pool=Monthly 1st mon at 22:04
Run = Level=Full Pool=Yearly december 31 at 22:04
}
# Mon-Thu, pool of 4 tapes
Pool {
Name = Weekly
Pool Type = Backup
Recycle = yes
Maximum Volumes = 4
AutoPrune = yes
Volume Retention = 6 days
Accept Any Volume = yes
LabelFormat = "Weekly-${WeekDay}"
}
# Fri every week, pool of 8 tapes
Pool {
Name = WeeklyFridays
Pool Type = Backup
Recycle = yes
Maximum Volumes = 8
AutoPrune = yes
Volume Retention = 1 month
Accept Any Volume = yes
LabelFormat = "WeeklyFridays-"
}
# Last day of the month, permanent
Pool {
Name = Monthly
Pool Type = Backup
Recycle = no
AutoPrune = yes
Accept Any Volume = yes
Use Volume Once = yes
LabelFormat = "Monthly-${Year}-${Month}-${Day}.${WeekDay}"
}
# Last day of the year, permanent
Pool {
Name = Yearly
Pool Type = Backup
Recycle = no
AutoPrune = yes
Accept Any Volume = yes
Use Volume Once = yes
LabelFormat = "Yearly-${Year}-${Month}-${Day}.${WeekDay}"
}
And here is the device definition from bacula-sd.conf:
Device {
Name = DDS-4
Media Type = DDS-4
Archive Device = /dev/nst0
AutomaticMount = yes;
AlwaysOpen = no;
RemovableMedia = yes;
RandomAccess = no;
LabelMedia = yes;
}
The problem I'm having, is that Bacula (for reasons I can't fathom)
occasionally decides, say, on Thursday that it must have the tape for
Wednesday (volume Weekly-3) instead, and refuses to use anything else,
despite a manual "mount" command and the fact that "Accept Any Volume"
is set to yes.
We always use do Full backups (gigabit network, so its not
particularly slow), I'm hesitant to switch to another scheme until I
can get Bacula to consistently run without requiring intervention
other than just inserting a tape, having to manually run a "mount"
command isn't really going to do it (the person inserting the tape and
the person looking after Bacula are two different folks with differing
levels of UNIX-fu).
We don't care if the contents of an existing tape is overwritten, no
matter which tape is in the drive, we just want Bacula to go ahead and
write over it.
The general opinion from this list seems to be that we should be happy
with "tar" in that case, but thats not quite true :) We had tar
before, and bacula's indexes and fast restores as well as the
agent-based file retrieval system are far superior, and I'd trust
Bacula's retrieval over a manual hacked together tar script any day.
Any ideas how I could make it always be happy with the Weekly volume
thats in the drive, no matter what?
Thanks,
Leon
-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users