In this chapter, I help you decide which backup software to use for versioned backups and which to use for bootable duplicates. (You might choose the same app for both purposes, but as we’ll see, the best app for one type of backup isn’t necessarily best for the other.)
Time Machine is the backup software built into the Mac starting with OS X 10.5 Leopard. Apple’s goal was to make backups as easy as possible, and compared to anything that came before it, Time Machine is certainly much simpler to set up and use. In some cases, you can set it up and turn it on with a grand total of one click! It’s hard to beat that. Anything that makes backups easier and thereby encourages more people to use them gets a gold star in my book.
However, Time Machine is not ideal for everyone. Before getting into the details about setting up and using it (see Configure and Use Time Machine), I want to tell you what I like and dislike about it, and look at a few situations in which it may be the wrong solution. For those people who need different software, I point you in the right direction with a discussion of features to look for and examples of other versioned backup apps I can recommend.
Without a doubt, Apple got a lot of things right about Time Machine:
The user interface is elegant, if unusual.
I love how I can restore files right in the Finder, and how I can restore missing email messages from within Mail.
I appreciate the fact that my MacBook Pro can back up files using Time Machine even when I’m away from my desk and a Time Machine volume (see Local Snapshots, later in this book).
Time Machine supports encryption for both local and network backups, and also lets me choose multiple destination disks (which it rotates among automatically).
You can back up either to a locally attached hard drive or to any of several kinds of network destinations (including a NAS device, an AirPort Time Capsule, and another Mac)—whatever you find most convenient.
All that is fantastic, and in many respects better than the competition. And yet, having used Time Machine since day one, I find the shine wearing off, for several reasons:
Time Machine’s approach doesn’t scale well to large amounts of data. For one thing, backing up lots of large files takes far longer than it should, because Time Machine always copies entire files rather than using delta encoding as many other backup apps do (see Delta Encoding, ahead). And, even if your Time Machine drive has plenty of storage space, by the time you have several months’ worth of backups the sheer number of files seems to bog down Time Machine and make simple operations unreasonably sluggish.
Although Time Machine is supposed to be almost invisible in ordinary use, it sometimes uses up far too many system resources. If I notice the fan on my wife’s MacBook Pro start to wail, it’s usually because Time Machine happens to be running.
Time Machine is pretty good at restoring individual files and folders from a specific point in time, but it falls down in a number of common usage scenarios. For example, suppose your hard drive dies and you replace it with a bootable duplicate you created last week—and now you want Time Machine to restore only the files that changed since last week. There’s no easy way to do that (see Finding Recently Backed-Up Files).
One of Time Machine’s flashiest features when it was introduced was the capability to restore individual items within apps like iPhoto, Mail, and Contacts (previously called Address Book). Indeed, Time Machine remains the best way I know of to restore individual email messages. Although Apple later added Time Machine support to GarageBand, they inexplicably removed support from iPhoto—and never added it to Photos. Lots of other apps could benefit from in-app restoration (Calendar, in particular, as well as numerous third-party apps), but for whatever reason, Apple has backpedaled on that capability.
Time Machine works best with a directly connected hard drive or a Mac functioning as a Time Machine server (see Use a Mac as a Time Machine Server) but tends to be flakier and slower when backing up to a Time Capsule or other NAS device. And woe betide the person whose Time Capsule malfunctions; repairing or replacing that disk is a pain and a half.
Time Machine has a lot of troubleshooting issues—judging by not only personal experience and anecdotal reports but also, for example, Apple’s pages Time Machine: Troubleshooting backup issues and If you can’t back up or restore your Mac using Time Machine. One particular issue I’ve encountered more than once, and have seen multiple other reports of, is a dialog that tells you Time Machine has encountered a verification error and has therefore stopped making new backups; your only choice is to abandon your existing backup archive and restart your backups from scratch.
As I mentioned in APFS Evolves in Mojave, Time Machine is currently unable to use backup drives formatted with the new APFS file system in High Sierra and later.
Despite these issues, I use Time Machine myself because it offers the fastest and most convenient way to restore individual files. But I also use other software for versioned backups to make up for some of Time Machine’s shortcomings and provide additional flexibility.
So, should you use Time Machine? The biggest question to ask is whether the underlying philosophy of Time Machine works for you. If Time Machine’s design is incompatible with your needs, then you need to choose a different solution for creating versioned backups.
Whether or not you ever encounter the issues I listed previously, Time Machine makes a poor match for these backup needs:
High-volume backups: Because Time Machine lacks file compression, deduplication, and delta encoding features (read Explore Versioned Backup Features, just ahead), backups may require much more storage space than with other software, and as a result may require expensive, high-capacity hard drives.
Backing up many Macs: Time Machine is fine for backing up, say, two or three Macs to a single drive, but the more Macs you back up, the less sense Time Machine makes, because it wastes space with duplicate files and bogs down the host Mac (or other storage device).
Backups to an unsupported NAS: Time Machine doesn’t work with some network-attached storage (NAS) devices as a backup destination. (A NAS is essentially a hard drive with a network interface, which functions as a standalone file server.) Apple’s now-discontinued Time Capsule is a notable exception (as is an AirPort Extreme base station with an external USB hard drive, or “AirPort Disk”), and there are numerous others—but not all NAS devices work with Time Machine.
Backups of Boot Camp and network volumes: Time Machine can back up your startup volume and most other mounted local volumes (such as a second internal hard drive or a secondary partition of your main disk). But to back up Boot Camp partitions or mounted network servers, you’ll need a different app. The same goes for backing up the data on a NAS; see Back Up a NAS.
Fine-grained control: Time Machine offers simplicity at the expense of flexibility. What if you want to exclude from your backup all files that match a certain pattern (disk images, videos, music)? You’d have to add each item individually, or the folders that contain them, to Time Machine’s “Exclude these items from backups” list (see Exclude Files from Time Machine). What if you want to use a different scheme for deleting old backups? Or you want to store some kinds of files in one destination, and other files in another place? These are just a few examples of the kinds of control you give up with Time Machine, but which you could gain, if you need it, with other backup software.
Bootable duplicates: It’s possible to restore an entire disk from a Time Machine backup and then boot from that disk. You can even reboot in macOS Recovery to do this, without having a separate boot volume. But you can’t boot directly from a Time Machine backup in such a way that your apps and data are immediately usable—and it could take hours or even days to restore an entire disk, during which time you won’t be able to do anything else with your Mac. So Time Machine should be considered a companion to a bootable duplicate, not a substitute for one.
If any of the foregoing makes you think Time Machine isn’t right for your needs—or if, like me, you want to use Time Machine but supplement it with other backup software—don’t worry; there are many other options to choose from. I turn next to the features to look for in versioned backup software, and then discuss a few particular apps I can recommend. However, if you’re satisfied with Time Machine, you can skip directly to Choose a Bootable Duplicate App.
I’ve tried more than 100 backup apps, and I’ve read websites and instruction manuals until my brain went numb. Evaluating any given app on its own is hard enough, but comparing them is even more challenging. For one thing, because software developers use terms like incremental, versioned, snapshot, and even backup differently, you may think you’re getting certain capabilities that later turn out to be missing. For another, even when two apps have essentially the same feature, they may implement it in entirely different ways.
In the next several pages, I describe features that may be significant to you in choosing an app to create versioned backups. Also, in the online appendixes, I provide a table that lists the features found in current versions of many backup apps, using my preferred terminology (which may or may not match what a given app’s marketing materials say). You may find it helpful to jot down the features you find particularly important as you read this section and compare your list against the latest version of the tables in the online appendixes.
However, please keep in mind that you don’t necessarily need all these features in your backup software, and that in some cases a combination of two or more apps might serve you best.
In general, backup software doesn’t start copying files immediately when it runs. It must first figure out what to copy—that is, apart from the first full backup, it needs to know which files are new or different since it performed the last incremental update. A backup app typically starts each run by scanning all the folders and files you’ve asked it to back up to determine not only what has changed but also how much space your backup will require and whether your backup will fit on the destination volume.
Some apps take a long time to scan, whereas others use any of several tricks to reduce or eliminate scanning time. Quite a few apps use the FSEvents (file system events) notification system in macOS to determine which files have changed recently, while others run in the background and use their own methods to watch for file changes. Whatever the mechanism, the result is that new or modified files can be copied immediately, and full scans (to identify changes that may have slipped through the cracks somehow) can occur infrequently. Among the backup apps that detect file changes instantly so that they can perform incremental updates without lengthy scans every time are NTI Shadow, Synchronize Pro X, and Time Machine. Some other apps, like SuperDuper!, scan and copy in a single pass for greater efficiency.
The volume from which you back up files is known as the source; the volume to which you back them up is known as the destination (or target). Be sure to select software that can accommodate the sources and destinations you want to use.
All backup apps can copy data from your startup disk, and most can also copy data from other attached hard drives and mounted network volumes. In most cases, your destination options also include any Finder-mountable volume. If you like, you can even back up your files onto a disk image (a special file that functions as a removable disk), although many apps require you to manually create the disk image using Disk Utility and mount it in the Finder before you can use it as a backup destination.
Finally, some backup apps can copy data directly to online storage facilities, such as Amazon S3, a private server, or a proprietary destination (Backblaze, IDrive, and the like). If you want to store a copy of your data online, you may find it convenient to use a single app for both local versioned backups and online backups, assuming you can find one that works with all your preferred destinations.
Among those backup apps that store multiple copies of your files, there’s an important distinction to make: true versioned backups versus rolling backups. In a true versioned backup, every version of every file you designate is saved, but identical files in the same location are never duplicated. In a rolling backup, the app creates a complete, separate copy of all your files each time it runs—basically a non-incremental backup. Then, after a certain number of days or backup runs (specified by the user), the app erases the oldest backup and adds a new one. Rolling backups give you multiple versions of all your files, but because they copy every single file each time they run, they take longer to perform and require more storage space.
Whereas a rolling backup scheme saves a fixed number of complete backups, deleting older ones as newer ones are added, many backup apps offer a more sophisticated way of saving space: they prune (or erase) older files or snapshots from versioned backups when certain conditions are met. For example, an app might let you choose the maximum number of copies of any given file to save; once you reach that limit, it prunes the oldest one to make space for newer ones. Or it may go by age—extra versions older than, say, 30 days are deleted automatically to make space for newly backed-up files.
Time Machine does its own sort of pruning: it keeps hourly backups for 24 hours, daily backups for a week, and weekly backups until it runs out of space. That means almost every time it runs, it purges at least some older files. And when your backup disk is almost full, it deletes further files to ensure that, if possible, you always have at least a day’s worth of hourly backups and a week’s worth of daily backups—even if you’re seriously low on disk space.
Without a pruning feature, you could get stuck when your backup media runs out of space: you’d have to migrate your backups to a larger drive or manually erase backed-up files to make room for new ones. So pruning can be a valuable feature, but use it with caution; you don’t want to erase files you might need to recover later. All things being equal, I prefer to have a choice as to whether and when pruning should occur. So, especially when you’re considering an online storage provider for your backups, pay attention to the flip side of pruning—data retention. That is, be sure you know how long the service retains old versions and deleted files, and whether you can adjust the retention period.
To oversimplify somewhat, most software employs one of two basic methods to copy files when performing a backup. One way is to copy each file in a standalone Finder-readable format, so that the backed-up files look and act exactly like the originals. Another way is to copy all the files into a single, larger file (sometimes called an archive file or a backup set). Each approach has advantages and disadvantages.
Finder-format copies can be restored without backup software; just drag and drop or copy and paste. Some people feel more secure knowing they can get at their files easily even if their backup software isn’t working or the developer goes out of business. Generally, each version of each backed-up file takes up exactly as much space as the original. (Time Machine, Personal Backup, and Mac Backup Guru store Finder-readable files but avoid using extra space for identical duplicates, thanks to a Unix trick; see the sidebar The Magic of Hard Links.)
Archive files, on the other hand, can be compressed as they’re stored, potentially saving a large amount of disk space. Of course, you’ll need the backup software to restore files, and you could have a slightly higher risk of data loss due to file corruption (since all the data is stored in a single file)—but most backup software has verification mechanisms to compensate for this.
Some backup software stores backups in disk images. Like archive files, disk images can thus contain many files and folders—and can optionally be compressed. But their contents are also Finder-readable.
For making a bootable duplicate, Finder-readable copies are obviously mandatory. For versioned backups, I consider Finder-readable files optional; the benefits of compression, along with delta encoding and deduplication (discussed ahead), that you can often get with proprietary archive files may outweigh the slight inconvenience of having to use backup software to restore your data. (Indeed, as I point out in Ease of Restoration, a backup app’s Restore feature may turn out to be easier than using the Finder.)
If there’s any chance at all that your backup drive could be lost, stolen, or otherwise accessible to an unauthorized person, you’ll be smart to encrypt its contents.
Some backup apps have built-in encryption features. You see this most often when an app stores backups in proprietary archive files; the archive itself is encrypted.
Encrypting Finder-format copies usually means encrypting the whole volume (using Disk Utility or a third-party tool). The same goes for disk images: they can be encrypted, which protects everything inside them. The contents of the encrypted volume (or disk image) will be protected only when it’s unmounted.
If you need an encrypted bootable duplicate, you can use either full-disk encryption software such as FileVault (which is built into macOS) or a hardware-encrypted drive, both of which I cover in the sidebar just ahead.
However, note that if you have a newer Mac with a T2 chip (see full list here), it can’t boot from an encrypted duplicate if that duplicate is formatted as HFS Plus (refer back to T2 Chips Change the Backup Rules). So you must either forgo encryption on your bootable duplicates or format the destination volume as AFPS, create the duplicate, boot from the duplicate, and enable FileVault.
In years past, almost all Mac backup software performed versioned backups on a file-by-file basis during incremental updates. In other words, if just 10 bytes of a 10 GB file change, that marks the file as modified, and thus the whole file must be copied on the next backup run. Increasingly, however, Mac backup tools (such as Backblaze, QRecall, Retrospect, and even macOS’s Versions feature; see Version Control) have a capability called delta encoding, which you may also hear referred to by numerous other terms. By whatever name, it means that the software copies only the changed portions of files.
In some cases, the software copies only the individual bytes that have changed since the last backup, and in other cases it copies larger units called blocks (a block being a unit of storage typically equal to 4096 bytes—4K—on modern Macs). So, you’ll sometimes see this feature referred to as block-level (or byte-level) incremental updates or words to that effect. With backup apps that use byte-level or block-level delta encoding, if only 10 bytes of a file change, only those 10 bytes, or the block(s) containing those 10 bytes, are added to the backup—a tiny amount of data.
The advantage of such an approach is that backups go much faster after the initial run and take up far less storage space. This is particularly important when backing up over the internet. The disadvantage is that restoring a file requires the backup software to reconstruct it by putting together the pieces from all its incremental backups. If even a single one of those incremental bits were to become damaged or lost, you might be unable to restore the file. However, backup software typically performs ongoing verification to ensure that all the necessary bits are present, alerting you or recopying data if any pieces should go missing or become corrupted.
You might have two or more identical copies of a certain file on your disk. Some backup software notices this and puts only one copy in your backup (along with a record that the file appears in multiple places). That way, you save storage space and speed up your backups considerably. Taking this concept further, many backup apps can look within files for portions of files that are identical to portions of other files and—thanks to delta encoding—copy only the unique parts of the additional files. This process of preventing duplicate data (at any level) from cluttering up your backups is called deduplication. Deduplication applies only to versioned backups, not to duplicates (you can see the contradiction in the name!) and is extremely useful.
Almost every online backup app offers deduplication, which is great when you’re paying by the gigabyte or trying to push data over a slow internet connection. The result sometimes seems impossible: how did hundreds of megabytes of data just upload in a few seconds? That’s deduplication magic at work. QRecall and Retrospect are among the desktop backup apps that can also prevent duplicate data from appearing in your backups—even, in some cases, from multiple computers.
Versioned backups may not include every file on your disk. If storage space is at a premium or if you want to save time on network backups, you might choose to include only part of your data in versioned backups (while putting all of it in your bootable duplicates). You can almost always do this manually, by selecting one or more specific files or folders to include or exclude. But some backup apps go further, letting you create patterns indicating which files or folders should be included (selectors) or excluded (exclusions) from a particular folder or volume based on items’ names, sizes, Finder labels, extensions, modification dates, and other factors. For example, you might want to include all Microsoft Word (.doc
or .docx
) files, regardless of their location, or exclude all files over 2 GB, even if they’re in a folder that is otherwise backed up.
When it comes time to restore files from a versioned backup, you must be able to locate the versions you’re looking for easily. Some backup apps facilitate such restorations by offering snapshots—lists of all the files being backed up as they existed at the time of each backup. Even though a certain file may not have been copied during a particular backup run (because it hadn’t changed since the previous backup), it will appear in the snapshot. You can typically restore all the files in a given snapshot, or delete a given snapshot, in a single operation.
One way of creating snapshots without relying on a separate catalog or file list is to use a Unix feature called a hard link (see the sidebar The Magic of Hard Links), which gives the appearance of a file or folder existing in more than one place even though only one copy is taking up any real space. When backup software creates hard links to all the files or folders it didn’t copy in their entirety on a given run, you get a versioned backup that essentially functions as its own snapshot. Time Machine, Personal Backup, and Mac Backup Guru use this approach.
Although snapshots are extremely useful, you may want to access your backed-up files in other ways too. Some backup software uses a hierarchical file list that shows you every file and folder you’ve backed up—and then, for each file, every version it’s stored over time. Depending on your needs, this arrangement—starting from the file in question rather than a particular backup run—may be preferable. Time Machine has an elegant hybrid approach, letting you zoom forward or backward in time to see how any given folder appeared at the time of each snapshot.
Without either a snapshot or a file list, you’ll need to locate each version of the file manually—often in a series of time- and date-stamped folders. This makes for a long and tedious restoration process, which brings me to…
No matter how easy it is to back up your disk, if your software makes it difficult to restore files, you’re going to be unhappy with it. After all, a backup that you can’t restore is worthless. Backup apps typically offer one of three main approaches to restoration:
A Restore command: The backup app (usually) tracks all the files you backed up during each session, allowing you to copy them back to their proper locations—or another destination of your choice—with a few clicks. In most cases, before starting the restoration, you can choose a subset of the files, or even pick out one version of a single file if that’s all you need. Restore commands and snapshots tend to appear together.
Finder restoration: The backup app has no Restore command; to restore files, you manually drag them (or copy and paste them) from the backup volume onto the original disk. This is fine for restoring an occasional file or folder if it’s in a convenient place, but if you’ve done a versioned backup, you may have to sort through dozens or hundreds of folders to locate the right version of each of your files.
Reverse backup: In this scheme, the backup app once again lacks a Restore command; instead, it expects that you’ll swap the source and destination locations and perform your backup again—in reverse. While this may reduce manual effort somewhat, it’s still a hassle when restoring files from a versioned backup (except, perhaps, in the case of apps that use hard links), especially when restoring from multiple locations.
I prefer apps with a Restore command; they usually make the restoration easier. Of course, the presence of a Restore feature does not, by itself, mean the process will be easy (for example, some products have a Restore command that operates only at the level of individual files), but it’s a hopeful sign.
If you’re performing a full (rather than selective) versioned backup, bear in mind that not all backup software can restore your backup from an arbitrary point onto a blank disk in such a way that the resulting volume will be bootable. For a full versioned backup to be bootable upon restoration, several things must be true:
All files needed for your Mac to start up—including many hidden files—must be included in the backup and restored later.
The backup software must preserve Unix ownership, permissions, and symbolic links during the backup and restoration processes. (This feature requires you to enter an administrator password.)
When restoring the files, the destination disk must not contain any extraneous files that could interfere with booting. Normally, this implies erasing the disk before restoring the backup.
Time Machine, along with Retrospect and most other backup apps that offer both duplication and versioned backup features, can restore a full versioned backup as a bootable volume, assuming that you set it up properly.
But there’s another approach to mixing versioning and bootable volumes, which I cover next.
Most backup apps that offer both versioning and bootable duplicates treat these two approaches as distinct modes, with the expectation that any given backup disk will hold one sort of backup or the other. But rather than storing two separate backups, wouldn’t it be nice if a single backup could be bootable and have the added bonus of containing multiple versions of all your files?
As a matter of fact, you can do this with several backup apps. But even though that may sound like the best of both worlds, it might not be what you’re looking for.
Here’s how such a scheme typically works. An app starts by making a bootable duplicate in the usual way (copying all files and attributes to give you an exact copy). On the next and subsequent runs, new and modified files are copied to their respective locations on the duplicate; however, deleted files and older versions, instead of being deleted from the duplicate, are moved to a special location on the backup disk—usually time- and date-stamped folders within an Archive or Safety Net folder—that won’t interfere with booting.
That’s nifty, no doubt about it. But in the apps I’ve seen that create bootable duplicates with versioning, the archive of older versions and deleted files is awkward to navigate and restore files from. It’s merely a series of folders—perhaps hundreds or thousands of them—in the Finder. And there’s usually no Restore feature to help you locate and retrieve those older files.
Plus, even though the versioned files are stored in a location that shouldn’t interfere with booting, the fact that you’re not making an exact duplicate introduces a variable that could potentially complicate troubleshooting. (There’s also the minor issue that if you create a bootable duplicate that includes versioned copies of your files and you later restore the duplicate to a blank disk, you’ll want to exclude the archive folder in order to avoid duplicated files.)
For all these reasons—but mainly the awkwardness of restoring versioned files—I don’t recommend using a versioned bootable backup as a substitute for a conventional versioned backup. As a supplement to a conventional versioned backup, however—or as a substitute for a conventional bootable duplicate—I can’t object. If you’re creating versioned backups and bootable duplicates already, the additional safety net of versioned bootable duplicates can’t hurt.
Here are three apps I know of that offer bootable duplicates with optional versioning as I just described:
Carbon Copy Cloner: My favorite app for bootable duplicates, Carbon Copy Cloner also offers a SafetyNet feature that stores old versions and deleted files. (See also Create a Duplicate with Carbon Copy Cloner.)
ChronoSync: An all-purpose syncing and backup app, ChronoSync can archive changed and/or deleted files on the destination, whether or not you’re creating a bootable duplicate. (See also ChronoSync Tips.)
Déjà Vu: The optional Safety Net setting in this backup app lets you store a user-selected number of archives of changed and deleted files in the destination folder of your choice.
Even if a backup app doesn’t offer a prebuilt “bootable duplicate with archived versions” option, you might be able to achieve the same effect with another app, by specifying the same destination volume for both bootable duplicates and versioned backups (with the versions stored in a folder at the top level of your backup disk). But because “bootable duplicate” normally means deleting anything on the destination that isn’t on the source, these two backup operations might conflict with each other.
A backup app called Mac Backup Guru lets you combine a bootable duplicate (which it calls a Synchronized Clone Backup) with a versioned backup (or Backup with Incremental Snapshots). Like Time Machine, this app creates hard links (see The Magic of Hard Links) to any files that are unchanged during a given backup run but creates complete copies of files that are new or different, and stores them all in date- and time-stamped subfolders of an Incremental Snapshots folder. The result is that the combination of bootable duplicate and versioned backup uses less disk space than the apps I listed just above, but restoring individual files is still awkward and Mac Backup Guru offers no automated Versioned Backup Pruning of older backed-up files.
In addition to ease of restoration, an app’s overall ease of use is important. The interface should be self-explanatory—ideally, clear enough that you can figure out how to perform a basic backup and restoration without looking at a manual. (Time Machine stands out in this regard as being exceptionally easy to use, because it builds on the existing interface of the Finder rather than displaying your files in a completely different context. The downside, though, is that it’s impossible to restore files from multiple locations at the same time.) After initial setup, the best backup software is virtually invisible, working silently behind the scenes until you need it.
The backup software included in the online appendixes ranges in price from free to about $120 (before discounts). The price does not necessarily correlate to capabilities, but I urge you not to skimp when it comes to backup software; buy the solutions(s) that fit your particular scenario the best. Over the life of your data, the right backup software will surely pay for itself.
If Time Machine isn’t right for you—or if, like me, you want to supplement it with a more robust and flexible option—you’ll need to pick a different app for creating versioned backups, keeping in mind the features I’ve described in Explore Versioned Backup Features, just previously.
I’ve tested oodles of apps that can create versioned backups (as well as many Mac backup apps that can’t), and I’ve included a reasonably detailed feature comparison chart in the online appendixes. Please feel free to peruse that at your leisure, download demo versions, try them out, and draw your own conclusions.
But if you want my professional advice, I suggest choosing from among just a few that stand out for one reason or another.
Arq is an unusual backup app designed to work primarily with cloud storage from providers such as Amazon (Amazon Drive, S3, or Glacier), Backblaze B2, Dropbox, Google Cloud Storage, Microsoft OneDrive, and Wasabi, although it can also back up to SFTP servers, NAS devices, and other local and network locations. Arq supports versioning, encryption, and file-level deduplication, and it faithfully backs up and restores all Mac metadata (such as file ownership and permissions, access control lists, extended attributes, Finder tags, and aliases)—a rare capability among online backup tools. On the downside, it backs up only on a fixed schedule (with a maximum frequency of once per hour). For more information, see Arq Tips.
As the name suggests, ChronoSync is an app designed mainly for synchronization. For years, it’s been one of my favorite tools for syncing folders between my Macs. But it’s also a powerful backup tool that can create not only versioned backups but also bootable duplicates (including versioned bootable duplicates!). It can also store backups on Amazon S3 or Google Cloud servers (with more cloud destinations in the works). Thanks to an add-on app called ChronoAgent, it has even joined the rarefied ranks of apps that can create bootable duplicates over a network. See ChronoSync Tips for additional usage hints.
DollyDrive started out as a way to store Time Machine backups in the cloud. But in just a few years, this Mac-only product has morphed into a full-blown versioned backup, syncing, and sharing service that doesn’t require Time Machine. DollyDrive still offers cloud storage, but you can also use its software to store versioned backups—or even bootable duplicates—on a local hard drive. You can get a free 14-day trial that lets you store up to 100 GB of data. Monthly costs for unlimited Macs range from $5 for 500 GB of data to $25 for 2 TB, but there’s also a plan for unlimited storage from a single Mac for $6 per month, and discounts apply for one- and two-year subscriptions. Read DollyDrive Tips for additional information.
QRecall can save space by deduplicating files from more than one computer. It offers encryption, compression, and delta encoding, so that large files need not be entirely duplicated every time they change. QRecall works with external hard drives and network volumes, and it has a long list of clever, useful features. However, it can’t make bootable duplicates, and it has a peculiar interface that introduces several unusual terms (such as capture, recall, layer, and timeline) that force you to think about backups in unfamiliar ways. I help you make sense of these in QRecall Tips.
When I started writing books about backups more than 15 years ago, Retrospect was my favorite backup app, and I recommended it unreservedly. But as time wore on and impressive competitors appeared—Time Machine, Backblaze, ChronoSync, and dozens of others—Retrospect’s status became more dubious as it stuck with an “old-school” approach to backups and an outdated interface. In recent years, however, Retrospect has enjoyed a comeback. It now has a much-improved interface; it also supports cloud storage destinations (such as Amazon S3, Backblaze B2, Google Cloud Storage, and Wasabi) and delta encoding (which Retrospect refers to as block-level incremental backups). I offer suggestions for using it in Retrospect Tips.
My main complaint was that Retrospect was more complex and expensive than most individual users would prefer, but then its target audience was business users with multiple computers (whether a few or thousands) to back up—and support personnel with enough technical expertise that they wouldn’t be bothered by a bit of fiddling.
But that changed in 2018 with the release of Retrospect Solo, a new version of the app without some of the bells and whistles only a network administrator would want, and with the consumer-friendly price of $49. Retrospect Solo can do just about any sort of backup an individual Mac user might want, except back up to or from a NAS.
Retrospect Desktop, the next step up, can handle NAS devices just fine. It excels at client-server network backups (for both Macs and Windows PCs), for both small groups and large organizations. It can combine multiple hard disks into a single logical backup device—no need for a RAID. It’s one of very few Mac backup apps that can create a bootable duplicate over a network (the others being Carbon Copy Cloner and ChronoSync). It also has good support for tape drives, magneto-optical drives, and other storage media that are common in large businesses. One copy of Retrospect Desktop includes five licenses for Retrospect Client—meaning it can back up the Mac it’s installed on plus up to five other computers. (Retrospect also makes editions of the app suitable for larger installations).
I’ve already mentioned several apps that can create bootable duplicates, including ChronoSync, Data Backup, Déjà Vu, DollyDrive, Retrospect, and SmartBackup. All these apps get the job done, and if you happen to like one of them for any reason, I won’t try to talk you out of it. However, I do want to call your attention to two apps that specialize in bootable duplicates and do an impressive job with extra features you may appreciate:
Carbon Copy Cloner is my favorite tool for bootable duplicates. It can back up and restore hidden Recovery HD volumes, create a bootable duplicate over a network, and archive old file versions and deleted files (although not, admittedly, in the most convenient way).
SuperDuper! includes a Sandbox feature that lets you make a special duplicate in which some key folders are linked, rather than copied, to the destination. The result is that, as long as you keep both the backup drive and the original mounted, you can install software or modify documents on either one, and the changes are reflected on both.
I discuss these special features further and offer more advice about choosing an app for bootable duplicates in my Macworld article Drive-cloning utilities: The best Mac apps for making a bootable backup. And I provide instructions for using them later in this book; see Create and Use a Bootable Duplicate.
18.117.137.117