Hello,
śr., 10 kwi 2019 o 02:37 David Brodbeck <brodb...@math.ucsb.edu> napisał(a):
> I've been wondering the same thing, especially since there seems to be no
> official way to migrate an SQLite database to PostgreSQL or MariaDB. I'm
> actually not opposed to doing using one of those (I feel like a "real"
> RDBMS might offer better performance and stability in my case -- my
> installation has grown to about 60 clients) but everyone who's done it
> seems to have rolled their own script to do the conversion. Descriptions of
> the process in the mailing list archives are pretty vague, and I'm not
> confident I understand the Bacula schema well enough to pull it off safely.
>
> I'm hoping if they decide to pull the plug on SQLite completely they'll
> provide some kind of migration path for those of us who made the
> (apparently bad) decision to choose it early on, when it was supported.
>
>
> On Fri, Mar 29, 2019 at 11:51 AM Oliver Lehmann <lehm...@ans-netz.de>
> wrote:
>
>> Hi,
>>
>> I just migrated my Bacula installation from 7 to 9.
>> During executing the DB schema update Tool, I noticed, that SQLite got
>> deprecated.
>>
>> I wonder why? :(
>>
>
The exact reason should be explained by Kern itself. Below is my thoughts
about it:
SQLite is a very limited "database" engine. Bacula internals requires
("support" depends from the point of view) a dedicated SQL queries prepared
for every catalog backend. Maintaining this backend requires more and more
work and brings no real value to Bacula. It is possible that developers
faced a technical limitation with SQLite during new feature development.
Today a single "standard" workstation could generate more then 6M files in
catalog database, so even with an extremely small home network you can
reach millions of entries catalog level. This level is not a target for
SQLite, sorry.
I doubt it return any time.
>
>> I didn't wanted to install, maintain a full RDBMS which eats up
>> ressources and might contain security issues just to get my backups
>> going.
>
>
:)
What "resources" are you referring to? My current phone has 64bit OS and
4GB of RAM (top models has 8G). Having a real bare metal server with
hundreds GB of ram is not a big deal. Storage space is extremely cheap too.
Unless you run your Bacula on wrist watch or 30Y hardware you do not need
to worry about any RDBMS for Bacula catalog.
> I seriously do not care about backup performance. It is a home
>> installation and a full backup only contains around 1 TB of data from
>> 4 systems (some of them virtual).
>>
>> Does this now mean I have to get MySQL (what is with MariaDB?) or
>> PGSQL installed just for keeping Bacula working in 10 or whatever
>> version SQLite support will be completly removed?
>>
>> How sad.... :(
>>
>
How Great! We removed this legacy in the end! Let's celebrate! :)
You see it as a loss, OK. I see it as a great step forward.
best regards
--
Radosław Korzeniewski
rados...@korzeniewski.net
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
