Backup of large database
So I have finally decided to subscribe to unlimited storage for my Zotero files. This is in part to replace my (a little more complicated) setup with backing up my files automatically with dropbox. I know using dropbox is strongly discouraged as there is a risk of file corruption, but I figured I was safe because I never accessed my data on any other device, and it would be possible restore data file from an older version from dropbox, in case the most recent one got corrupted.
But now that I expect to use zotero from different devices, I decided to abandon this setup, and sync all my data on zotero servers. The issue I now have is that Zotero guidelines are to not rely on syncing as backup of files. This is little bit of a problem for me because with the way zotero database is set up, my data results in about 300,000 files (for about 8000 database entries) which literally take hours to copy/backup. What is the recommended method for backing the zotero database, when you have a large database?
(On dropbox this was manageable once the initial sync was completed, as only a small number of files would need to be updated after that. On OneDrive, which my workplace offers for free, I can't even get the initial backup to work because it freezes due to too many files being saved at the same time. And as I said, copying the the database to another drive on the computer takes several hours)
Any suggestions would be much appreciated.
But now that I expect to use zotero from different devices, I decided to abandon this setup, and sync all my data on zotero servers. The issue I now have is that Zotero guidelines are to not rely on syncing as backup of files. This is little bit of a problem for me because with the way zotero database is set up, my data results in about 300,000 files (for about 8000 database entries) which literally take hours to copy/backup. What is the recommended method for backing the zotero database, when you have a large database?
(On dropbox this was manageable once the initial sync was completed, as only a small number of files would need to be updated after that. On OneDrive, which my workplace offers for free, I can't even get the initial backup to work because it freezes due to too many files being saved at the same time. And as I said, copying the the database to another drive on the computer takes several hours)
Any suggestions would be much appreciated.
Online Zotero storage will help you if, say, your computer dies (and it has saved many people's libraries), but it's technically not a proper backup because there's no version history. So if you make a change you didn't mean to make and then sync, you can't restore it (not counting the automatic backups Zotero keeps for a couple days in the local data directory).
Not saying it is a limitation of Zotero. But the way the database is set up (thousands of small files, rather than fewer larger files) makes it take a very long time to copy and transfer files. Maybe there is no other way.
While we're on the topic of files: why is that the sqlite file of my original zotero installation is 740 MB, but when I synchronize the entire database (with all info, data, and attachments) to another computer, the sqlite file on the new computer is only 180 MB?
In any case, this just isn't a problem with a proper incremental backup system like Time Machine. Probably a combination of a couple things:
1) The other computer hasn't done full-text content indexing yet. If you have full-text content syncing enabled on both computers, it should do it automatically in the background. You can force it to index unindexed items from the Search pane of the preferences, though if you're using "as needed" file-syncing mode that won't work (which is why full-text content syncing exists).
2) New databases can be smaller due to decreased fragmentation. If you check your database integrity from the Advanced → Files and Folders pane of the Zotero preference, it will currently perform a cleanup operation on the database that might decrease the size a bit. (This could take a while on a 700 MB DB, so be prepared to let it go if you do this.)