If you’ve decided to create versioned backups using an app other than (or in addition to) Time Machine, set that up now. I wish I could give you step-by-step instructions for using each one of those apps, but that would take too many pages (and you can read the app’s documentation for help). Instead, I want to give you a few tips for each of several good choices, all of which I mentioned back in Choose Another Versioned Backup App. Although I’ve used and can recommend each of the apps I mention here, I don’t pretend that this is an exhaustive list. There are many other excellent options, and you can read about them in the online appendixes.
Later in the chapter, I also give several general pointers about things like power management and testing versioned backups.
Arq is an increasingly popular choice for people who want the benefits of cloud storage but also want greater control over their data than cloud backup providers offer—and the freedom to choose inexpensive cloud storage. If you use Arq for your versioned backups (or are considering doing so), keep the following in mind:
All cloud storage is not created equal. Arq supports lots of different cloud storage providers, some of which are so inexpensive that they seem almost too good to be true. As I point out later, in BYOS (Bring Your Own Software) Internet Backups, some cloud storage services limit your upload rate—perhaps only after you’ve transferred a given amount of data or number of files in a certain month. The result can be that backups are disappointingly slow. So read your provider’s fine print and try some speed tests with a few gigabytes of data before you start to upload files by the millions.
Backups run on fixed schedules. Compared to, say, Backblaze, which backs up your data continuously, Arq can run any given backup no more often than once per hour. So, if you’re moving to Arq from a competitor that backs up files as often as you save them, you might need to adapt your thinking and behavior, because Arq won’t make such frequent copies. (In addition, running less frequently means each backup is likely to take longer.) You can, however, work around this somewhat by setting up multiple backups to the same destination; make them identical except for the time. (For example, make the first one hourly on the hour and the second one hourly on the half hour.)
Mind your settings. Arq helps you avoid unexpected expenses by letting you set a budget (the maximum amount of storage space your backups can occupy on any given cloud service), but this feature is disabled by default—and even when it’s on, your budget is enforced only at an interval you set (such as every 30 days). So review the settings carefully for each destination and make sure you’re taking advantage of Arq’s money-saving features.
Arq supports local backups too. Although Arq is best known as a backup app to be used with cloud destinations, you can also choose local hard drives, network volumes, or NAS devices as destinations. That makes it much more versatile than most cloud backup apps and lets you use the same app for both local and cloud-based versioned backups. Alas, Arq lacks the capability to make bootable duplicates, so you’ll still need a separate app for that.
If you’ve selected ChronoSync for versioned backups, please do the following:
Put synchronizers in containers. ChronoSync is designed around the concept of documents called synchronizers, which contain the instructions for backing up or synchronizing something.
When you set up a backup or sync operation, you’re creating a synchronizer, which the app prompts you to save when you close the window or quit the app. Although ChronoSync gives you a wealth of options for each synchronizer, one fundamental limitation is that a synchronizer can apply to only a single volume or folder (and everything inside it). If you want to back up items from more than one location (perhaps even with different options) in a single operation, create one synchronizer for each folder or volume, save them individually, and then choose File > New > Container and add each synchronizer to the list. You can then run all the synchronizers in one pass, and even schedule the entire container to run at a predetermined time.
Take the easy way out. ChronoSync is amazingly flexible, but the flip side of that flexibility is a somewhat complex user interface; for example, you have to choose one of 11 backup or sync operations for each synchronizer, but the names and functions of these operations are far from self-explanatory. But I have good news! In a recent update, ChronoSync added a Setup Assistant, which walks you through each step of the process and creates the synchronizer you need without overwhelming you with technical terminology. To use this tool, just click the “Use a setup assistant” button in the main ChronoSync Organizer window.
Look for new destinations. ChronoSync can now back up to Amazon S3, Backblaze B2, Google Cloud Storage, and SFTP servers, and support for more cloud destinations is reportedly in the works. Although ChronoSync can’t yet work with as many cloud destinations as Arq can, it’s moving in that direction.
Dissect away. ChronoSync can optionally look inside a package (a special folder that acts like a file) when performing a sync, so that if just some of the contents have changed, only those items are copied. This is crucial for things like your Photos library, because without using this feature, the entire library must be copied if even a single photo is added or changed. For reasons that are unclear to me, this feature is turned off by default, and you must re-enable it manually whenever you create a new synchronizer. To do so, click Options, choose Custom from the pop-up menu under Special File/Folder Handling, and choose Dissect from the “Package handling” pop-up menu.
Use archives for versioned backups. To create a synchronizer that produces versioned backups, choose Backup (either Left-to-Right or Right-to-Left, depending on your setup) from the Operation pop-up menu and check the “Archive replaced files” box. Then click Options, and in the Archive Handling section, select the options you want (such as how many copies of each file to keep and when to purge older versions). (If you used Setup Assistant, as I recommended above, you may not need to do this manually, but it may be useful to know what’s happening behind the scenes.)
Get a good agent. ChronoSync, by itself, can back up the Mac it’s on, and it can optionally use mounted network volumes as the source or destination. However, to back up to or from another Mac on your network with administrative privileges, keeping ownership and permissions intact—crucial for, among other things, creating a bootable duplicate over the network—you must install the add-on app ChronoAgent on the other Mac.
If DollyDrive is your preferred tool, consider these things:
Local and remote: DollyDrive is best known for its online storage, but its software can (like Arq and ChronoSync) also back up your data to a local hard drive. As I’ve said elsewhere in this book, I’m a big believer in having both local and offsite backups, and DollyDrive can cover both needs.
Cloned like Dolly: In addition to creating versioned backups, the DollyDrive software can store a bootable duplicate on an external drive using its Clone feature.
Sync and share too: DollyDrive isn’t just for backups; it can also enable multiple Macs and iOS devices to sync files with each other via the cloud and share files with other people, in much the same way as Dropbox.
In short, DollyDrive is the complete package—the only tool I know of that offers versioned local and online backups, bootable duplicates, cloud syncing, and file sharing in a single piece of software. (That doesn’t necessarily mean it’s the best tool for each of those jobs—for example, at the moment, the most frequent backup interval is hourly—but it’s nice to have so many capabilities rolled into a single package.)
If you use QRecall for versioned backups, I suggest the following:
Learn the lingo. QRecall has its own special vocabulary. You may find the app easier to use if you translate its jargon into more familiar words. When you see capture, just think “store a versioned backup.” (QRecall uses archive to mean a special file in which versioned backups are stored.) When you see recall, think “restore,” and when you see restore, think “restore to the original location.” A layer is essentially a snapshot that contains only the items copied during a particular incremental update of a versioned backup. You can merge (combine) layers for convenience; you can also do a rolling merge, in which layers are combined according to your specifications after a certain number of days.
Let the Assistant help. To get help setting up complex options in QRecall, Choose Help > Capture Assistant.
Use multiple keys to save space. Although you can use a single QRecall license key on multiple computers, doing so means each computer must store its data in a separate archive. If you purchase an individual license for each Mac, they can all share a single archive—significantly reducing the overall size of the backup, because QRecall doesn’t store any duplicated data.
If Retrospect is your weapon of choice, consider these tips:
Get the right edition. If you’re backing up a single Mac (whether to one or more external hard drives, to the cloud, or both), you now want Retrospect Solo. If you want to back up multiple Macs over your network to shared storage—or if you want to back up to or from a NAS—you’ll need Retrospect Desktop. But note that the same software is used for all editions; the license you enter determines which features are enabled.
Understand the terminology. Retrospect has always had a somewhat odd way of referring to certain activities, and starting with version 8.x—it’s at 15.6 as of publication time—quite a few terms changed (some for the better, others not so much). On the plus side, what older versions called selectors (which could either include or exclude files) are now called rules, and the ambiguously named Backup Server feature is now called Proactive Backup. However, what was formerly duplicate (namely, the operation you choose if you want a bootable duplicate) is now the less-specific copy, while scripts—specifications for backup operations—keep the same name, even though they don’t resemble what the rest of the world calls scripts (procedures written in a language such as AppleScript).
Parts is parts. Even if you use the app only to back up a single Mac, you must install and configure both Retrospect Engine (which does the work of copying the files, and is turned on and off via System Preferences > RetrospectServer) and the Retrospect app itself (sometimes referred to as Retrospect Console), which lets you configure and control backups. The first thing you must do after running Retrospect is to tell it where to find the engine you want to work with—which, in the case of the one running on the same Mac as the console, is at the address 127.0.0.1
.
When your first full versioned backup is complete, test it by choosing a few random files or folders to restore. If your backup software has a Restore feature, use it; if not, you’ll have to restore the files manually (usually with drag-and-drop).
To test your backup, follow these steps:
Restore to a different location. Most backup software lets you restore files either to their original locations or to another location of your choice. For this test, restore your selected files to a different location—say, your desktop, where you can find them easily.
Check the restored files. Compare the restored files to the originals using the Finder’s File > Get Info command. Each pair of files should match exactly: same name, size, icon, creation date, and modification date. You should also confirm that the files open correctly. If the files were not copied, were not identical, or didn’t open, then either your backup software or its user made a mistake! Check your software’s documentation, and if necessary contact the developer’s technical support department for assistance.
Try an in-place restoration. Temporarily move one of the original files you backed up to a different location (again, your desktop works well for this), then use your app’s Restore feature (if it has one) to restore the file to its original location.
Check the restored files. Again, check each file carefully to make sure it’s correct.
If the files are correct regardless of the location to which you restored them, your versioned backup is working properly.
18.216.244.98