To be honest, my mistake was I didn't realize that by "testing purposes" they meant "a temporary, throwaway system where you delete everything before moving on to production." By the time I decided Bacula was doing the job for me and it was time to move to a more robust backend, I had too much backup data to just start over from scratch. I didn't want to have to tell someone "I had a backup of that, but I deleted it." Basically I failed to look two steps ahead to see if there would be a migration path forward.
I haven't yet had an SQLite problem I couldn't fix with the command line tools, in spite of once running out of disk space on the partition the DB was on. My biggest complaint about it is if you have backups with millions of files, operations on them can tie up the director for quite a while. That's the main reason I'd like to switch to a proper DB server. On Mon, Apr 29, 2019 at 8:54 AM Phil Stracchino <ph...@caerllewys.net> wrote: > > > "For testing purposes." > > Was SQLite *ever* actually *recommended* for production? > -- David Brodbeck System Administrator, Department of Mathematics University of California, Santa Barbara
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
