# Notification when uploading backup to cloud storage fails

**URL:** <https://meta.discourse.org/t/notification-when-uploading-backup-to-cloud-storage-fails/269994>\
**Category:** Feature\
**Tags:** backups, s3\
**Created:** [June 29, 2023, 7:39am UTC](https://meta.discourse.org/t/notification-when-uploading-backup-to-cloud-storage-fails/269994 "2023-06-29T07:39:09Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![gerhard](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/gerhard/32/119479_2.png) [@gerhard](https://meta.discourse.org/u/gerhard)\
**Post date:** [June 29, 2023, 12:46pm UTC](https://meta.discourse.org/t/notification-when-uploading-backup-to-cloud-storage-fails/269994/3 "2023-06-29T12:46:23Z")

</div>

The backup process is supposed to clean up when it’s finished, even when there was a failure. But it’s possible that the OS kills the backup process before it’s able to do that cleanup. Reasons I can think of right now:

- the host restarts (maybe because of OS upgrade)
- the Docker container restarts (maybe because the Docker daemon is updated or crashed)
- the system runs out of memory and kills processes
- the process crashes for whatever reason and isn’t able to exit cleanly

I guess the feature request here is: A background job should check if a backup was aborted. In that case it should cleanup temporary artifacts of the backup and send a warning to the admin.

---

_[View the full topic](https://meta.discourse.org/t/notification-when-uploading-backup-to-cloud-storage-fails/269994)._