I need a comprehensive solution that won’t let me do something like this again. The result was two weeks worth of clipping and storing gone. I had carefully backed-up my DT databases-but hadn’t known about the Global Inbox being in another location. I note that I just suffered a hard drive crash. This, too isn’t an optimal situation.Ĭan someone at least show me how to edit the script to insert a different backup location? The script “Export–>Daily Backup Archive” seems limited to putting the backup in a folder “backup” (where is it?) and does not allow one to change the backup location on the fly. I need to be able to back up all my DT databases (including the Global Inbox!) to an external drive, in as few steps as possible.Īs I understand it now, the command: file–>export–>Database Archive only works on one database at a time. (This is safe, but inconvenient to you.) you do not want to back that folder up, it does you no good.I’m still fairly new to DevonThink, and need some help on the perennial topic of backup. IN FACT restoring that folder from Time Machine is so profoundly the wrong thing, we “safety freeze” your backup if you do that. If your laptop is destroyed, all you need is on the Backblaze servers. For example, when you change a random file somewhere on your laptop, the last modification time and filename are recorded inside of /Library/Backblaze.bzpkg and the contents sent to the Backblaze servers, but the “cache” must be kept in /Library/Backblaze.bzpkg so it knows it already sent that file. Those files change CONSTANTLY, and are part of the “state” of your Backblaze backup, but absolutely not part of the “data”.

we changed it to a “bzpkg” folder to prevent that like a decade ago, I will look into it.

Yes! In fact, I am surprised it is backed up. Can /Library/Backblaze.bzpkg be excluded from Time Machine

Time machine backblaze