Quote:
Originally Posted by MightyDuck
So basically periodically rsync on the library directory or exporting all the data with calibre-debug --export-all-calibre-data. The server must be stopped in both cases? Using rsync I think it can keep running as long as you don't make changes during the copy procedure.
|
Use any sync program you want. Best is one that does a one-way sync of only the changed files calibre-machine -> server. Don't mirror. I wouldn't use calibre export unless your library is very small because it will copy everything, not just the changed files.
You probably should sync the calibre configuration directory as well, to pick up changed options. The command line args used to start the server will override the library paths in the configuration.
Calibre on the machine with the library must be stopped before the sync to be sure the info in the config directory and the db are up-to-date and won't change in the middle of the sync.
The server must be stopped while metadata.db and the configuration directory are being updated. I think it is safe to leave it running while the library directories are being updated, but personally I wouldn't take the chance of hitting some kind of lock.
Note that some web client viewer operations can modify the library, particulary reading positions for syncing between multiple instances of the viewer. These are stored by the server and thus will be lost.
Quote:
|
Thank you very much for the info by the way!
|
You are welcome.