I just updated from Bacula 9.2.1 to 9.4.1, and suddenly I have a problem.
Actually I had a series of problems, which started out with the Solaris
11.3 disk FD failing because, by the looks of it, I accidentally built
it 32-bit and last night's backups overflowed EndBlock. So I rebuilt
64-bit, and found that the installed MySQL libraries installed on
Solaris were only 32-bit, which apparently is why I'd managed only a
32-bit build. Don't ask me why the 32-bit 9.2.1 SD was working but a
32-bit 9.4.1 SD overflows, because I have no idea.
So I removed the near-useless Oracle-Solaris-11.3-provided 32-bit-only
MySQL package, and replaced it with an
Oracle-MySQL-for-Solaris-11.3-provided MySQL package which actually is
64-bit, and was able to rebuild a proper 64-bit Bacula-9.4.1 fd and sd.
asgard:root:/netstore/src/bacula-9.4.1:39 # file /opt/bacula/sbin/bacula-*
/opt/bacula/sbin/bacula-dir: ELF 64-bit LSB executable AMD64 Version
1 [SSE2 SSE], dynamically linked, not stripped
/opt/bacula/sbin/bacula-fd: ELF 64-bit LSB executable AMD64 Version
1 [SSE2 SSE], dynamically linked, not stripped
/opt/bacula/sbin/bacula-sd: ELF 64-bit LSB executable AMD64 Version
1 [SSE2 SSE], dynamically linked, not stripped
========================
I note here that I configured with --disable-build-dird, and configure
shows it disabled:
bat support: no
client-only: no
build-dird: no
build-stored: yes
But the build ignored that and build the Director *anyway*.
These options have always been a bit balky. I think it would probably
be easier to get it to build what you want if
--[enable|disable]-client-only went away and there was a consistent set
of --enable-build-client, --enable-build-dird, --enable-build-stored,
defaulting to 'yes', 'no', 'no'.
========================
Restarted the new SD and FD, restarted the Director out of constructive
paranoia, ran a new test set of differential backups, and now I have a
NEW problem:
Device File: "FileStorage" (/spool/bacula) is not open.
Device is BLOCKED waiting to create a volume for:
Pool: Diff-Disk
Media type: File
Available Space=7.051 TB
I'm baffled as to why creating a new volume would suddenly be blocked.
It's always worked before and I have made no configuration changes.
Any suggestions? I have absolutely no idea why it is blocking.
--
Phil Stracchino
Babylon Communications
ph...@caerllewys.net
p...@co.ordinate.org
Landline: +1.603.293.8485
Mobile: +1.603.998.6958
_______________________________________________
Bacula-devel mailing list
Bacula-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-devel
