View Single Post
Old 02-27-2022, 08:34 PM   #454
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 compurandom View Post
I wish that was 100% true, but I've found that the database corruption can be subtle and not immediately detected, and the most recent backup may also be corrupt.
The backup runs a full check after taking a copy of the database file. If there are any problems with the database, you will see an error and "CORRUPT" will be added to the file name.

Putting the database back on the device can result in a corrupt database. As you don't have control of everything involved what is happening, something could happen to corrupt the database after it is replaced. I have not decided on the best way to do it. I power off, but, whether it is better to do it as soon as the device is disconnected or after the home screen is displayed, I'm not sure.
davidfor is offline   Reply With Quote