Quote:
Originally Posted by DaltonST
1. It has nothing to do with bytes saved. Not at all. It is all about saving hours and hours a week of backup time for huge libraries with hundreds of thousands of small files that change all of the time due to mass-maintenance of metadata, such that you avoid backing up because of the time it takes. If you make external and verified copies of metadata.db, you do not need to back up the .opf files if it becomes so burdensome that don't back anything up.
|
Interesting claim. Personally, I do not find it takes much time to back up the changes to hundreds of thousands of files, or at least, a few thousand (not everyone's library is
multiple tens of thousands of books, and for
hundreds of thousands of files I expect
hundreds of thousands of books, minus the three metadata.db/backup-restored.db/prefs files, times three or perhaps four files per book record).
- Perhaps that is because as a backup service I allow it to happen unobtrusively, as a service.
- Perhaps it is because I do incremental changes. It is not entirely unlikely that there are other calibre users out there, that do NOT constantly perform mass operations that completely redefine metadata for all books.
Most of my books remain pretty much the same after I process them, and my custom columns don't change much. (When they do, yes -- that impacts all metadata.opf files.)
- Perhaps both...