Does Sentry automatically create a pre‑upgrade backup before running sentry upgrade?

Administrators need to know whether the sentry upgrade command produces any backup artifacts before applying schema migrations and code changes.

The official documentation advises taking a manual PostgreSQL dump and copying configuration files, yet the upgrade tool does not enforce this step and offers no automated rollback if a migration fails mid‑process.

Understanding the exact behavior is essential for planning safe maintenance windows and for defining a reliable recovery procedure.

• Does the upgrade command create a backup directory or snapshot automatically?
• Is there a flag or configuration option to trigger an automatic pre‑upgrade backup?
• What manual steps are recommended to restore a consistent state after a failed upgrade?