# Small database. Serious recovery routine.

> Back up SQLite using database-aware tools. Understand integrity checks, included application files and how to rehearse recovery into a separate database path.

Canonical page: https://www.calmbackup.com/guides/sqlite-backups

Back up SQLite with its database-aware tooling, include the files around it, and test recovery into a separate path.

[Start free trial](https://app.calmbackup.com/register)

## Treat the file as a live database.

SQLite is stored in a file, but that does not make an arbitrary copy of a busy database a dependable backup. Use database-aware tooling that understands the database while it is being written.

The CalmBackup CLI uses the sqlite3 .backup command when available. Install sqlite3 on the machine and make it available to the scheduled job. The driver has a file-copy fallback, but that should not be your planned method for backing up an active application.

[Read SQLite’s backup documentation](https://www.sqlite.org/backup.html)

## Check the copy. Keep the surrounding files.

The driver runs PRAGMA integrity\_check against the backup. A successful integrity check concerns the database structure; it does not validate your business rules, upload references or application behavior.

Configure any application-owned directories that must come back with the database. Think about uploads, generated documents and other files that cannot be recreated from your deployment. Keep enough local disk space for the temporary data, compressed archive and encrypted copy.

**Keep related data consistent**

A database backup and a directory archive do not form an atomic snapshot of a changing application. Coordinate writes when the database and files must reflect the same application state.

[Understand database and file coverage](https://www.calmbackup.com/database-backups)

## Restore to a path you have checked.

The SQLite restore replaces the database file at the configured destination. For a rehearsal, use a separate path and isolated application instance. Confirm the path, file ownership and permissions before attempting to start the recovered application.

Open the application, inspect important records, and check that related uploaded files are present. Record which backup was used and how long the full procedure took. A small database still benefits from a written recovery routine that someone else can follow.

[Follow the restore checklist](https://www.calmbackup.com/guides/restore-checklist)
