# "missing files" error after switching to custom retention policy

**URL:** https://forum.duplicati.com/t/missing-files-error-after-switching-to-custom-retention-policy/2695
**Category:** Support
**Created:** [March 1, 2018, 3:25am UTC](https://forum.duplicati.com/t/missing-files-error-after-switching-to-custom-retention-policy/2695 "2018-03-01T03:25:06Z")
**Posts on this page:** 1
**Showing post:** 12

<div class="post-metadata">

### Author: ![JonMikelV](https://forum.duplicati.com/letter_avatar_proxy/v4/letter/j/439d5e/32.png) [@JonMikelV](https://forum.duplicati.com/u/JonMikelV)
#### Post date: [March 14, 2018, 3:26pm UTC](https://forum.duplicati.com/t/missing-files-error-after-switching-to-custom-retention-policy/2695/12 "2018-03-14T15:26:51Z")

</div>

So I backed up my database just in case I wanted to do some more testing then went ahead and ran another backup WITHOUT doing a repair first, but WITH the `--no-backend-verification=true` parameter added.

As expected, the backup ran just fine - though it did complain (warnings, not errors) about not being able to delete files that were already deleted.

> [@Repeated "Delete operation failed" due to file not found](https://forum.duplicati.com/t/repeated-delete-operation-failed-due-to-file-not-found/2852):
>
> Let me start by saying I understand I should be able to resolve this issue by doing a database repair. I’m posting this because I think a repair should not be necessary and am hoping somebody can explain to me why it is. After changing my retention policy a bunch of destination files were cleaned up as they should be, however something went wrong when recording it in the local database. So now when the back runs it finishes just fine (so backups are working) but tosses out 48 sets of messages…

Removing the `--no-backend-verification` parameter puts me back in the “Found n files that are missing from the remote storage” failure scenario.

Guess I’m off to do a database repair. 🙂

---

_[View the full topic](https://forum.duplicati.com/t/missing-files-error-after-switching-to-custom-retention-policy/2695)._