Quote:
Originally Posted by mbovenka
The solution, I think. I use FFS to backup my Calibre setup, and I have no issues with Check Library. It puts a lock file in the source directory, but removes it when done.
|
Thanks
Quote:
Originally Posted by ilovejedd
The sync.ffs_db is optional. It's only created if you select certain settings. I think it was if you enable keep track of moved files? In any case, it's just a single file and it'll be in the same location as metadata.db so quite easy to add to exceptions for Check Library.
Logs are stored in the user's AppData folder by default, iirc.
As mentioned, FFS does create a temporary lock file during sync which gets deleted right after.
|
That was it. Seeing that file name, and after a sleep, I can recall the details.
A fellow member of the local b&m library reading group was getting IO errors on one of his metadata.db files, another member suggested he delete "the database" and run the Library->Maintenance->Restore database.
He deleted metadata.db
and sync.ffs_db. After running the calibre database restore everything was fine with calibre. But when he ran FFS it complained about its missing database. That's when he called me.
He's a law professor, with limited IT knowledge. He wanted the archive/versioning features of FFS for his Documents folder (his calibre libraries are at %appdata%\Calibre\Libraries). After I gave him some choices he opted to switch to Goodsync, which doesn't write in user folders and uses NTFS' VSS feature rather than lock files.
Quote:
Originally Posted by theducks
Extra files generate warning MESSAGES. In this case, they do no harm, do not indicate 'problem' book entries. I even believe there is an option to 'ignore in the future". As ALWAYS: 'Ignores" should be used with KNOWLEDGE and care
|
Calibre ain't always the only kid on the block. The lawyer thought it better to invest the price of half a bottle of Whisky to keep the backup tool's thumb out of calibre's pie
@
AnotherCat - we x-posted
BR