Technical guide

Backup vs sync on Mac: what protects deleted files?

Sync keeps current files available in more places. Backup preserves recoverable history. Both are useful, but treating synchronization as the only backup can make one unwanted change authoritative everywhere.

Last technically reviewed: July 10, 2026.

Scope and disclosure. Azivault is a backup app, not a bidirectional synchronization tool. This guide favors neither category universally: sync is better for collaboration and access, while backup is designed for independent recovery.

The short version

Sync: propagates current files and changes across devices or locations.
Backup: creates recoverable history with a defined restore path.
Version history: can soften sync mistakes, but remains subject to the provider account, retention window, and product rules.
Use both: sync the working set for access and back it up independently for recovery.

What file synchronization does

Synchronization compares locations and makes their current state converge. That is excellent for opening the same document on a laptop and desktop, sharing a folder, or keeping a working set available across devices.

The same property creates risk: a deletion, destructive edit, rename, or encryption event can propagate. A synchronized second copy may quickly become a second copy of the wrong state.

What backup does

Backup records state that can be recovered later. The destination does not need to look like the current working tree, and it should not treat every source deletion as an instruction to erase all history immediately.

Azivault commits completed runs as restore points in an encrypted repository. Current deletions are represented in later state, while earlier completed runs can still expose the prior file until retention or cleanup intentionally removes that history.

Version history helps but does not remove the distinction

Many sync providers offer trash, version history, or account recovery. Those are valuable safeguards. Check the retention window, excluded file types, plan limits, account recovery, and whether administrators or attackers can delete history.

Independent backup uses a separate repository, service, credential boundary, or storage policy. Its failure modes are less correlated with the sync account that holds the working copy.

Cloud-only placeholders complicate backup

Optimized storage can leave a filename and metadata on the Mac while the provider retains the bytes. Backup software must not mistake a placeholder for an empty file or a deletion.

Azivault compares cloud-only metadata with the previous catalog. New plans default to downloading only new or changed placeholders from the live source, then may re-evict files materialized for that run. Unchanged placeholders reuse prior backed-up content.

Accidental deletion and bad edits

When a sync mistake occurs, pause synchronization before restoring. Otherwise the sync engine may delete or replace the recovered file again. Identify a known-good backup run, restore to a temporary folder, inspect it, and then decide which side becomes authoritative.

Ransomware and compromised accounts

Ransomware can modify accessible working files and mounted shares. Sync may distribute the encrypted versions. Backup history can help only if a clean run exists and the attacker cannot remove every usable recovery point.

Azivault provides encrypted content-addressed repositories, create-if-absent blob storage, and completed-run history, but it does not currently implement provider-enforced object-lock retention. Arq supports immutable backup records on supported storage, preventing alteration or deletion until the provider-enforced retention period ends. Arq is stronger when that independent immutability boundary is a requirement.

One-way copy is not automatically backup

A scheduled copy can be a useful recovery layer when the destination retains old or deleted files. If it simply mirrors current state and deletes destination files to match the source, it has sync-like failure behavior. Read the deletion, overwrite, snapshot, and retention rules rather than relying on the word copy.

A practical combined design

Use iCloud Drive, Dropbox, or another sync tool for access and collaboration. Use Time Machine for fast local history. Add an encrypted offsite backup for important folders when device loss, site loss, or sync-account failure must not remove every recovery path.

FAQs

Is iCloud Drive a backup?

It provides synchronization, storage, and some recovery features, but an independent backup is still valuable because changes and deletions can propagate within the same account.

Does copying a folder count as backup?

Only if the copy provides the history and isolation you need. A mirror that immediately repeats deletions can have the same weakness as sync.

Should I back up folders already in Dropbox or iCloud Drive?

Yes when those files matter enough to need recovery independent of the sync provider and account.

Can Azivault synchronize two folders?

No. Azivault creates backup repository history; it is not a bidirectional sync product.