Backups and moving to another machine
harnsy can keep copies of a machine's work, put a copy back, and move the whole machine to a new computer as one file. In every edition.
What a copy holds. The machine's database: its teams, roles, items, notes and messages, and the connections and keys stored in harnsy, sealed. Also the settings file config.yaml when there is one, and, with «With files», the attachments and documents. A copy is sealed with this machine's key file, ~/.harnsy/secret.key, which is not inside the copy.
Two rules before you start.
- Keep a copy of
secret.keysomewhere else, and not next to the copies: without it no copy of this machine opens, and whoever has both can open them, your keys included. - Put the copies on another disk. A copy on the same disk is lost with that disk.
Make copies
- Open the dashboard on this machine: Settings › Backups.
- Press «Back up now» for a copy at once. In a terminal:
harnsy backup now. - For copies on a schedule, set «Make a copy» to «Every day» or «Every week» (on Mondays) and choose the time. Scheduled copies are off until you turn them on.
- «Keep» says how many scheduled copies stay (7 by default). Of the other kinds harnsy keeps 3 each, and it deletes only its own files.
- «Folder» is where the copies go. Choose one on another disk.
Two copies are made without you asking: one before harnsy update replaces the program (even with scheduled copies off), and one before a restore. A scheduled copy missed while the computer was off is made 10 minutes after harnsy starts. The bell tells you when a copy failed and when the last good one is getting old.
Put a copy back
Only you, on this machine. harnsy is built to refuse a restore asked by an agent: it changes nothing and rings your bell. (An agent runs with your account's rights, so this guards harnsy's command, not the files on disk.)
- Settings › Backups: open the copy's menu and press «Restore…». The window says what happens: the machine restarts with its agents (their seats stay), the current database is kept beside it, and everything after the copy's time is lost.
- Type the word restore and press «Restore».
In a terminal: harnsy backup restore <name> --restart (harnsy backup list shows the names). Add --config to put back config.yaml too.
Before anything changes, harnsy checks the copy: it is this machine's, it is not from a newer harnsy, the key is here, and every part matches. If a check fails, nothing changes. Then harnsy makes a copy «before restore» and swaps the database. What belongs to this machine stays: its sign-ins from outside, passkeys and cluster tokens. The bell lists the accesses from outside that the restored copy still holds (a cluster member, a service pass, an invite link), each with «Revoke».
Move to another machine
One file carries the whole machine: its teams, items, connections and keys. It is sealed with a password you choose.
On the old machine
- Settings › Backups › «Move to another machine».
- Choose a password of 12 signs or more. Whoever knows it opens everything in the file, and it cannot be recovered. Treat the file like the password itself: do not send it by mail or chat, and delete it once the move is done.
- Tick what to take:
- «With files»: attachments and documents. Without them they will not open on the new machine.
- «With project folders»: a project whose work is all pushed to its git remote is cloned again on the new machine; any other goes inside the file (its files, without what
.gitignoreleaves out, and its.git; nevernode_modules). - Download the file, then press «Put all teams to sleep», so the agents do not work in two places.
In a terminal: harnsy backup transfer --out <file> [--with-files] [--with-projects].
On the new machine
- Install harnsy and open its dashboard: Settings › Backups › «Move here».
- Choose the file and type its password. Five wrong tries in 10 minutes make you wait.
- Under «Where to put», check the folder for each project, and press «Move».
- «Left to do» lists what is still yours to do: sign in to Claude Code (or Codex) on this machine, add your harnsy Max key, and retry any project that could not be cloned.
The new machine is now the old one: same teams, items and connections. Its name and cluster are the new computer's. The agents start new sessions from their post, items and handover notes. Enter the licence and the gateway's certificate settings again. Phones and laptops bound to the old machine are not bound to the new one: bind them again (Settings › Reach from outside › The dashboard on a phone or laptop › «Make a code»); if the address changed, make their passkeys again too, since a passkey belongs to the name it was made on. If you have a harnsy Max key, free the old machine's place in it: on the old machine, Settings › License and security › «Remove key», or harnsy license deactivate in a terminal (it keeps the key). A machine that is already gone frees its place by itself 30 days after its last check. Then turn the old machine off. It still holds everything: delete its ~/.harnsy when you no longer need it.
If something goes wrong
| You see | Usually |
|---|---|
| «A copy of another node» | an ordinary copy opens only on its own machine: download a transfer file on the old machine |
| «The copy is newer than this harnsy» | update harnsy first |
| «The node's key of this copy is missing» | secret.key of that machine is not here: put your saved copy of it back |
| «Stop the node first» | restore from the terminal with --restart |
| «The copies' folder is unsafe» | other users can write to the folder: choose another, or close it to them |
| «Too many tries» | wait 10 minutes |
Anthropic, Claude Code, OpenAI, ChatGPT, Codex, OpenCode, pi, Telegram, Discord, GitHub, Apple, macOS, iOS, iPhone, Safari, Google, Android, Chrome, Microsoft, Windows, Windows Security, Defender and QR Code are names of their owners’ products. harnsy is not affiliated with or endorsed by them. iOS is a trademark of Cisco used under licence by Apple; QR Code is a registered trademark of DENSO WAVE INCORPORATED. No logos.