8/24/2023 0 Comments Sqlpro finished with error![]() ![]() ![]() The error is: Failed: Unexpected difference in fileset version 6: 3:43:02 AM (database id: 53), found 11 entries, but expected 12Äetails: : Unexpected difference in fileset version 6: 3:43:02 AM (database id: 53), found 11 entries, but expected 12 Another version of this same backup job (this time to another local USB drive) failed this morning at ~4am. Though there are reports of this happening on systems that are always on, itâd still be a good idea to see if that happens to you, or if things like sleep or restart tend to encourage this problem to show up sometime. You can also see if using âno-auto-compact helps, change Backup retention to Keep all backups, and (if network backup) set ânumber-of-retries higher.įileset 0 is the newest, so damage to an older fileset such as 4 (with 16 versions total) seems like it might be some sort of non-backup maintenance work such as a compact coming through, doing wider changes. Here is an example of how it looks in job logs. With such a small list, you could even humanly compare the file lists with an SQLite browser such as this.įor those of you who are seeing the error too much, Iâd suggest looking in logs for compact operations just before it. Count from those SQL queries should be the same. Technical details of this internal check are found here. If things look wrong, sometimes itâs better to stop than to spread the mess further. Programs are typically written to rely on things being the way they should be. Weâre not likely to hear from the original designer, however this is one of the self-checks Duplicati does to make sure its various database records are in order. Why doesnât Duplicati warn of the failure and then keep backing up? Posting big files here is not possible, so youâd post a link to a cloud storage share, Firefox Send, or similar. with source pathnames and other data removed to protect privacy. Iâm open to all kinds of theories, but rely on people who can see it to try to guess what encourages it and to consider adding logging, consider posting logs, and consider even posting database bug reports which are sanitized versions of the database, e.g. There have also been theories involving things like retention deletions. Manual compact ran, now unexpected difference in fileset is finding that compact without enough temporary file space can cause this. ![]() People have seen it on backups to local disk. The problem is that this is not the only cause. There has definitely been a network-problem cause identified by me here, reproduced by here, leading to possible code fixes at below:Ä®nsure that failed put operations throw exception #3697 Getting the error to stay away has been a problem for some people, but I hope we can use their results to try to figure out why it only seems to affect certain backups. Change Command at top to delete, then Run at bottom. The BACKUP command syntax gets turned into The DELETE command by deleting the source files from Commandline arguments and adding -version=4. The easiest way to delete a fileset is probably using the jobâs GUI Commandline and adjusting the screen. Is there any way to fix an âunexpected difference in filesetâ error other than deleting? is post although the original poster was also trying to avoid doing this, but troubleshooting there didnât get very far. Itâs too frequent for the two who have just posted. Whatâs your history with the error? That might hold you for awhile if itâs rare. The only frequently-successful repair that I know of is to delete the fileset version, which is probably what was suggesting (unless somehow it now requires deleting all the versions). Iâd love to know what youâd suggest doing to repair it Failed: Unexpected difference in fileset version 4: 4:03:11 AM (database id: 100), found 6180 entries, but expected 6181Äetails: : Unexpected difference in fileset version 4: 4:03:11 AM (database id: 100), found 6180 entries, but expected 6181Īt .LocalDatabase.Verifåonsistency (System.Int64 blocksize, System.Int64 hashsize, System.Boolean verifyfilelists, transaction) in :0Given that this is a moderately large fileset (57GB), Iâd love to know what youâd suggest doing to repair it. The fileset from version 4 (2/24) has the unexpected difference in the number of entries. The most recent successful run was on March 2nd. There are 16 versions of this backup set. Iâve not changed anything on that configuration AFAIK. I started getting this error on one my backup sets. I have been getting this fatal error for weeks.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |