[GH-ISSUE #138] Feature Request: Add Application Version Metadata to Backups #115

New issue

Open

opened 2026-02-26 21:34:30 +03:00 by kerem · 0 comments

kerem commented

2026-02-26 21:34:30 +03:00

Owner

Originally created by @michaelvips on GitHub (Oct 1, 2025).
Original GitHub issue: https://github.com/eduardolat/pgbackweb/issues/138

Add Application Version Metadata to Backups

In some Docker-based applications, when updating to a new image, database migrations are automatically applied. In this scenario, a backup taken before the update can only be safely restored if the database is running with the same application version that was active at the time of the backup. Currently, pgbackweb does not provide a way to associate backups with the application version.

It would be useful if pgbackweb could store application version information alongside each backup. Some possible approaches:

Allow passing the application version (via environment variable, Docker tag, or config) and attach it to the backup.
Include the version in the backup filename or backup directory.
Generate a small metadata file (e.g., JSON/YAML) containing application version, date, and other relevant details.

alternatives

Manually renaming backup files with the application version (error-prone and hard to standardize).
Keeping a separate log mapping backups to versions (adds extra overhead and risk of losing consistency).

context
This feature would make it easier to manage backups across application updates, avoid incompatibilities, and provide more clarity when restoring data in version-sensitive environments.

Originally created by @michaelvips on GitHub (Oct 1, 2025). Original GitHub issue: https://github.com/eduardolat/pgbackweb/issues/138 ### Add Application Version Metadata to Backups In some Docker-based applications, when updating to a new image, database migrations are automatically applied. In this scenario, a backup taken before the update can only be safely restored if the database is running with the **same application version** that was active at the time of the backup. Currently, pgbackweb does not provide a way to associate backups with the application version. It would be useful if pgbackweb could store application version information alongside each backup. Some possible approaches: - Allow passing the application version (via environment variable, Docker tag, or config) and attach it to the backup. - Include the version in the **backup filename** or **backup directory**. - Generate a small metadata file (e.g., JSON/YAML) containing application version, date, and other relevant details. **alternatives** - Manually renaming backup files with the application version (error-prone and hard to standardize). - Keeping a separate log mapping backups to versions (adds extra overhead and risk of losing consistency). **context** This feature would make it easier to manage backups across application updates, avoid incompatibilities, and provide more clarity when restoring data in version-sensitive environments.