Re: [Bacula-users] Upgrade Bacula from 7.4.2 to 9.2.0. Fatal error: sql_create.c: ... failed. ERR=Field 'StartTime' doesn't have a default value

2018-08-06 Thread Gary R. Schmidt
On 07/08/2018 10:05, George Anchev via Bacula-users wrote: Today I installed 9.2.0 FD on one of the network workstations. Trying to run an estimate for an incremental job tells me that "Job 0" cannot find previous Full backup, so it will estimates a full one. My workaround with changing the

Re: [Bacula-users] Upgrade Bacula from 7.4.2 to 9.2.0. Fatal error: sql_create.c: ... failed. ERR=Field 'StartTime' doesn't have a default value

2018-08-06 Thread George Anchev via Bacula-users
Thanks for the quick response Phil. On Mon, 6 Aug 2018 20:13:17 -0400 Phil Stracchino wrote: > You probably need to go through each table and > change any field (except BLOB or TEXT) that is > declared NOT NULL without a DEFAULT to 'DEFAULT > NULL'. Is there a command which does that or should

Re: [Bacula-users] Upgrade Bacula from 7.4.2 to 9.2.0. Fatal error: sql_create.c: ... failed. ERR=Field 'StartTime' doesn't have a default value

2018-08-06 Thread Phil Stracchino
On 08/06/18 20:05, George Anchev via Bacula-users wrote: > Today I installed 9.2.0 FD on one of the network > workstations. Trying to run an estimate for an > incremental job tells me that "Job 0" cannot find > previous Full backup, so it will estimates a full one. > > My workaround with changing

Re: [Bacula-users] Upgrade Bacula from 7.4.2 to 9.2.0. Fatal error: sql_create.c: ... failed. ERR=Field 'StartTime' doesn't have a default value

2018-08-06 Thread George Anchev via Bacula-users
Today I installed 9.2.0 FD on one of the network workstations. Trying to run an estimate for an incremental job tells me that "Job 0" cannot find previous Full backup, so it will estimates a full one. My workaround with changing the SQL_MODE didn't work in this case. On Mon, 6 Aug 2018 16:37:02

Re: [Bacula-users] Upgrade Bacula from 7.4.2 to 9.2.0. Fatal error: sql_create.c: ... failed. ERR=Field 'StartTime' doesn't have a default value

2018-08-06 Thread Phil Stracchino
On 08/06/18 15:32, Tilman Schmidt wrote: > Am 02.08.2018 um 23:47 schrieb Phil Stracchino: >>> >>> Minimal fix: >> >> ALTER TABLE Media MODIFY FirstWritten datetime DEFAULT NULL; > > Thanks. I extended that to: > > ALTER TABLE Media MODIFY FirstWritten datetime DEFAULT NULL; > ALTER TABLE

Re: [Bacula-users] Upgrade Bacula from 7.4.2 to 9.2.0. Fatal error: sql_create.c: ... failed. ERR=Field 'StartTime' doesn't have a default value

2018-08-06 Thread Tilman Schmidt
Am 02.08.2018 um 23:47 schrieb Phil Stracchino: >> >> Minimal fix: > > ALTER TABLE Media MODIFY FirstWritten datetime DEFAULT NULL; Thanks. I extended that to: ALTER TABLE Media MODIFY FirstWritten datetime DEFAULT NULL; ALTER TABLE Media MODIFY LastWritten datetime DEFAULT NULL; ALTER TABLE

Re: [Bacula-users] tapes running out of space

2018-08-06 Thread Adam Weremczuk
On 06/08/18 14:08, Jérôme Blion wrote: LTO-4 are supposed to store 800GB uncompressed. That's the only value you can expect from the tape. Depending on the data pieces you want to backup, you can have a ratio lower than 2. If data pieces are already compressed you won't have a good

Re: [Bacula-users] tapes running out of space

2018-08-06 Thread Jérôme Blion
Hi, LTO-4 are supposed to store 800GB uncompressed. That's the only value you can expect from the tape. Depending on the data pieces you want to backup, you can have a ratio lower than 2. If data pieces are already compressed you won't have a good compression ratio. Is the capacity dynamic,

[Bacula-users] tapes running out of space

2018-08-06 Thread Adam Weremczuk
Hi all, For the second time this year I have experienced backups failing due to tapes filling up: 06-Feb 22:16 bacula_sd JobId 42315: Writing spooled data to Volume. Despooling 5,368,719,418 bytes ... 06-Feb 22:17 bacula_sd JobId 42315: End of Volume "LTO-W20141230A" at 1417:11071 on device

Re: [Bacula-users] Warnings during make

2018-08-06 Thread Kern Sibbald
Yes, my mistake, sorry.  It was indeed due to a new compiler version, but was a real "error". On 08/05/2018 11:15 AM, George Anchev wrote: On Sun, 5 Aug 2018 10:42:14 +0200 Kern Sibbald wrote: This is fixed and pushed to the repo. Thanks! I noticed yesterday. So the bug report was valid