Quote:
Originally Posted by chaley
The one counter argument I can make is that the user might not remember what books were on the device. If the database were restored then the books would be listed in calibre on the next connect. The user could select them all and send them.
|
Good point. I was thinking that the database would be useless without the books for restore purposes, but I forgot that CC tells Calibre which books are "present" on the device. People would have to know thay they needed to resend the books the Calibre said were already there, but the backup/restore function is probably nerdy enough that people who use it will understand the extra work involved.
Quote:
Originally Posted by chaley
I would rather not have a pick & choose scheme. Lots of settings are related to each other in non-obvious ways.
|
I wasn't thinking that the user would pick and choose, but that the program would read the key and use that to set the value internally. As long as a person didn't try to restore a newer version of the backups on an older version of the program, there should never be a setting that didn't make sense.
Quote:
Originally Posted by chaley
Attaching the backup to an email message is an interesting idea. I was assuming that the user would put the file into dropbox or drive or what-have-you. CC would create the file wherever the user wants, then the user would use the cloud storage app of choice to get the backup off the phone.
|
Definitely the way to go if backing up the DB. The Email really only works for a small file like the settings.
Quote:
Originally Posted by chaley
Hmmm... I am not sure what happens if I install an SD card on a new machine when an app is using the private SD card app folder. Does the app adopt what is there? Does Android clear it first? My guess is that the folder is adopted or things would go bad very fast every time I swapped cards, but given that the kitcat changes make very little sense (to me) I don't trust my intuition.
|
I don't know either, but I would be glad to test this for you when I get my new phone. Or, perhaps I can test it by moving my SD card from my phone to my tablet. If the books files can still be accessed, we should be ok. I'll try that later.
Quote:
Originally Posted by chaley
One scheme would be to store the settings and DB backup in the Calibre_Companion folder and use Dropsync (or something like it) to upload that folder to Dropbox whenever a backup is made. That makes a self-consistent set of data.
|
True, but a common use of Dropsync is to do the backup automatically every time things change. Something like this might make for a lot of extra backups. Or a backup while the program was running.
Quote:
Originally Posted by chaley
A question related to backing up the db: should the calibre device ID also be backed up? If you are cloning a device or restoring after uninstall/wipe then restoring the device ID would prevent uploading all the metadata on the first connect after restore. However, if you are copying a device then restoring the device ID would be a bad idea because calibre would not be able to distinguish between them. It is very likely that metadata caching would break.
|
I would say no. This whole operation refers to something rare enough that an occasional extra metadata load is probably better then causing some problems in some situations.