Docs › Running MCDock

Backups and restore

Two kinds of backup, a NAS copy, restore tests and restoring only what you need.

Two kinds of backup

  • Server backup: settings, users, teams, permissions, branch rules, webhooks and pipeline set-up. No source code, so it is small. Every 4 hours and 5 minutes after an admin change.
  • Repository backup: one per repository with all branches, tags, LFS files, issues and pull requests. Nightly; unchanged repositories are skipped. Mark a repository critical to back it up every hour when it changes.

Local and NAS

Set a NAS folder on the Backups page. Every backup is written locally and copied to the NAS. A restore checks every byte and uses the other copy if one is missing or damaged. Run the service with a group-managed service account that alone may write to the share, and give ordinary users no access to it.

Restore

  • A repository: as a new copy (nothing changes), replace it (a backup of its current state comes first), or bring back one branch.
  • Part of a server backup: users and teams, permissions and rules, pipelines set-up or settings. Repository content is never touched.
  • Everything onto a new machine: mcdock.exe restore-all, or from the web.

Restore tests

The newest backups are restored into a scratch folder every week and checked file by file, with git fsck on every repository. Results are on the Control center.

Updated 20 Nov 2026 · Something missing? Ask in the community.