Hi Marcin,
Thanks for the info! I didn’t realize I was using an old version of baculum. I
removed version 7 and installed version 9. I was then able to connect to the DB
on the Catalog API tab.
Now I’m running into a problem on the Console API tab. I have the Bconsole
binary file path set to
Well, I must be blind. A few minutes after posting my message, I found this
section in bacula-dir.conf:
# Generic catalog service
Catalog {
Name = MyCatalog
dbname = "bacula"; dbuser = "bacula"; dbpassword = ""
}
I added my password and now things are working again. Sorry for the false
System details:
CentOS 7.3
Bacula 9.06
Baculum 9.05
MySQL (MariaDB) 5.5.56
I just finished configuring Baculum and have access to the web interface now.
However, when I try to click on any of the options on the Workspace (Storage
Daemons, Clients, Volumes, Pools, etc..), nothing happens. I
Am 06.02.2018 um 19:46 schrieb Mike Eggleston:
> Thanks for the suggestion. I’m now using:
>
> ./configure --enable-client-only --enable-static-client-only
> --enable-static-fd --disable-libtool --without-ssl
>
> with no success… L
Still the same error? Still saying
> checking for MySQL
Thank you Martin.
We are using a pretty old Bacula 5.2.6.
This version already appears to support compressions on clients.
But it's currently not defined for any.
I'm assuming hardware compression is enabled on the LTO-4 tape drive.
I've checked:
- Device and Storage directives,
- "status
Hello Shawn,
You can try to enable debug in Baculum by clicking on the bottom
checkbox with label 'Enable debug'. Then you can click few times on
these parts that don't show any data. In the end you can look in the
/usr/share/baculum/htdocs/protected/Web/Logs/
If it doesn't show any error then
Hello,
I'm using Bacula 5.2.6 with about 15 clients and recently experienced a
tape filling up quite unexpectedly.
So I'm looking for a way to make some kind of space usage listing.
Something like a list of top-level directory sizes for each client on
any given tape and date.
The idea is to
