I have a nightly clone on my desktop computer, and a weekly one for my laptop.The code works and uploads images to Backblaze but it's not waiting for the for loop to finish running and the query to finish before calling next. These all offer “smart” updates, so that only files that need to be replaced or deleted on the clone are modified each time it runs. With external drives so inexpensive, add one that uses one of the packages mentioned earlier that can clone the contents of your startup drive. The files & DB are stored in your cloud storage app Amazon S3, Wasabi, Backblaze, Dropbox or Google Drive.

It’s also great for migrating from one Mac to another. Time Machine works best in my experience and opinion as an archive-retrieving older or deleted versions of individual files or the contents of folders-than for restoring a drive. That’s not as secure as we thought-or at another location to which you have regular access.Īdd a clone to your mix. Put one in safe-deposit box-though the New York Times warns macOS can automatically back up to multiple Time Machine destinations if they’re connected at once, but it will also catch up destinations that you plug back in after they’re removed. That can avoid you worrying about the drive being stolen or examined when you’re not around. I recommend using disk encryption for backup drives (Control-click the drive and choose the Encryption item), because at rest a macOS-encrypted volume is extremely secure. You can wind up with a compounded problem: If your Time Machine volume contains other data besides the Time Machine container, some of the cloud archiving services won’t back up that non-Time Machine data! (This column was prompted by a reader who hit that issue with Backblaze.) If you have caps or throttles on your broadband data upload, Time Machine backups can easily push you over, too, for this reason. However, CrashPlan’s archive grew to 303.5GB. Over a week, that Mac’s Time Machine backup reached 63GB. (This also makes it difficult to copy a Time Machine backup from one volume to another without bloating the size.)Ĭode42 tested how quickly Time Machine archives grew with a 53GB volume on a Mac. If you back up files from that volume using file-based archiving software, hard links are copied each time they appear. It’s clever, but it only works within a single volume. These hard links can appear multiple times in a volume, but all refer to a single file. That omits making a fresh copy of any file that remains the same between those bakcups. The primary issue is that Time Machine uses a special kind of alias, called a hard link, to create complete snapshots for each point in time that a backup operation happens.

The issue with Time Machine and onlne backup

Backblaze timemachine