On 11/01/18 13:53, krashoverr...@free.fr wrote:
Yeah, i've just read Gary and Ralf tips, thanks to all of you.
I'm sad to hear SQLite is depreciated, as it's still available in packages list.
It was only ever intended that SQlite be used for testing purposes, not
production systems
We started to use postgres, also tried SQLite, and choosed SQLite, as it seemed
to be lighter than postgres.
"lighter" does not automatically mean "scalable".
Something that works for testing may turn out to be a major load in a
production system and this is _definitely_ the case for SQlite when you
may have 100 million entries in a production backup system.
BTW, regarding your personal experience and feedback, what would be the
best/faster option with a disaster plan; let's say you lose everything, bacula
server, file server (and i mean file server, no databases / etc).
Dump the database daily, copy it to an external resource. That way you
have a starting point that you can work with. Unless you copy your BSRs
outside the backup server you can regard those as "lost" in a scenario
you describe and it's not much extra effort to copy the database dump
when backing these up.
In a critical system you may even want to consider using postgres
replication to ensure the database is kept in multiple locations and
thus avoid hardware failure causing total DB loss.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
