# Non-empty blocksets with no associated blocks

**URL:** https://forum.duplicati.com/t/non-empty-blocksets-with-no-associated-blocks/7868
**Category:** Support
**Created:** [August 24, 2019, 7:04pm UTC](https://forum.duplicati.com/t/non-empty-blocksets-with-no-associated-blocks/7868 "2019-08-24T19:04:53Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![ts678](https://forum.duplicati.com/letter_avatar_proxy/v4/letter/t/8491ac/32.png) [@ts678](https://forum.duplicati.com/u/ts678)
#### Post date: [August 25, 2019, 11:29pm UTC](https://forum.duplicati.com/t/non-empty-blocksets-with-no-associated-blocks/7868/3 "2019-08-25T23:29:45Z")

</div>

Welcome to the forum @DBL

I’m sorry to hear about your Windows woes. I don’t know if you’re inclined to worry about Duplicati now. If you are, then [Warning: sqlite-journal errors 1400](https://forum.duplicati.com/t/warning-sqlite-journal-errors-1400/6702/2) was possibly a similar problem (except maybe easier to identify) where a file being actively changed during backup triggers that problem, and possibly also yours.

If you happen to have [specially installed](https://duplicati.readthedocs.io/en/latest/07-other-command-line-utilities/#duplicatiwindowsserviceexe) as a Windows service (or are otherwise running on Administrator privileges), [–snapshot-policy](https://duplicati.readthedocs.io/en/latest/06-advanced-options/#snapshot-policy)=Required would prevent Duplicati backing up Duplicati’s database while it’s actively changing. Another option to avoid that would be to [Edit in](https://duplicati.readthedocs.io/en/latest/03-using-the-graphical-user-interface/#editing-an-existing-backup) an exclude [Filter](https://duplicati.readthedocs.io/en/latest/appendix-d-filters/) for files beginning with your backup’s [Database](https://duplicati.readthedocs.io/en/latest/03-using-the-graphical-user-interface/#database-management) path. This will avoid the `.sqlite-journal` file that often seems to be the culprit. Commonly the DB isn’t intentionally backed up, but just gets backed up in wholesale backups, e.g. of C:\

Because above is a guess, logs such as default backup log, or [live log](https://duplicati.readthedocs.io/en/latest/03-using-the-graphical-user-interface/#viewing-the-duplicati-server-logs) at About --\> Show log --\> Live, or setting [–logfile](https://duplicati.readthedocs.io/en/latest/06-advanced-options/#log-file) might catch some other message or path that would help to figure out what the issue was.

Even better (if you’re willing to take a small risk of filenames being seen), is linking a [database bug report](https://duplicati.readthedocs.io/en/latest/03-using-the-graphical-user-interface/#creating-a-bug-report).

[FoundIssue1400Error](https://forum.duplicati.com/t/foundissue1400error/7844/3) took a DB-level look at that, and  
[CheckingErrorsForIssue1400 and FoundIssue1400Error test case, analysis, and proposal #3868](https://github.com/duplicati/duplicati/issues/3868) testing and theory suggests that these two issues are related.

---

_[View the full topic](https://forum.duplicati.com/t/non-empty-blocksets-with-no-associated-blocks/7868)._