Hi Jim,
I will try to help here.
It seems to me your C2T-Data backup job is reading from disk and writing to
tape.
The disk autochanger used by this job gor reading is "FileChgr" and it has
three devices each having a different media type (DailyDisk, WeeklyDisk and
MontlhyDisk).
In this case,
Hello Luke,
I noticed you are using "/dev/tape/by-path/" for the tape drives archive
device configuraton. It is safer to use "/dev/tape/by-id" to avoid tape
drives be twisted after server reboots, for example.
It is even more safe to use udev rules based on your tape drives attributes
(such as
Hello Jose Alberto,
Could you please send to us the configuration used for both tape drives you
have in the bacula-sd configuration files?
It seems to me you have different devices configured with different mefia
types in this case. Bacula "ties" volumes to devices through media types.
It would
On 07/16/17 15:11, Kern Sibbald wrote:
> Hello Phil,
>
> According to the documentation in both MySQL and MariaDB, I can use
> "-00-00 00:00:00".
Yes - prior to MySQL 5.7, or if you change MySQL 5.7's default SQL_MODE.
The default SQL_MODE in 5.7 includes NO_ZERO_DATE,NO_ZERO_IN_DATE.
Hello Phil,
According to the documentation in both MySQL and MariaDB, I can use
"-00-00 00:00:00". I might have missed something though. It seems
to work fine with MariaDB 10.0. I will test it with MariaDB 10.2 and
with the current Ubuntu 16.04 version of MySQL, and if it works, I will
On 07/16/17 04:52, Kern Sibbald wrote:
> Hello,
>
> It sounds like this is another change in MySQL in a newer version.
> Previously they prohibited a DEFAULT 0 for the start time, because zero
> is not a permitted value, even though the field is a Unix Time stamp,
> where 0 is a perfectly valid
Hello once more,
I have now removed MySQL from my system and installed MariaDB.
Info:
MariaDB [regress]> show variables like "%version%";
+-+--+
| Variable_name | Value
Hello,
After a more careful look, I see that my first two paragraphs are
not correct. After looking at your output more carefully, I see
that you are running MariaDB, and at the moment Bacula does not
officially support MariaDB. My suggestions for correcting the
Hello,
It sounds like this is another change in MySQL in a newer
version. Previously they prohibited a DEFAULT 0 for the start
time, because zero is not a permitted value, even though the field
is a Unix Time stamp, where 0 is a perfectly valid time.
Hi,
I've managed to compile and install 9.0.0 (with much appreciated help)
however now the jobs fail.
I have run the update_bacula_tables script
--
Error Message:
JobId 0: Fatal error: sql_create.c:84 Create DB Job record
INSERT INTO Job
10 matches
Mail list logo
