I use TM on my Mac but that's not my 'main' backup schema. I have a product (ChronoSync) that does a full backup daily and automatically where the entire drive(s) are cloned. And I backup to the cloud using Backblaze. I rarely need to go into TM, it can be useful for iterations it keeps (like if I want to go back 5 versions of a document). On my Mac, TM dedicated drive is always mounted and TM just 'does its thing' as it sees fit.
Pretty much what I do—and, actually, quite similar to the regime I had the technicians working for me implement when I was responsible for preserving the digital information assets of a government agency:
- Perform incremental back-ups on a frequent basis. (Time Machine's hourly back-ups are optimal* in a home computing environment.)
- Perform full back-ups to a different storage medium at least once a day and whenever you make a major configuration change.
- Regularly store full back-ups offsite (e.g., in the "cloud") as a hedge against a catastrophic facility incident.
My formula for data protection is based on the premises that any hardware platform used for preservation may fail at any time; that you should always assume any software product, including back-up software, is harboring at least one bug that will someday cause an unrecoverable loss; and that lightning
can strike twice in the same place.
———
*Although I also back-up recently-imported raw image files once a minute while I am performing initial culling and post-processing until they are moved to a permanent repository, using custom scripts I wrote, just in case my fat fingers delete some pictures prematurely.