Skip to content
Klyo Changelog

Verified database snapshot taken before every migration

Every schema migration now starts with an automatic, verified snapshot of the database. The snapshot is checksummed and a sample restore is attempted before the migration runs; if either step fails, the migration aborts and the prior state is preserved.

A failed upgrade always has a restore point on the same host. The snapshot is retained for the configured backup window and is visible to the existing backup tooling.

Operators who already snapshot at the infrastructure or volume layer can bypass the in-process snapshot by setting KLYVEX_SKIP_PREMIGRATE_BACKUP=1. The skip is logged in the audit trail.

No action required. The snapshot runs by default for both fresh installs and existing tenants, on every migration regardless of how it is triggered.