@
RotAnal - if you can do the 'database backup' via
calibredb backup_metadata command you should find it's a lot faster. By design, the option in the GUI does it as a very low priority 'background' task, it typically chugs along at about a book a second, whereas the command line option does it as a normal priority 'foreground' task and executes as fast as it can.
Quote:
Originally Posted by RotAnal
<snip>
I wonder if it would be possible to change machinery so that it works on ONE certain library only.
|
FWIW - I now have the content of my libraries on a Windows server. I have symlinks at the server referencing workstation resident library metadata databases. 'Logically' they are something like:
At server <libraryName>\metadata.db files reference ...\Metadata\<libraryName>.metadata.sqlite files at workstation.
This may or may not be doable on your NAS and workstation setup.
I changed the extensions to .sqlite because Windows regards .db files as something 'special' - thumbs.db and all that jazz. Obviously the server side symlinks must conform to calibre's expectations, so they retain the metadata.db name. On Windows the name of a symlink and its target do not have to be the same, I have a vague recollection from aeons ago that on another OS they did have to be the same.
BR