# Failed: Invalid header marker **URL:** \ **Category:** Support\ **Created:** [March 12, 2018, 3:32pm UTC](https://forum.duplicati.com/t/failed-invalid-header-marker/2871 "2018-03-12T15:32:32Z")\ **Posts on this page:** 1\ **Showing post:** 45
**Author:** ![rinaldi6109](https://forum.duplicati.com/letter_avatar_proxy/v4/letter/r/439d5e/32.png) [@rinaldi6109](https://forum.duplicati.com/u/rinaldi6109)\ **Post date:** [December 23, 2019, 3:34pm UTC](https://forum.duplicati.com/t/failed-invalid-header-marker/2871/45 "2019-12-23T15:34:32Z")
> [@ts678](#): > > Do you know of good examples of software handling damaged backups? No, I don’t. But in my experience with Duplicati the rate of backups that end up damaged is very high, and this is not normal for a end user. You gave nearly ten approaches, but the only one that I can easily follow is to avoid upload throttle option. Unfortunately, if I have well understood, once the damage is done, deleting such option doesn’t solve the issue. The other hints are out of my reach, mainly because the time. I have a normal life with limited (even cognitive) resources, and I don’t understand a lot about logs, exadecimal editors, and how to identify a damaged file among thousands. So, the simplest thing a user lke me can do is to delete a backup and start a new one. As long as a new damage occurs. This is my sad truth. --- _[View the full topic](https://forum.duplicati.com/t/failed-invalid-header-marker/2871)._