The frequency of your backups usually determine the amount of data you loose should you need te restore a backup.
There are many things to consider with backups, and the amount of effort and money you put into it primarily depend on your loss should all your backups fail. To name just a few (and certainly not all) considerations, you might want to:
encrypt your backups (e.g. in case of theft)
use multiple external media on-site (e.g. in case a medium fails)
store at least one medium off-site (e.g. in case your house burns down)
regularly test your backups (e.g. in case you happened to backup the wrong data)
use additional read-only media like DVD-R or Blueray (e.g. in the case of ransomware attacks)
And the most important in my opinion: consider using a backup method that is automated to a level of âzero-effortâ. Most people that depend on a habit to backup, will eventually forget to do it, and that might be the moment you require your backup.
The easiest (zero-cost) backup method on macOS is Time Machine in my opinion (although other software might have additional benefits). It will back-up your data incrementally, only adding the files you changed. Keep in mind though Time Machine requires an HFS formatted disk and doesnât support APFS (yet) AFAIK. That said, once you get Time Machine going, you practically donât have to think about it anymore.
I hope I havenât asked this before, but is there a way to automate the verification proces (in line with reasoning behind automating back-ups)?
If subsequent repair might bring about changes that could be detrimental, I personally wouldnât want to automate that though. But an automatic warning that DEVONthink found errors would be nice IMO.
In the normal course of things, a repair or rebuild should have no ill effects on a database.
It would be possible to automate a verification using a Reminder. It would just require the addition of a Reminder script for the purpose. Perhaps that will be a new one in the Extras soon.
Perhaps I misunderstand, but wouldnât that still require some user action (i.e. acting upon the reminder)? That would be similar to set a reminder to perform a backup, which probably isnât as sustainable as a âzero effort, behind your backâ verify and repair I think.
Perhaps I misunderstand, but wouldnât that still require some user action (i.e. acting upon the reminder)?
No, thereâs no need to respond to a Reminder. That depends onthe what alarm type is. You can use an Execute External (or Embedded) Script as an alarm. That would just run the script at the time of the alarm.