Quote:
Originally Posted by kovidgoyal
There are many thing in the db that a restore will not restore. Plugin data, book specific conversion settings, etc.
A restore is basically designed to restore only your book metadata, as that is the most precious thing. A restore should really be a last resort thing to do if you dont have backups.
And you can often recover a bad sqlite db by dumping it to sql and using the sql to re-create it, you might need to manually edit the sql a little to fix errors.
|
Thanks! Looks like the conversion settings (for 4,000+ books) was the culprit. I always do bulk conversions so I never realized that per book conversion settings were getting stored in metadata.db. I'll need to make a habit of deleting those via bulk metadata edit. I do versioned backups of metadata.db (sometimes up to 5 times in one day) so that should save quite a bit of space.
Yep, the metadata is the important part. The database wasn't actually bad or corrupted at all. I just did something stupid and accidentally changed tags that I didn't mean to change and restoring the old tags was priority. Anyway, I actually do have copies of the library in several flash drives that I forgot in the office. I just didn't want to wait until Monday to test out some things so I tried out the Restore database function and I'm happy to report it worked wonderfully. I'll nuke this library and restore from backup but in the meantime, I was able to test a bunch of regex stuff for search and replace, and MCS as well as templates for save to disk.
