View Single Post
Old 02-01-2021, 12:48 AM   #2119
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by tgoold View Post
I'm having an issue with the backup, that just started a couple of days ago. I'm not sure exactly what to do about it.

Calibre version: 5.10 & 5.10.1
OS: Mac OS 11.1 Big Sur
Plugin version: 2.12.3
Device: Kobo Libra H2O

Here's the message that I get from the details of why the backup failed:


When I run the database check, I get a similar message:


Any idea of what I should do to try to figure out where the problem is?

I did have a book that had two copies on the device, but I removed it and put back one copy, and when I reconnected the Kobo, it still said that it couldn't backup the database with the same error message. (Those messages were taken after I fixed the issue of the two copies on the Kobo.)
Firstly, having multiple copies of the same book on Kobo devices doesn't matter. I do it all the time. The filepath is used to distinguish between them in the database and hence in the UI. I noticed last night that I had five copies of a book on one of my devices. One was probably an kepub version, but the others were files that I had renamed on the device while doing some testing.

Those messages say the database is corrupted. They are actually the same. The backup process does a check of the database as part to warn you of issues. And to make sure it doesn't save an invalid backup.

Those particular errors are probably not going to cause any real issues. But, they can be a precursor of more damage. Calibre and the device re probably accessing the database OK, but, it is possible that they aren't writing changes successfully. On the device, this would be noticed as book status not updating, or books being reimported. And this can be noticed especially after restarting the device.

The general fix for a corrupt database is to restore a recent backup of the database, or to sign out of the Kobo account on the device. With the latter, it will reload the sideloaded books, but, you will lose the reading status and annotations. But, with those particular errors, a compress of the database may fix it. The compress basically exports the data and reimports it to rebuild the database structures. Errors in the index will generally be fixed by this.
davidfor is offline