Awesome, thank you very much!
+--
|This was sent by bill.dam...@yahoo.com via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--
---
CREATE TABLE RestoreObject (
RestoreObjectId INTEGER UNSIGNED NOT NULL AUTO_INCREMENT,
ObjectName BLOB NOT NULL,
RestoreObject LONGBLOB NOT NULL,
PluginName TINYBLOB NOT NULL,
ObjectLength INTEGER DEFAULT 0,
ObjectFullLength INTEGER DEFAULT 0,
ObjectIndex INTEGER DEFAULT 0,
I have managed to get everything up and running with the help from the Maraidb
group and backups are now running ok! Thanks to everyone for the help. There is
one last table I need to create manually - the RestoreObject one. Can someone
please list the CREATE TABLE statement I need to make it, a
Hello,
No, your database has not been properly updated.
We do not test Bacula with MariaDB, so all bets are off, but clearly
something went wrong with the database upgrade.
Best regards,
Kern
On 11/23/2015 03:32 AM, bdam wrote:
> Sorry for the verbosity this time, you'll see it is necessary tho
Sorry for the verbosity this time, you'll see it is necessary though. I am
wondering why the code looks for a column which doesn't exist, even though the
db upgrade script says it has been updated. See this - does it look like a v15
table structure?
[root@tiger ~]# mysql
Welcome to the MariaDB
(I cannot post literal SQL here as backupcentral.com is seeing it as SQL
injection, so I have editted appropriatley but know you'll see how it was
originally)
19-Nov 01:15 tiger-dir JobId 0: Fatal error: sql_create.c:90 Create DB Job
record I$NSERT I$NTO Job
(Job,Name,Type,Level,JobStatus,Sche
Thanks again Kern.
[root@tiger ~]# find / -name "bacula-dir"
/mnt/Vol-06/Mirror/etc/sysconfig/bacula-dir
/root/.config/bacula-dir
/usr/sbin/bacula-dir
/etc/sysconfig/bacula-dir
find: /run/user/42/gvfs: Permission denied
[root@tiger ~]# which bacula-dir
/sbin/bacula-dir
Some more clues?
[root@
Hello,
On 11/22/2015 01:55 PM, bdam wrote:
> Thanks for your help so far. This must be a big clue. Do you think just dnf
> uninstall bacula; dnf install bacula would fix it? I am very reluctant to try
> just as a gamble.
Normally, when I do it manually, I can just re-do the "make install" and
i
Thanks for your help so far. This must be a big clue. Do you think just dnf
uninstall bacula; dnf install bacula would fix it? I am very reluctant to try
just as a gamble.
[root@tiger bacula]# ./update_mysql_tables -u root -p
This script will update a Bacula MySQL database from version 12-14 to
Hello,
>From what I see, your database has been updated to the Bacula 7.2.0
version, but your Director or one of the shared objects is not on the
same Bacula release version.
Note, it is also probable that just the opposite happened. That is you
updated your Bacula binaries, but your database did
Version: 7.2.0 (14 August 2015) x86_64-redhat-linux-gnu redhat Three)
+--
|This was sent by bill.dam...@yahoo.com via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+-
Help!
All the backup jobs fail - is the db screwed? I just did the automatic update
and now get:
22-Nov 12:01 tiger-dir JobId 6262: Fatal error: bdb.h:103 bdb.h:103 query
SELECT
MediaId,VolumeName,VolJobs,VolFiles,VolBlocks,VolBytes,VolABytes,VolHoleBytes,VolHoles,VolMounts,VolErrors,VolWrites,
12 matches
Mail list logo
