Re: Bacula Release 11.0.0 (beta)
Sven Hartge <[email protected]>
| Newsgroups | gmane.comp.sysutils.backup.bacula.devel |
|---|---|
| Message-ID | <[email protected]> |
On 15.12.20 12:46, Gary R. Schmidt wrote: > On 15/12/2020 20:41, Sven Hartge wrote: >> On 15.12.20 10:33, Sven Hartge wrote: >>> On 15.12.20 10:00, Eric Bollengier via Bacula-devel wrote: >> >>>> This release of Bacula uses a new catalog format. We provide a set of >>>> scripts that permit to convert a 9.x and earlier versions to the new >>>> 11.0.0 format (1023). Normally, it is automatic, though this is a big >>>> change that takes longer than usual. The upgrade process will require >>>> more or less twice the size of the actual database on disk. >> >>> One thing I can directly see is that the SQlite catalog upgrade is >>> broken for DB versions 15 and 16. >> >> With "broken" I mean: non-existent. >> > SQLite for Bacula was deprecated years and years ago, anyone who is > still using it has had more than enough time to update. > > I presume that the chance to remove it completely as part of the 11 > re-write was so obvious that not doing it would have been foolish. This is all known and well, but the sqlite3-update script *has* been updated to the current DB version 1023, so it was clearly adapted. But it is missing the upgrade path from Bacula 7.0.0 and 9.0.0, as if something went wrong during the merge from or to BEE. Grüße, Sven. _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel