

But alas, it seems that dream will have to wait. So when CloudBerry Lab approached TidBITS to review CloudBerry Backup for macOS and we read its impressive feature set, we were excited about the possibility of discovering a compelling solution for both versioned and offsite backups. As a result, a category of competing apps has arisen, led by Arq, that can both create versioned backups and store them offsite (see “ Roll Your Own Cloud Backups with Arq and B2,” ), obviating the need for an additional Internet-only backup service for offsite backups. For versioned backups, Time Machine is certainly the most well-known and common solution, but it’s far from perfect. A detailed survey of the best of these products and how to assemble them into an overall backup strategy appears in Joe Kissell’s Take Control of Backing Up Your Mac, which also includes an online appendix of tables comparing many other apps.įor bootable duplicates, Carbon Copy Cloner and SuperDuper dominate the Mac world, and ChronoSync can create bootable duplicates in addition to its syncing capabilities. Numerous products have emerged over time to fill these needs. Offsite Backups: copying your data to a place outside your home or office to protect against theft, fire, and flood.Versioned Backups: keeping multiple versions of files as they change in case you need to go back in time.Bootable Duplicates: making an exact, bootable clone of your internal drive so you can get back up and running as quickly as possible in case of drive or computer failure.#1621: Apple Q3 2022 financials, Slack's new free plan restrictions, which OS features do you use?Ī complete backup strategy involves three types of backups, including:.#1622: OS feature survey results, Continuity Camera webcam preview, OWC miniStack STX.#1623: How to turn off YouTube's PiP, use AirPlay to Mac, and securely erase Mac drives.


#1625: Apple's "Far Out" event, the future of FileMaker, free NMUG membership, Quick Note and tags in Notes, Plex suffers data breach.I’ve looked for “ignore file ownership” in the forums but haven’t found anything that helps. Maybe this has nothing to do with my missing file issue but I want to be certain given my dependence upon this kind of “syncing” between machines. If you leave “ignore file ownership” unchecked then, presumably, the permissions for the file are preserved as it is copied to another machine. If you leave “ignore file ownership” checked Chronosync warns you but it’s not clear to me what the risk is. And despite their attempts to help, the tech support staff at Econ Technologies have not been able to enlighten me regarding the difference between leaving the option “ignore file ownership” checked or unchecked on my portable HDD when I run basic left-right syncs. This has been very stable for most of my very short career of DTPro usage.īut recently, after rebuilding my system I encountered an issue that I don’t really grasp, the “ignore file ownership” option on my portable HDD. I’ve always been pretty conservative with my databases, copying them “manually” or using ChronoSync to copy entire databases from one machine to a portable HDD to another machine and then back again. But I’m still confused about how permissions affect DTPro databases and the files therein. I’ve spent a lot of time over the previous 18 months reading and occasionally interacting on the forums, consulting the manual, and becoming more cautious about the way I run MacOS. But I’m concerned that I don’t really know how this happened in the first place. I was able to recover by using one of my external backups created using the Daily Backup Archive script. I’ve been using DTPro for about 18 months now and I’ve just run into my first real problem: I discovered that about 800 files were missing from one of my DTPro databases.
