Better designed apps allow export/import of configuration as a single file, e.g. all decent network appliances provide this (all routers, my NAS, Pi-hole etc.), like as .tgz, .txz archives, or Sqlite files.
https://www2.mobileread.com/i/smilies/eek.gif eventually happens, so configuration backups are useful, say on upgrade. Maybe one or more Calibre plugins could fix this oversight, ... if supported outside a Preferences open ...
Quote:
Originally Posted by DNSB
It's not a question of if but when. If you have followed the posts about using calibre with the library in the cloud/on a NAS/whatever, the first words tend to be similar to "I've done this for years and now my calibre library is corrupt." I'd avoid the chance of an error by keeping my library local and saving a backup copy to cloud storage when calibre is not running.
|
Yes, live use on cloud storage is
https://www2.mobileread.com/i/smiliesadd1/smack.gif, for various reasons, but single access use on a decent NAS, via a wired end-to-end (not WiFi!) connection, can be low risk.
I keep most of my libraries on a TrueNAS Scale spinning-rust box with a wired LAN, because of my library(s) size, the significant IO caching, and the far better data security of transactional Copy-On-Write storage, than on any local logging filesyste, and rarely see integrity issues. Large calibre libraries are best on, far more expensive, SSD storage because of the significant seek delays Calibre file IO can cause on spinning-rust disks, e.g. minutes just to change libraries or to quit Calibre, why?!
TrueNAS Scale (ElectricEel-24.10.2.1) supports hosting Calibre via a Docker App with Web-VNC, but I don't use it much because the usable functionality is inferior to a local desktop instance, however it's still better than the Calibre web server. A possible better compromise could be a network API exposed by a NAS instance of Calibre, and a separate desktop instance(s) of Calibre running in network client mode, which recognise network share access for the book content files.