Thread: [KOBO] Calibre has issue automatically backing up to remote disk
View Single Post
Old 09-11-2018, 08:27 AM   #4
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 Derf View Post
The database on the device is fine. I have all my reading stats, all my current reading locations. Everything is fine on the device.

When I use the plugin to fix errors on the device database it simply shows
Spoiler:

Result of running 'PRAGMA integrity_check' on database on the Kobo device:


ok


When the "automatic" backup happens when I plug in the device (if I have it so configured) happens, it throws an error. BUT, when there is no automatic backup, or when I manually use the plugin to create a backup, the backup completes with no error.

Again, as noted in my troubleshooting, if I change the target location of the backup from a remote disk on my LAN to a local hard disk, the problem vanishes. But when I set it back to the remote disk again, the problem reappears.

I wouldn't say the problem is with the remote disk, per-se, since manual backups complete without error, and Calibre is storing its database and ePub files there. But something is off with regards to the automatic backup on a remote disk.
In that case it has to be a problem with copying the database file to the server. The copy is done using OS functions, so there isn't really anything that can be done. Unless the issue is timing and the server is still doing something when the check is started. If that is the case, then adding a delay between the copy and the check. It might be interesting toc o a separate check of one of the backups that were reported to be corrupt.
davidfor is offline   Reply With Quote