Normal system backups of DEVONthink databases (TimeMachine, ChronoSync, Arc, CCC, Backblaze, whatever) should be good enough and work just fine. Not complicated. And can and should be automated. Just what you want. Not sure why you are hesitant of doing this normal, automated, standard way of backing up DEVONthink databases as part of normal system backups.
Archive zip files great for moving a database somewhere else, or simply taking a (as the name suggests) an “archive” copy for whatever reason. Or use this as yet another backup.
I’m not convinced I NEED these database archives, but as it “costs” me basically nothing in money or system performance I do it. And creating one for a database is a standard part of DEVONthink, and can be automated.
To make scheduled archive backups, see the whole thread, but I copied and tweaked this one. It zips all the currently open databases to archive. Read the whole thread, but this one sums it up and works.
I use a macOS cron job to launch this apple script once a week. DEVONthink needs to be open when this goes, so it’s scheduled in the morning when I can expect to be at my desk with the Mac not sleeping.
I have a Hazel rule setup to delete any zip files older than the three most recent.
Works great. And I’ve tested that the databases can be restored from these archives. Not the indexed files, of course. These zip archives (and indexed files) backed up by the normal system methods.
This another reason to rely on the DEVONthink forum to learn good stuff about DEVONthink.
that would not be useful, IMHO. That implies you are indexing stuff. Frankly, don’t bother. DEVONthink not a Finder replacement. It’s more than that. And these indexed files NOT in the database archive anyway, so back to the top paragraph here on this post.