Hello,
The variable expansion code is *very* complicated and has a few esoteric
bugs, so the code has been deprecated (destined to be removed) for a
long time. Any patches to fix problems would be welcome, but we are not
planning to spend any time trying to make it work -- sorry. The best
solution is to chose a simpler naming convention or just let Bacula
handle it for you.
Best regards,
Kern
On 15-09-30 12:14 PM, Georg Altmann wrote:
Hi,
there seems to be a problem with variable expansion in Pool/LabelFormat
after failed jobs. I randomly get expansions that do not have the
expected value.
Pool {
Name = Disk3Pool
Pool Type = Backup
Recycle = no
AutoPrune = Yes
Volume Retention = 500 years
Maximum Volume Jobs = 1
Label Format =
"disk3-${Disk3VolNum+:p/6/0/r}-${Year}-${Month:p/2/0/r}-${Day:p/2/0/r}-${Job}-${Level}"
}
>From the log, with expected volume name:
Build OS: x86_64-unknown-linux-gnu archlinux
Job: gurke-arch-linux.2015-09-30_17.17.01_08
Backup Level: Incremental, since=2015-09-15 08:55:26
Client: "gurke-arch-linux-fd" 7.0.5 (28Jul14)
x86_64-unknown-linux-gnu,archlinux,
Pool: "Disk3Pool" (From Job resource)
Volume name(s):
disk3-000616-2015-09-30-gurke-arch-linux-Incremental
But then the label is often incorrect / unexpected:
Job: BackupCatalog.2015-09-30_17.17.01_16
Backup Level: Full
Client: "gurke-arch-linux-fd" 7.0.5 (28Jul14)
x86_64-unknown-linux-gnu,archlinux,
FileSet: "Catalog" 2011-11-13 17:21:08
Pool: "Disk3Pool" (From Job resource)
Volume name(s):
disk3-000618-2015-09-30-georgtp-arch-Incremental
Another incarnation of the same job with correct volume label:
Job: BackupCatalog.2015-09-15_08.55.24_39
Backup Level: Full
Client: "gurke-arch-linux-fd" 7.0.5 (28Jul14)
x86_64-unknown-linux-gnu,archlinux,
FileSet: "Catalog" 2011-11-13 17:21:08
Pool: "Disk3Pool" (From Job resource)
Volume name(s):
disk3-000615-2015-09-15-BackupCatalog-Full
This problem seems to occur when a previous run job fails. In fact the
unexpected label
disk3-000618-2015-09-30-georgtp-arch-Incremental
for the job
BackupCatalog.2015-09-30_17.17.01_16
would have been the correct label for the first of two failed jobs that
were scheduled before BackupCatalog:
Job: georgtp-arch.2015-09-30_17.17.01_12
Backup Level: Incremental, since=2015-09-15 09:12:20
Client: "georgtp" 7.0.5 (28Jul14)
x86_64-unknown-linux-gnu,archlinux,
Volume name(s):
Volume Session Id: 3
Volume Session Time: 1443626168
Last Volume Bytes: 0 (0 B)
Non-fatal FD errors: 1
SD Errors: 0
FD termination status: Error
SD termination status: Waiting on FD
Termination: *** Backup Error ***
Notice the empty Volume name field.
So it seems as if the volume label for a failed job remains in some kind
of queue of buffer that is then incorrectly used for a following job.
Can anybody confirm this?
I did not find a bug report in mantis. May this have been fixed with 7.2?
I am running bacula 7.0.5 on Arch Linux:
% pacman -Q |grep bacula
bacula-bat 7.0.5-1
bacula-common 7.0.5-1
bacula-console 7.0.5-1
bacula-dir 7.0.5-1
bacula-dir-postgresql 7.0.5-1
bacula-fd 7.0.5-1
bacula-sd 7.0.5-1
Regards,
Georg
------------------------------------------------------------------------------
_______________________________________________
Bacula-devel mailing list
Bacula-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-devel
------------------------------------------------------------------------------
_______________________________________________
Bacula-devel mailing list
Bacula-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-devel
