View Single Post
Old 06-26-2024, 09:54 AM   #4
sgmoore
Zealot
sgmoore ought to be getting tired of karma fortunes by now.sgmoore ought to be getting tired of karma fortunes by now.sgmoore ought to be getting tired of karma fortunes by now.sgmoore ought to be getting tired of karma fortunes by now.sgmoore ought to be getting tired of karma fortunes by now.sgmoore ought to be getting tired of karma fortunes by now.sgmoore ought to be getting tired of karma fortunes by now.sgmoore ought to be getting tired of karma fortunes by now.sgmoore ought to be getting tired of karma fortunes by now.sgmoore ought to be getting tired of karma fortunes by now.sgmoore ought to be getting tired of karma fortunes by now.
 
Posts: 138
Karma: 642206
Join Date: Mar 2021
Device: Kindle Voyage
Quote:
Originally Posted by BetterRed View Post
You could do what I do:

Run calibredb backup_metadata against each calibre library at the start of the backup script, that will finish off any outstanding updates at full throttle. Gets them out of the way for next time you start calibre.

BR
Just to double check.

Does that mean I should Stop calibre first and then run the "calibredb backup_metadata" command.

I can't seem to run this command while calibre is running (even with the --with-library option), but I was worried that stopping calibre would lose any outstanding updates.
sgmoore is offline   Reply With Quote