Back up and restore

For the person who set up Stuga.

For the person who set up Stuga. By default, Stuga backs up daily at 03:00 in its configured time zone and keeps the newest three backups, plus the latest backup from before an upgrade. Backups stay on the same computer. Stuga also backs up before an update changes its data.

Check or take a backup

Open Settings → This node → Backups.
Check Scheduled backup, Repeat and At for the schedule and time. The page shows the time zone.
Set Keep to choose how many backups to keep.
Choose Back up now to take one now.

Stuga pauses while backing up; open documents reconnect afterwards. The page lists backups and any failure. A failed scheduled backup also notifies the people who look after Stuga.

Keep another copy

The folder appears under Backups. Copy backups to another disk so a failure of Stuga’s disk doesn’t take them too. On a Mac, Time Machine can keep copies when it is enabled.

Restore on a Mac

Restoring replaces all current Stuga data. Nobody can use Stuga during the restore. Take a fresh backup first if you want to keep the current state.

Open Terminal and follow the Mac command setup to add stuga-node to this Terminal window.
Run stuga-node list and copy the name of the backup you want.

Stop Stuga:

sudo launchctl bootout system/dev.stuga.node

Restore, replacing the example with the backup name. Type that name again when asked:
Terminal window
```
stuga-node restore 2026-09-16T101500Z
```

Start Stuga again:

sudo launchctl bootstrap system /Library/LaunchDaemons/dev.stuga.node.plist

Open Stuga and check your documents. The restore keeps the data it replaced separately, but the restored Stuga resumes its usual deletion of old trash and expired history.

Restore with Docker

Use the Docker restore instructions. They stop Stuga, restore the backup and start the Stuga release recorded in it.

Move a workspace to another computer — move one workspace or all of Stuga.
When something goes wrong — deal with a failed start or connection.