Sync is not backup.

Sync solves an important job

A good sync system makes the same notes available across devices. Edit a Markdown file on one device and the change appears on another. That speed is useful, and version history can add another valuable recovery option.

The limitation is structural: every device is participating in one current state. A mistaken deletion, a destructive automation, a corrupted file, or an unwanted rewrite can travel through that same path. Version history may help, but it still depends on the provider, account access, retention window, and the scope of what can be recovered.

The question is not whether sync is good. The question is whether the recovery copy can survive the same event that damaged the working copy.

Four tests for a real backup layer

1. Independence

The copy should live outside the same folder and, ideally, outside the same device or provider. A copy inside the active vault is easy for the same sync, script, or cleanup action to reach.

2. Versioning

One mirrored state is not enough when damage is discovered late. Keep multiple restore points so yesterday's known-good state is still available after today's mistake.

3. Inspectability

You should be able to see when the copy was made, what it contains, and whether its archive and file checks pass. A green icon without verifiable facts is reassurance, not evidence.

4. Restorability

A backup is only useful if it can return. Restore it into a new or empty folder, open representative files, compare counts, and keep the original untouched until the result is understood.

A practical stack for a Markdown vault

These layers complement each other:

• Sync: keeps everyday work current across devices.
• Full-Mac backup: protects the wider computer, applications, settings, and other folders.
• Version control or manual exports: provides precise history when you maintain the habit.
• Vault-sized recovery copy: keeps the knowledge base as a portable unit that can be inspected and restored separately.

You do not need to replace a working sync setup. Add a recovery layer whose failure boundary is different, then test it before an emergency.

Where VaultCopy fits

VaultCopy is a narrow local-first layer for Markdown and Obsidian-compatible vaults. The Mac Agent creates a snapshot, the iPhone downloads it over the local network, and the app verifies the archive before saving it. VaultCopy does not host your notes and does not sync edits between devices.

For recovery, the iPhone exports a portable .vaultcopy package. The Mac Agent verifies its manifest, file counts, archive hash, and per-file checksums, then restores only into a new or empty folder. It does not overwrite the active vault in place.

VaultCopy is not a replacement for a full-Mac backup, and it is not affiliated with Obsidian. It is one independent recovery path beside the tools you already use.

• Your backup lives outside the active vault.
• You keep more than one restore point.
• You can inspect integrity and file counts.
• You have restored into a clean folder at least once.