Back up and restore

Treat the database, uploaded media, environment configuration, and release code as separate recovery inputs. A database dump does not include uploaded files, and a code archive does not include production configuration or customer data.

Before each upgrade:

1. Create a database backup and verify the compressed archive and checksum.
2. Verify that uploaded media has a separate recoverable copy.
3. Protect the environment file, signing/certificate material, and provider credentials separately from the application archive.
4. Record the source release, edition, database engine/version, and backup time.
5. Restore the backup to an isolated environment and compare key record counts, totals, relationships, and representative media before relying on it.

For a restored environment, use separate credentials and disable scheduled jobs and external side effects. Scrub personal data where appropriate and set a retention/deletion date. Never use a restore drill that can overwrite the live database or send production messages, capture payments, book shipments, or release payouts.

Do not delete the only verified recovery copy after an upgrade. Define retention and off-site storage with the operator responsible for the installation.