Skip to main content

📝 Lesson 7.2: Sync, Backup & Version Control (Sync + Git)

Your vault now holds real work — tasks, projects, months of thinking. Which means one dead hard drive, one bad sync, or one fat-fingered "delete folder" could erase it. This lesson makes sure that never happens. We'll untangle the two ideas people constantly confuse — sync and backup — and set up both, for free or nearly so.

📚 What You'll Learn

By the end of this lesson, you will be able to:

  • Explain the difference between sync and backup — and why you need both, not one
  • Compare Obsidian Sync against free cloud-folder sync (iCloud, Dropbox, OneDrive, Google Drive) and know each one's traps
  • Set up the Obsidian Git plugin to auto-back-up your vault to a private repo with full version history
  • Turn on the built-in File Recovery plugin and design a sane recommended setup that survives mistakes and disasters

⏱️ Estimated Time: 60 minutes

🎯 Project: Set up ONE backup method today — Git or a cloud copy — and prove it works by actually restoring a file.

In This Lesson

Sync vs Backup — The Big Distinction

These two words get used interchangeably, and that confusion is exactly how people lose data. They solve different problems:

🔄 Sync 🛟 Backup
Question it answers "Are my notes the same on my laptop and my phone?" "Can I get back a note I ruined or deleted last Tuesday?"
Direction of copies Mirrors the current state everywhere Keeps past states you can return to
The danger it does NOT cover A mistake syncs instantly to every device Doesn't help you edit on two machines at once

Here's the trap that catches everyone: sync is not backup. If you delete a paragraph or a whole folder and your vault is synced, that deletion is faithfully copied to every device within seconds. Sync did its job perfectly — and your work is gone everywhere at once. Backup is the safety net that remembers yesterday, so a mistake made today is recoverable.

📖 Definition

Sync keeps the same notes on all your devices, always current. Backup keeps copies of previous versions you can restore after a mistake or disaster. A good setup does both — one service for sync, another (or the same one, if it offers version history) for backup. Never assume "it's in the cloud" means "it's backed up."

graph TD L["💻 Laptop vault"] -->|"🔄 Sync"| P["📱 Phone vault"] P -->|"🔄 Sync"| T["📱 Tablet vault"] T -->|"🔄 Sync"| L L -.->|"🛟 Backup
keeps history"| B["🗄️ Versioned store
(Git repo / snapshots)"] B -.->|"⏮️ Restore any past version"| L S["😱 Oops — deleted a note"] -->|"sync spreads it"| P B -->|"backup brings it back"| S

Notice how sync (solid arrows) spreads everything, good and bad, instantly — while backup (dotted arrows) is the one-way ratchet that lets you step back in time.

Obsidian Sync (Official)

Obsidian Sync is the company's own paid service, and it's the path of least resistance. You turn it on, log in on each device, and your vault stays mirrored across all of them. It's a subscription add-on (separate from the free app), and it's built specifically for how Obsidian works.

👍 Pros 👎 Cons
End-to-end encrypted — your notes are encrypted with a password only you hold; Obsidian's servers can't read them. Costs money — a monthly/annual subscription (though modest and it supports the developers).
Smart conflict handling — designed for notes, it merges or flags conflicts sensibly rather than making mystery duplicate files. It's sync first. Its version history gives you real backup-like recovery, but you're trusting one vendor for both roles.
Built-in version history — restore previous versions of notes and recover deleted files for a retention window. Requires an account and internet to sync (offline edits sync when you reconnect).
Rock-solid on mobile — the officially supported way to sync to iOS/Android without fuss. You choose which folders/attachments to sync, so a misconfiguration can leave something out.

Because Sync includes version history and file recovery, it comes closer than most options to covering both jobs at once — but many careful users still pair it with an independent backup (Git or a periodic export) so their history doesn't live entirely with a single provider. If you value your time and want mobile that "just works," Obsidian Sync is the easy, honest recommendation.

✅ Pro Tip

Whatever you sync with, sync the whole vault folder, including the hidden .obsidian settings folder, so your plugins, hotkeys, and theme travel with you. The one thing you may not want to sync is a large media folder or a Git repo's .git directory — more on that in the cloud-folder section.

