Still trying to get Progressive Virtual
Full backups to work.
I solved the "no previous jobs found"
problem by making only one job definition (instead of
separate incremental and virtualfull definitions), and
changing the job level to VirtualFull in the schedule
for the times when I want to consolidate. It now
correctly locates the jobs to consolidate. However,
I'm getting deadlock when it tries to access storage,
probably because I have Pool and Next Pool set to the
same location.
"Alternatively, you can set your Next Pool to
point to the current pool. This will cause Bacula to
read and write to Volumes in the current pool. In
general, this will work, because Bacula will not
allow reading and writing on the same Volume."
This is what I'm trying to do, but it doesn't
work; the job stalls with "waiting on Storage." I
assume this is because my file pool only has one
device, so Bacula assumes it can't both read from
and write to it at the same time. I've found lots of
old (v5.x era) references to using vchanger to solve
this kind of problem, but I'm unsure if that's still
the best way to go. The current documentation is a
bit fragmentary on this and I'm hoping someone can
point me in the right direction.
Here's the relevant configuration stanzas for my
storage:
bacula-dir.conf:
Storage {
Name = russell.math.ucsb.edu-sd
SDPort = 9103
Password = <redacted>
Device = DataCenter
Media Type = DCFile
Maximum Concurrent Jobs = 10
}
Pool {
Name = DataCenterPool
Pool Type = Backup
Recycle = yes
AutoPrune = yes
Volume Retention = 60 days
Maximum Volume Bytes = 50G
Maximum Volumes = 280
Label Format = "DCVol-"
Storage = russell.math.ucsb.edu-sd
}
bacula-sd.conf:
Device {
Name = DataCenter
Device Type = File
Media Type = DCFile
Archive Device = /media/bacula/DataCenterPool
LabelMedia = yes;
Random Access = Yes;
AutomaticMount = yes;
RemovableMedia = no;
AlwaysOpen = no;
Maximum Concurrent Jobs = 10
}
