# Automatic backup monitoring

**URL:** <https://meta.discourse.org/t/automatic-backup-monitoring/261122>\
**Category:** Self-hosting\
**Created:** [April 9, 2023, 8:42pm UTC](https://meta.discourse.org/t/automatic-backup-monitoring/261122 "2023-04-09T20:42:24Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Luke\_Cousins](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/luke_cousins/32/223644_2.png) [@Luke\_Cousins](https://meta.discourse.org/u/Luke_Cousins)\
**Post date:** [April 10, 2023, 8:52am UTC](https://meta.discourse.org/t/automatic-backup-monitoring/261122/4 "2023-04-10T08:52:57Z")

</div>

Thanks. If there’s no way to set a “hook” after a backup has been completed, then I think the idea of reverse engineering the discourse API to find the most recent backup, is probably the way to go, and then we have full control over what to do if a backup hasn’t worked… but if a hook (web or shell command) could be added post-backup, that would be ideal.

Thanks for your help 👍

---

_[View the full topic](https://meta.discourse.org/t/automatic-backup-monitoring/261122)._