Free Sync via Cloud Folders

You already own a general-purpose sync service — iCloud Drive, Dropbox, OneDrive, or Google Drive. The trick is beautifully simple: put your vault folder inside the folder that service already syncs. Because your vault is just a folder of plain files, the cloud service mirrors it across every device signed into that account, and Obsidian never has to know.

How to do it, in essence:

  1. Move (or create) your vault folder inside your Dropbox / iCloud Drive / OneDrive folder on your computer.
  2. In Obsidian, "Open folder as vault" and point it at that location.
  3. On your other desktop, wait for the cloud app to download the folder, then open it as a vault there too.

It's free (within your existing storage quota) and it works well between desktops. But there are real caveats you must respect:

⚠️ Watch Out — the cloud-folder caveats

  • Conflicts make duplicate files. If two devices edit the same note before syncing, you can get "note (conflicted copy).md" files. It's recoverable, but it's messier than Obsidian Sync's merge.
  • Mobile is the sharp edge. On iOS/Android these services generally do not sync arbitrary folders into the Obsidian mobile app cleanly — iCloud Drive is the main workable route on iOS, and Dropbox/Google Drive/OneDrive typically don't sync directly into mobile Obsidian. If you need phone access, plan for Obsidian Sync or Obsidian Git instead.
  • "Online-only" / smart-sync can hide files. If the cloud app keeps files as cloud-only placeholders, Obsidian may not see them. Set the vault folder to "always keep on this device."
  • Never sync one vault through two services at once (see the warning below).
⚠️ Important Note: Do not put the same vault under two sync services simultaneously — e.g. a folder that lives in both Dropbox and iCloud, or Obsidian Sync layered on top of a Dropbox folder. The two services will fight over the same files, racing to overwrite each other, and you'll get corruption and conflict copies. Pick one sync mechanism per vault. Backup is different — it's fine (and good) to have a backup in addition to your one sync method.

Obsidian Git for Backup & History

If sync answers "everywhere," Git answers "every version." Git is the version-control system developers use to track every change to a codebase — and since your vault is plain text, it's a perfect fit. The Obsidian Git community plugin wires Git into Obsidian so you don't need the command line.

The idea: your vault becomes a Git repository, pushed to a private repo on GitHub, GitLab, or similar. On a schedule (say every 10 minutes) the plugin commits a snapshot of everything that changed and pushes it to the remote. The result is a complete, timestamped history — you can see exactly what a note said last week and roll any file back to any past commit. It's an outstanding, free backup with version history baked in.

What Obsidian Git gives you The caveats
Free, full version history of every note, forever. Needs a one-time setup: install Git, create a private remote repo, authenticate.
Off-site backup — your work survives a dead laptop, sitting safely on the remote. Not a great primary sync tool — it can move notes between machines, but conflicts and merges are clunkier than a real sync service.
Automatable — auto-commit/backup on a timer or on save. Mobile works but with caveats — the plugin supports mobile, though large repos and big binary files can be slow or fiddly on a phone.
Private — use a private repo and no one but you can read it. Binary attachments (PDFs, images) bloat the repo; consider a .gitignore for huge media.

Setup, at a high level:

# 1. Install Git on your computer (git-scm.com) — desktop only step
# 2. Create a NEW, PRIVATE, empty repo on GitHub/GitLab
# 3. In a terminal, inside your vault folder:
cd /path/to/YourVault
git init
git remote add origin git@github.com:you/your-vault.git
git add .
git commit -m "Initial vault backup"
git push -u origin main

Then in Obsidian: install the Obsidian Git plugin, and in its settings enable auto-backup (e.g. "commit and push every 10 minutes"). From then on it's hands-off. A tiny .gitignore keeps noise out of history:

# .gitignore inside your vault
.obsidian/workspace.json   # per-device window layout, changes constantly
.trash/                    # Obsidian's local trash
# Optionally, huge media:
# Attachments/*.mp4

✅ Pro Tip — think of commits as save-points

Every commit is a snapshot you can return to, like a save-point in a game. You don't need to understand Git deeply to benefit: let the plugin auto-commit, and know that "restore an old version" is always available. If you ever want the details, the C++/Netlify course and countless free Git primers cover branches and merges — but for backup, auto-commit is all you need.

