> ## Documentation Index
> Fetch the complete documentation index at: https://snapr.seshuk.im/llms.txt
> Use this file to discover all available pages before exploring further.

# SQLite

> Back up a single SQLite database file as a SQL text dump using the sqlite3 CLI.

`type: sqlite` backs up a single SQLite database file by running `sqlite3 <file> .dump` and writing the resulting SQL to the archive.

## Example

```yaml snapr.yaml theme={null}
sources:
  - type: sqlite
    path: /var/lib/app/app.db
```

## Options

| Option | Type     | Required | Description                         |
| ------ | -------- | -------- | ----------------------------------- |
| `type` | `sqlite` | Yes      |                                     |
| `path` | string   | Yes      | Path to the `.db` / `.sqlite` file. |

## Requirements

* `sqlite3` must be installed on the snapr host and available in `PATH` (Debian/Ubuntu: `sqlite3`).
* snapr needs read access to the database file. SQLite uses file locks during the dump, so a backup taken while the application writes heavily may briefly fail — it will succeed on the next scheduled run.

## Notes

* The output is a `.sql` text dump named after the source file (for example `app.sql`). Restore it with `sqlite3 new.db < app.sql`.
* For binary copies (faster restore, larger size), use a [local source](/configuration/sources/local) pointed at the database directory while the application is stopped.

## Related

* [Sources overview](/configuration/sources/overview)
* [Local files source](/configuration/sources/local)