{
  "manifest_version": "1",
  "slug": "backup-to-exe",
  "title": "Backup to exe.dev",
  "headline": "Back up your computers to an exe.dev VM",
  "description": "Make an exe.dev VM the backup server for your laptops and servers: restic and rest-server, append-only, encrypted on your machines, with Backrest.",
  "category": "security",
  "tags": [
    "restic",
    "rest-server",
    "backrest",
    "backup server",
    "self-hosted backup",
    "backblaze alternative",
    "append-only backups",
    "offsite backup"
  ],
  "url": "https://exe.dev/deploy/backup-to-exe",
  "markdown_url": "https://exe-staging.dev/deploy/backup-to-exe.md",
  "upstream": {
    "website": "https://restic.net",
    "source": "https://github.com/restic/rest-server",
    "docs": "https://restic.readthedocs.io",
    "license": "BSD-2-Clause (restic, rest-server), GPL-3.0 (Backrest)"
  },
  "example_vm_name": "my-backups",
  "time": "15 minutes",
  "stack": [
    {
      "name": "rest-server 0.14",
      "detail": "restic's own HTTP server, append-only, run by systemd behind exe.dev's HTTPS proxy",
      "port": 8000,
      "data": "~/restic"
    },
    {
      "name": "backup-watch",
      "detail": "A daily systemd timer; emails you when a machine stops backing up or the disk fills"
    },
    {
      "name": "restic 0.20 or Backrest 1.14",
      "detail": "On each machine you back up; encrypts everything before it leaves"
    }
  ],
  "access": [
    {
      "url": "https://my-backups.exe.xyz/",
      "who": "private",
      "what": "The backup server, for restic and Backrest with a VM token or VM-to-VM integration per machine"
    }
  ],
  "delivers": [
    "rest-server 0.14 in append-only mode on port 8000, storing repositories in ~/restic, started at boot.",
    "The VM private, so only clients with an exe.dev VM token or VM-to-VM integration, or you over SSH, reach the repositories.",
    "A daily check that emails you when any repository has gone two days without a new snapshot, or the disk is 80% full.",
    "A test repository created, backed up to, refused a delete, restored, and removed again."
  ],
  "owner_runs_after": [
    "ssh exe.dev ssh-key generate-api-key --vm=my-backups --label=backup-laptop --exp=1y --json | jq -r .token"
  ],
  "deployable": true,
  "deploy": {
    "new_vm_url": "https://exe-staging.dev/new?prompt=Set%20up%20Backup%20to%20exe.dev%20on%20this%20VM%20by%20following%20the%20exe.dev%20recipe%20at%20https%3A%2F%2Fexe-staging.dev%2Fdeploy%2Fbackup-to-exe.md%3Fvia%3Ddeploy%20from%20top%20to%20bottom.%0A%0AThe%20recipe%27s%20example%20VM%20name%20is%20my-backups.%20This%20VM%27s%20name%20is%20the%20output%20of%20%60hostname%60%3A%20use%20it%20wherever%20the%20recipe%20writes%20my-backups.%20Skip%20the%20step%20that%20creates%20the%20VM%3B%20you%20are%20on%20it.%0A%0AYou%20are%20done%20when%20all%20of%20these%20are%20true.%20Check%20each%20one%20yourself%3A%0A-%20rest-server%200.14%20in%20append-only%20mode%20on%20port%208000%2C%20storing%20repositories%20in%20~%2Frestic%2C%20started%20at%20boot.%0A-%20The%20VM%20private%2C%20so%20only%20clients%20with%20an%20exe.dev%20VM%20token%20or%20VM-to-VM%20integration%2C%20or%20you%20over%20SSH%2C%20reach%20the%20repositories.%0A-%20A%20daily%20check%20that%20emails%20you%20when%20any%20repository%20has%20gone%20two%20days%20without%20a%20new%20snapshot%2C%20or%20the%20disk%20is%2080%25%20full.%0A-%20A%20test%20repository%20created%2C%20backed%20up%20to%2C%20refused%20a%20delete%2C%20restored%2C%20and%20removed%20again.%0A%0ARead%20the%20whole%20recipe%2C%20including%20the%20closed%20details.%20For%20initial%20setup%2C%0Afollow%20%22Install%20by%20hand%22%20first%2C%20skipping%20VM%20creation%20and%20SSH.%20The%0Awalkthrough%20at%20the%20top%20is%20for%20the%20owner%20afterwards.%0AWork%20as%20exedev.%20Install%20exactly%20the%20pinned%20versions%20and%20check%20their%0Achecksums.%20Leave%20the%20VM%20private.%20Never%20put%20a%20repository%20password%20on%0Athis%20VM%20except%20the%20throwaway%20one%20in%20%22Test%20it%22%2C%20and%20delete%20that%20test%0Arepository%20afterwards%20as%20the%20steps%20say.%20You%20can%27t%20make%20VM%20tokens%20from%0Athe%20VM%3B%20leave%20tokens%20and%20client%20setup%20to%20the%20owner.%0ADon%27t%20run%20Update%20or%20Restore.%0AVerify%20rest-server.service%20and%20backup-watch.timer%20are%20enabled%20and%0Aactive%2C%20port%208000%20answers%2C%20the%20append-only%20test%20refused%20the%20delete%2C%0Aand%20backup-watch.sh%20--dry-run%20prints%20ok.%20Do%20not%20reboot.%0A%0AFinish%20with%20the%20URLs%20I%20should%20open%20and%20these%20commands%2C%20which%20only%20I%20can%20run%2C%20from%20my%20own%20computer%20%28with%20this%20VM%27s%20name%20in%20them%29%3A%0A%20%20ssh%20exe.dev%20ssh-key%20generate-api-key%20--vm%3Dmy-backups%20--label%3Dbackup-laptop%20--exp%3D1y%20--json%20%7C%20jq%20-r%20.token%0A",
    "terminal": "curl -fsSL https://exe-staging.dev/deploy/backup-to-exe/prompt.txt | ssh exe.dev new --prompt=/dev/stdin",
    "prompt": "Set up Backup to exe.dev on this VM by following the exe.dev recipe at https://exe-staging.dev/deploy/backup-to-exe.md?via=deploy from top to bottom.\n\nThe recipe's example VM name is my-backups. This VM's name is the output of `hostname`: use it wherever the recipe writes my-backups. Skip the step that creates the VM; you are on it.\n\nYou are done when all of these are true. Check each one yourself:\n- rest-server 0.14 in append-only mode on port 8000, storing repositories in ~/restic, started at boot.\n- The VM private, so only clients with an exe.dev VM token or VM-to-VM integration, or you over SSH, reach the repositories.\n- A daily check that emails you when any repository has gone two days without a new snapshot, or the disk is 80% full.\n- A test repository created, backed up to, refused a delete, restored, and removed again.\n\nRead the whole recipe, including the closed details. For initial setup,\nfollow \"Install by hand\" first, skipping VM creation and SSH. The\nwalkthrough at the top is for the owner afterwards.\nWork as exedev. Install exactly the pinned versions and check their\nchecksums. Leave the VM private. Never put a repository password on\nthis VM except the throwaway one in \"Test it\", and delete that test\nrepository afterwards as the steps say. You can't make VM tokens from\nthe VM; leave tokens and client setup to the owner.\nDon't run Update or Restore.\nVerify rest-server.service and backup-watch.timer are enabled and\nactive, port 8000 answers, the append-only test refused the delete,\nand backup-watch.sh --dry-run prints ok. Do not reboot.\n\nFinish with the URLs I should open and these commands, which only I can run, from my own computer (with this VM's name in them):\n  ssh exe.dev ssh-key generate-api-key --vm=my-backups --label=backup-laptop --exp=1y --json | jq -r .token\n",
    "prompt_url": "https://exe-staging.dev/deploy/backup-to-exe/prompt.txt"
  },
  "published": "2026-11-21",
  "updated": "2026-11-21",
  "verified": "2026-11-21",
  "related": [
    "syncthing",
    "s3-storage",
    "garage",
    "rustfs",
    "vaultwarden",
    "immich"
  ],
  "alternatives": [
    "Backblaze",
    "CrashPlan",
    "iDrive"
  ],
  "files": [
    "https://exe-staging.dev/deploy/backup-to-exe/backup-watch.sh"
  ]
}