File Recovery (Local Snapshots)

Before any cloud service, Obsidian ships a humble hero: the File Recovery core plugin (enable it in Settings → Core plugins). It periodically saves local snapshots of your notes, right on your machine. If you accidentally delete a big chunk of text, or a note gets mangled, you can open File Recovery, browse past versions of that note, and restore one.

Its scope is deliberately small but genuinely useful:

  • It protects against editing mistakes — wiped paragraphs, bad find-and-replace, an errant plugin.
  • You control the snapshot interval and how long history is kept, in its settings.
  • It's local only — so it does nothing if your drive dies or your laptop is lost. It is not a substitute for off-device backup.

⚠️ Watch Out

File Recovery is your "undo of last resort," not your backup plan. Because its snapshots live on the same computer as your vault, a hardware failure takes both. Treat it as the fast, local safety net for oops moments, and pair it with an off-device backup (Git or cloud version history) for the disaster moments.

A Sane Recommended Setup

You don't need all of these — you need one sync and one backup, plus File Recovery switched on because it's free and local. Here are three sane, complete recipes:

Profile Sync Backup
Easiest (some money) Obsidian Sync Obsidian Sync version history + occasional Git or export for peace of mind
Free, desktop-centric iCloud / Dropbox / OneDrive folder Obsidian Git auto-commit to a private repo
Free, tech-comfortable, mobile Obsidian Git (or Sync) — plus iCloud on iOS The Git remote itself is your versioned backup; add periodic exports

Across all three, the non-negotiables are the same:

  • One sync mechanism per vault — never two racing each other.
  • At least one off-device backup with history (Git remote, Sync history, or a periodic zipped export saved elsewhere).
  • File Recovery enabled for instant local undo.
  • You've actually tested a restore — an untested backup is a rumour, not a backup.

🧠 Mindset

Backup feels like insurance: boring, invisible, easy to postpone — until the one day it's the most important thing you ever set up. The people who lose years of notes aren't careless; they're just busy, and "I'll sort backups later" quietly became "never." Spend 30 minutes today. Future-you, staring at a dead drive with a calm smile because everything's on GitHub, will thank you more than you can imagine.

🎯 Project: Set Up & Test a Backup

The goal today is small and decisive: get one real backup working, and — crucially — prove you can restore from it. A backup you've never tested is just a hope.

🏋️ Stand up one backup and verify a restore

Objective: Pick Git or a cloud copy, set it up, then deliberately break a note and bring it back.

Instructions (about 30 minutes):

  1. (2 min) Enable the File Recovery core plugin first — it's free and instant insurance while you set up the real thing.
  2. (3 min) Choose your path: A — Obsidian Git (full version history, best long-term) or B — Cloud copy (simplest today).
  3. (15 min) Do your chosen path:
    • Path A (Git): Install Git, create a private, empty repo, run the git init … push commands from Section 4 inside your vault, then install the Obsidian Git plugin and turn on auto-backup. Confirm your files now appear in the remote repo's web view.
    • Path B (Cloud copy): Close Obsidian. Copy your entire vault folder into your synced cloud folder (Dropbox/iCloud/OneDrive) — or, at minimum, zip the vault and upload the zip. Wait for it to finish uploading and confirm it shows online.
  4. (5 min) The restore test — do not skip this: In a throwaway test note, type "DELETE ME", save, let the backup capture it, then delete the whole note. Now recover it: Path A — use the plugin's history / your repo to restore the file; Path B — pull the earlier copy back from the cloud (or File Recovery). Confirm the text returns.
  5. (3 min) Write one line in your Learning Journal recording which method you chose and how to restore, so tomorrow-you isn't guessing during an emergency.
  6. (2 min) Double-check you are not syncing this vault through two services at once.
💡 Hint — the fastest possible backup right now

Short on time? Close Obsidian, zip your vault folder, and drop the zip in your cloud drive with today's date in the filename. It's not automated and it's not versioned, but it's a real off-device backup you can do in five minutes — then upgrade to Git or Sync when you have a spare half hour.

