Feature request: pre- and post-backup script hooks #92

New Issue

MrUnknownDE · 2026-04-05T16:15:44+02:00

MrUnknownDE commented

2026-04-05 16:15:44 +02:00

Originally created by @Alter-Evo on 2/27/2026

I would like to propose a feature enhancement regarding scheduled backup tasks.

The application already provides a notification mechanism to report whether a backup job has succeeded or failed. However, it would be very useful to introduce the ability to execute custom scripts before and after a scheduled backup task.

This feature would enable integration with external monitoring systems that rely on a “dead man’s switch” model, such as Healthchecks.io. These services expect to receive an HTTP request when a job starts and/or completes in order to verify that the task is running as expected. In some cases, it is also desirable to include relevant log output in the request body.

Specifically, I suggest:

A configurable pre-backup hook (executed before the backup starts)
A configurable post-backup hook (executed after the backup completes, regardless of success or failure)
Optional access to job metadata (status, timestamps, exit code)
Optional access to log output, so it can be forwarded in the HTTP request body if needed

This would provide greater flexibility for integrations and allow the backup process to be monitored by external systems without relying solely on built-in notification channels.

Thank you for considering this enhancement.

*Originally created by @Alter-Evo on 2/27/2026* I would like to propose a feature enhancement regarding scheduled backup tasks. The application already provides a notification mechanism to report whether a backup job has succeeded or failed. However, it would be very useful to introduce the ability to **execute custom scripts before and after a scheduled backup task**. This feature would enable integration with external monitoring systems that rely on a “dead man’s switch” model, such as Healthchecks.io. These services expect to receive an HTTP request when a job starts and/or completes in order to verify that the task is running as expected. In some cases, it is also desirable to include relevant log output in the request body. Specifically, I suggest: - A configurable pre-backup hook (executed before the backup starts) - A configurable post-backup hook (executed after the backup completes, regardless of success or failure) - Optional access to job metadata (status, timestamps, exit code) - Optional access to log output, so it can be forwarded in the HTTP request body if needed This would provide greater flexibility for integrations and allow the backup process to be monitored by external systems without relying solely on built-in notification channels. Thank you for considering this enhancement.

MrUnknownDE closed this issue

2026-04-05 16:15:44 +02:00

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/databasus#92