Built on SQLite itself
SQLite is among the most thoroughly tested software in the world: its project keeps about 590 times as much test code as library code, with 100% branch coverage of its core (How SQLite Is Tested). Litebackup is built so your app keeps all of that.
-
Your app keeps its SQLite. It goes on using the official SQLite it already links, with any driver. Litebackup does not replace the engine, load an extension into your app, or change your file format.
-
Litebackup uses SQLite as released. It runs the unmodified SQLite library from sqlite.org and reads your changes only through features SQLite ships and documents.
-
What comes back is plain SQLite. Every replica and restore is an ordinary SQLite file that opens with any driver, and a restore passes SQLite's own
quick_checkbefore it finishes.
What a nightly backup looks like
-
A cron job runs
sqlite3 app.sqlite ".backup /backups/app.sqlite"orVACUUM INTO, or the host takes a disk snapshot, and a script uploads the copy somewhere safe. -
Anything written after the last copy is lost with the machine, and you can only restore the moments you happened to copy.
What changes with Litebackup
-
Each change reaches your own server within seconds and your bucket after that, encrypted with your key.
-
Restores pick any kept version or time, write a new file, and check it before they finish.
-
Nothing to script: install the service, point it at your databases, and choose how long to keep backups.