✅ Project Completion Checklist

  • File Recovery core plugin is enabled
  • You set up one real backup (Git remote or a cloud copy)
  • You deleted a test note and successfully restored it
  • You recorded, in writing, how to restore in an emergency
  • You confirmed the vault is synced by at most one service

🎯 Quick Quiz

Question 1: You delete an important note by accident and your vault is synced across all devices. What happens, and what saves you?

Question 2: Which setup is a recipe for corruption?

Best Practices for Sync & Backup

✅ Do's

  • Have both. One sync method and one off-device backup with history.
  • Test your restore. Recover a throwaway note now, not during a real emergency.
  • Sync the whole vault, including .obsidian, so settings travel too.
  • Enable File Recovery — it's free, local, and saves you from editing blunders.

❌ Don'ts

  • Don't run two sync services on one vault. They corrupt each other.
  • Don't call sync a backup. Mistakes sync instantly; only history undoes them.
  • Don't rely on cloud folders for iOS. Only iCloud works cleanly on iPhone/iPad; plan Sync or Git otherwise.
  • Don't bloat a Git repo with huge media — .gitignore the big binaries.

📓 Learning Journal

Open your Learning Journal note in your vault. After this lesson, jot down:

  • Key concepts you learned
  • Techniques that clicked for you
  • Questions or confusion points to revisit
  • Ideas you want to try
  • Your progress and feelings about learning this

✍️ This lesson's prompt: Write down your exact recovery plan in one paragraph: which service syncs your vault, which one backs it up with history, and the precise steps you'd take at 2 a.m. to restore a note you just wrecked. If you can't answer confidently, that's your to-do for tomorrow.

📝 Lesson Summary

🎓 Key Takeaways

  • Sync ≠ backup. Sync keeps devices identical; backup keeps recoverable past versions. You need both.
  • Obsidian Sync is the easy paid option: end-to-end encrypted, smart conflicts, built-in version history, best on mobile.
  • Cloud folders (iCloud/Dropbox/OneDrive/Drive) sync for free between desktops — but mind conflict copies and the fact that only iCloud sync works cleanly into mobile Obsidian.
  • Obsidian Git is superb free backup with full version history; File Recovery is your local undo-of-last-resort. Never run two sync services on one vault.

🎉 What You've Accomplished

You now understand the single most important safety idea in personal knowledge management — that sync and backup are different jobs — and you've set up at least one real backup and proven you can restore from it. Your vault is no longer a single point of failure. That's the difference between notes you're nervous about and notes you can build a life's work on.

❓ Common Questions at This Stage

Do I really need to pay for Obsidian Sync if Git and cloud folders are free?

No. Plenty of people run entirely free setups (cloud folder for sync + Git for backup). Pay for Sync if you value the convenience, seamless mobile support, and encrypted, conflict-aware syncing — it's a fair price for zero fuss, and it funds the app. Both routes are legitimate; choose by budget and tolerance for setup.

What's the simplest option if I only use one computer?

Then you don't need sync at all — just backup. Enable File Recovery, and set up Obsidian Git (or a scheduled cloud copy) so an off-device, versioned backup exists in case that one computer dies. One machine still needs protection from disk failure and mistakes.

Can I use Obsidian Git on my phone?

Yes, the plugin supports mobile, but with caveats: large repos and big binary attachments can be slow or awkward on a phone, and the initial setup is fiddlier than on desktop. If seamless mobile is your top priority, Obsidian Sync is the smoother path; if you're comfortable with Git and keep media modest, Git on mobile works.

🔭 Looking Ahead

Your notes are now safe and everywhere. Next we look outward: how to publish and share selected notes with the world — as a digital garden, documentation, or blog — using Obsidian Publish or free tools like Quartz and GitHub Pages, while keeping your private notes private.

✅ Before the Next Lesson

  • Confirm your backup is running and you've tested one restore
  • Write your one-paragraph recovery plan in your journal
  • Decide (even loosely) which sync method is your one-and-only for this vault

📚 Additional Resources

🌟 Encouragement for the Journey

You just did the unglamorous work that separates a hobby from a home for your thinking. Everything you write from here on rests on solid ground — synced, versioned, and recoverable. Now that your vault is bulletproof, let's share the best of it with the world. 🔮