Quote:
Originally Posted by paai
Is it possible that the problem lies in the fact that during the backup, the metadata.db gets backed up too?
I use Luckybackup with rsync on a Linux machine, and in theory the metadata.db in the live directory is always the same age or newer than the file in the backup. So that should work.
Now say, I made a mistake and changed the database in the backup tree. Now this metadata.db is newer and gets copied over the live one. Will it bring the pathnames of the backup with it and overwrite the pathnames in the live database? Thatwould explain a lot.
Paai
|
I suggest you configure Luckybackup/rsynch to maintain a one-way mirror of your library. Then it won't propagate any inadvertent changes you make to the backup library across to the live library.
If you want the backup library to be permanently accessible in calibre I recommend you give the backup library folder a different name to lessen the chances of you making inadvertent changes to it. Maybe Luckybackup/rsynch has a feature to facilitate that, or you could do it via pre-sync and post-sync script commands.
BR