Skip to main content

Plan a recoverable change

Before a schema migration, take an application-consistent data backup and record the app release ID. Test the restore procedure in an isolated environment. Rolling back code is insufficient if the database schema has become incompatible. A root-disk checkpoint is useful before changing system packages. Snapshot creation requires a stopped workspace and replaces its previous snapshot. Do not use snapshots as a multi-version backup archive.

Continue