kw123 wrote:Time machine is too slow to backup any dB. And it is not consistent.
More specifically, if some process opens and keeps open a file, making changes randomly, then a timemachine backup will likely not correctly back the file up because it may not be in a stable state at the time it's read. Indigo doesn't do this: we load the entire Indigo database into memory and make changes to it there, and we periodically flush the changes to disk. This makes it safe for time machine to back up with minimal potential data loss (only changes between the time the change is made in Indigo and the time it flushes to disk).
SQL Lite generally works that way also. Postgres, like MySQL and other more powerful DB systems, don't do this so it's harder to get an external process like time machine to automatically back up. By flushing the DB to a file (i.e. sqldump) you're more guaranteed to get a good backup file that you can then import separately upon recovery.
Not sure I agree with the too slow statement - I've never had an issue with speed since time machine just automatically runs periodically in the background. But I also don't have a ton of data getting written every second like some of you have. I've also never had consistency problems other than permission issues upon recovery, and that issue is more with the process that recovers (Migration Assistant) the backup rather than the backup itself.