# Duplicati fails deadly?

**URL:** https://forum.duplicati.com/t/duplicati-fails-deadly/6509
**Category:** Support
**Created:** [March 6, 2019, 5:53pm UTC](https://forum.duplicati.com/t/duplicati-fails-deadly/6509 "2019-03-06T17:53:37Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![kees-z](https://forum.duplicati.com/user_avatar/forum.duplicati.com/kees-z/32/29_2.png) [@kees-z](https://forum.duplicati.com/u/kees-z)
#### Post date: [March 6, 2019, 7:29pm UTC](https://forum.duplicati.com/t/duplicati-fails-deadly/6509/2 "2019-03-06T19:29:44Z")

</div>

I partially agree, but it’s just how you look at it.

If a backup solution says the backup completed successfully, but the contents of one or more source folders is skipped completely, you could be unpleasantly surprised when you have to restore files from that source folder.

Duplicati could continue the backup operation for the sources that still exist, but the main developer chose to abort the backup and throw an error message in this case. Underlying meaning is that the backup operator should regularly check and/or monitor the backups for errors or warnings. [Duplicati-Monitoring](https://duplicati-monitoring.com) and [dupReport](https://forum.duplicati.com/t/announcing-dupreport-a-duplicati-email-report-summary-generator/1116) could help monitoring your backups.

There’s some discussion about this topic [here](https://github.com/duplicati/duplicati/issues/2919) and [here](https://github.com/duplicati/duplicati/issues/2760).

---

_[View the full topic](https://forum.duplicati.com/t/duplicati-fails-deadly/6509)._