Accept SQLite VACUUM INTO output only after completed execution

Stage compacted SQLite outputs and accept only completed, checked recovery artifacts.

Source facts

SQLite VACUUM INTO writes a compacted copy to a separate output file while leaving the source database unchanged. The output is a consistent snapshot when the operation completes, but interruption by power loss or unplanned shutdown can leave it incomplete and corrupt. The named output must not already exist unless it is empty. The documentation also describes synchronization of completed output when the source connection’s synchronous setting is NORMAL or FULL, subject to functioning operating-system and storage guarantees.

Source: SQLite — VACUUM.

Applicability

This applies to SQLite versions supporting the documented VACUUM INTO behavior. It addresses output acceptance and destination handling, rather than the incremental Online Backup API or every application’s recovery procedure.

DSE recommendation

DSE recommends creating each output at a unique staging path and recording command completion before promoting it into the backup inventory. Have the application owner confirm that its SQLite release and connection settings match the procedure. Treat an interrupted output as unaccepted until it is replaced by a completed run and reviewed. Keep destination ownership and free-space checks explicit. Avoid overwriting the only known recovery copy while experimenting with a compacted export or maintenance schedule.

Verification

With disposable data, generate an output at an unused path, retain the completion result, and open that output independently for integrity and application checks. Rehearse interrupted-run handling separately. Confirm the backup inventory accepts only the completed artifact and keeps older recovery copies until acceptance is finished.

Official reference

SQLite — VACUUM. Reviewed October 15, 2026.