Rask.SQLite.Snapshots 0.23.1-alpha.0.61

Rask.SQLite.Snapshots

Scheduled, consistent SQLite backups — no external binary. Takes point-in-time file snapshots of a live SQLite database on a schedule using SQLite's Online Backup API (never an unsafe File.Copy of a WAL database), keeps the newest N, and writes them to a directory — or a pluggable store for object storage.

Use it on its own for simple periodic full backups without a sidecar or object storage, or alongside Rask.SQLite.Litestream (continuous streaming) as a second line of defence. Standalone: depends only on Microsoft.Data.Sqlite and the Microsoft.Extensions hosting/DI abstractions.

Install

dotnet add package Rask.SQLite.Snapshots

Use

builder.Services.AddRaskSqliteSnapshots();

// appsettings.json
{
  "Rask": {
    "Snapshots": {
      "DestinationDirectory": "/backups",
      "Interval": "06:00:00",
      "Retain": 14,                 // keep the 14 newest
      "SnapshotOnStartup": true     // also take one at boot
    }
  }
}

It snapshots the database behind Rask:ConnectionStrings:App unless DatabasePath names another. A callback — AddRaskSqliteSnapshots(o => …) — runs after the Rask:Snapshots section and wins.

Snapshots land as app-20260714-030000000.db — each a complete, standalone SQLite database you can open, copy or archive.

Need a backup on demand (say, before a risky migration)? Inject ISqliteSnapshotter:

var name = await snapshotter.SnapshotAsync(ct);

Sending snapshots to object storage instead of a directory? Register your own ISqliteSnapshotStore before AddRaskSqliteSnapshots and DestinationDirectory is no longer required.

To show what you've captured, await store.ListAsync(ct) returns each snapshot's name, size and timestamp, newest first. A custom store inherits a default that returns an empty list — override it if yours can enumerate, because callers can't tell "no snapshots yet" from "this store doesn't list".

Notes

• Consistent, not a raw copy. The Online Backup API copies pages while writers continue, so the snapshot is a valid database even under load — unlike copying the file yourself.
• Resilient. A failed snapshot is logged and the schedule continues; a backup problem never crashes the app.
• Dedicated directory. Point DestinationDirectory at a directory used only for snapshots — pruning is scoped to this database's own files, but a dedicated directory keeps things tidy.

Full documentation: https://github.com/pal-tamas/rask/blob/main/docs/sqlite.md#scheduled-snapshots