Azivault

Technical guide

How to back up a Mac to the cloud

Cloud backup keeps a recoverable copy away from the Mac, but the phrase covers two different products: a managed backup service with storage included, or backup software that writes an encrypted repository to storage you control.

Last technically reviewed: July 10, 2026.

Scope and disclosure. Azivault is Mac backup software and supports S3-compatible cloud storage. This guide also explains when a managed service such as Backblaze or a broader storage client such as Arq is the better choice.

Quick recommendation

Cloud backup is not the same as cloud sync

iCloud Drive, Dropbox, and similar products keep a working set available across devices. Their normal job is synchronization: when a file changes or disappears, that state can propagate. Version history may help, but it remains part of the same account and synchronization system.

A backup needs a recovery point that does not simply mirror the current state. It might be a version held by a managed service, a completed repository run, or an immutable snapshot. The practical test is simple: after a file is deleted or overwritten, can you still recover the earlier contents?

Choose managed storage or bring your own

Backblaze Computer Backup is the managed-service shape: install the client, subscribe, and let Backblaze supply remote storage and an account-based restore workflow. This minimizes bucket, region, endpoint, and storage-billing decisions.

Arq and Azivault separate software from storage. You choose a provider and retain that provider relationship. Arq supports a much broader set of destinations and mature retention controls. Azivault supports local and network folders plus S3-compatible object storage, using the same portable encrypted repository format across them.

Decide which Mac data belongs offsite

Start with folders whose contents cannot simply be reinstalled or downloaded again: active work, documents, source material, financial exports, writing, family archives, and original media. A smaller reliable offsite plan can be more useful than a whole-disk plan that never completes.

Understand cloud-only source files

macOS file providers can leave placeholders whose metadata exists locally while the content remains remote. A filesystem clone or snapshot can preserve the placeholder without downloading its bytes, so backup software must handle that state deliberately.

For new Azivault plans, the default is to download a cloud-only file only when catalog metadata indicates that it is new or changed. Unchanged files reuse their previous repository object without a download. Materialized files are read from the live source path and may be re-evicted afterward. A provider process may be unable to download content while the Mac is sitting at the login window.

Encryption and key custody matter

Transport encryption protects bytes in motion, but it does not answer who can read the stored backup. Check whether the provider holds the encryption keys, whether metadata and filenames are protected, and what happens when a password is lost.

Azivault encrypts supported repository contents and path metadata before storage. Recovery depends on the repository key available through Keychain or the recovery password saved when the plan was created. If you lose every unlock route, the repository is unreadable. There is no provider reset for client-side encryption.

Model cost before the first large upload

A managed service commonly charges per computer or plan. Object storage commonly charges for stored capacity, requests, retrieval, and sometimes egress. Low storage pricing can still produce an expensive emergency restore if retrieval terms are ignored.

Estimate the initial dataset, monthly change rate, retention, request volume, and cost of downloading the full recovery set. Provider lifecycle rules must not delete repository objects independently of the backup application’s format and retention contract.

Test recovery from another Mac

A cloud upload is not a finished backup plan. Restore a small file, then document how a replacement Mac would authenticate to the provider, obtain the repository, unlock it, and verify it.

Azivault can browse completed runs through Finder when its local repository or cache is available. For independent recovery, the azi CLI can hydrate an S3-compatible repository to local storage, verify it, search completed runs, and restore or export selected content.

A practical Mac cloud-backup design

Use Time Machine or another local system for fast nearby recovery. Add one cloud path whose account and credentials survive loss of the Mac. Run both automatically, keep recovery material separate, and perform a restore drill after configuration changes.

FAQs

Can Time Machine back up directly to cloud object storage?

No. Time Machine supports attached storage and compatible network destinations, not general S3-compatible buckets.

Is iCloud Drive a Mac backup?

It is primarily synchronization and cloud storage. Keep an independent backup for recovery from propagated deletion, account loss, or unwanted changes.

Does Azivault include cloud storage?

No. You provide the folder, network, or S3-compatible destination and pay that storage provider separately.

Should I keep Time Machine after adding cloud backup?

Usually yes. Local restore is faster, while cloud backup protects against failures that affect the Mac and nearby storage together.