Quote:
Originally Posted by cortman
Another thing to note (and kovid says the same thing) is that it is very important not to let Copy and Calibre run at the same time. If you are going to sync your Copy.com folder, close down Calibre first.
I use a similar setup- I have Calibre on two computers, and the library is on Copy.com. It works pretty good for me.
|
I don't think that there's any problem with a single instance of calibre running at a time (this doesn't apply to calibre-server, that's read-only). What you don't want to do is have two instances of calibre trying to update the same db at the same time.
Let's say I have a laptop and a desktop, both with a Copy folder with a local copy of the calibre library, synced by Copy.com. And let's also assume that the Copy.com client is actively running on both machines.
I open calibre on my laptop, do some library things, close calibre. Copy.com is uploading the changes as it sees them to individual files. When I close calibre on the laptop, the metadata.db file is updated, which Copy.com will sync up to the cloud. Depending on your upload speed and the number of changes you made to your library, this could take some time. Even if you simply open and close calibre without making any changes, your metadata.db file will be updated. Get familiar with monitoring Copy.com's status to know when it's done updating the cloud.
So far so good.
Now we turn to the desktop, where Copy.com is actively running. You definitely would want to make sure that the local Copy folder has been updated before opening calibre on the desktop. The Copy.com icon shows activity, but assuming you didn't make a lot of changes, that resync should be very quick. Again, you make changes to the db from the desktop version, and the affected files are uploaded to the Copy.com cloud.
My point is that as long as only one machine is editing the local copy of the db, all changes will pushed up from the active machine to the cloud. As long as you don't have more than one instance of calibre trying to edit the db, you should be fine. If you have more than one person managing your library, this would require some coordination. Otherwise, as long as it's one open instance of calibre at a time, you shouldn't need to do anything special for Copy.com.
What would be bad (very bad) would be having the laptop and the desktop both editing the same library at the same time, with Copy.com valiantly trying to push changes to the cloud, then the other machine. Very bad.
And, just to reiterate, none of this is a factor for calibre-server. It monitors changes to metadata.db and reloads as needed.
G