Backups
Fix backups that won't turn on, won't run, can't reach off-site storage or can't be restored, and what to do about a lost recovery key.
Turning backups on and running them
You see
Backups won't turn onDo this
- Pick a folder you can write to, outside Murage's own data folder. A folder inside
.murageis refused, because a backup kept with the data it protects is lost with it. - Allow the restart. To take a backup, Murage closes and reopens its own window. It asks your permission once. Backups can't run until you allow it.
- On Windows, pick a local folder. A network folder or a USB stick is refused, because Windows can't lock those down to your account. A password file you choose is refused if other accounts can open it.
You see
Back up now does nothingDo this
Back up now won't start while a bot is working or another backup is running. Wait for the bots to finish, or stop the running turn, then try again.
You see
The daily backup didn't runDo this
- Murage needs to be running at backup time, unless Also back up when Murage is closed is on. That option works on a Mac and on Linux (
.deband AppImage), not on Windows yet. - If a bot was waiting for your answer, the backup waits too. SettingsBackups and the Inbox name the bot, and the backup starts as soon as you answer.
- If the backup folder or recovery key was moved, or its drive is unplugged, SettingsBackups names which one is missing, with an Inbox item and a notification.
- A sleeping computer doesn't back up.
- Check the latest verified backup shown in SettingsBackups.
You see
Update waiting for backupDo this
Murage may take a backup before updating. If the update card says it's waiting for the pre-upgrade backup, open SettingsBackups and deal with whatever it shows.
The recovery key
Your recovery key is the only thing that can open your backups. Murage saves it outside both its data folder and your backup folder, and never keeps another copy.
You see
Save a copy of the recovery keyDo this
Choose Save a copy… and keep one on a USB drive or in your password manager.
You see
I lost the recovery keyDo this
The backups can't be opened without it. If Murage still works on this computer, start a fresh backup with a new recovery key straight away, and save a copy of the new key. Old backups made with the lost key stay unreadable.
You see
I want to use my own key fileDo this
Open I already have a recovery key and choose Use a key I already have.
Off-site copies
Off-site copies are encrypted before they leave your computer. Set them up under Off-site copy (optional).
You see
Off-site copy to S3-compatible storage failsDo this
Check the endpoint, bucket, region and access keys in Off-site copy (optional). The bucket must already exist, and the keys need permission to write to it.
You see
Off-site copy to an SFTP server failsDo this
Check that the key Murage showed you (Copy key) is in the server's authorized_keys for the user you entered.
If Murage says the server's fingerprint changed, it refuses to connect. If you reinstalled or replaced the server, choose Change destination and save it again to trust the new fingerprint. If you didn't, ask whoever runs the server first.
On Windows, SFTP uses the OpenSSH Client that comes with Windows. If it's missing, add it under SettingsSystemOptional features.
Also check your storage provider's status and your internet connection.
Restoring
You see
I can't restore a backupDo this
- Choose Restore…, then pick a backup on this computer, or choose Find off-site backups and Download verified copy.
- On a new computer, add the same off-site destination first and choose Choose a password file I already have with the off-site password you kept.
- Have your recovery key ready.
- After a restore, memory stays paused until you review it.
- If the restore stops with a message, read it before retrying.
What isn't in a backup
- Engine sessions. Not included.
- Local VM home folders. Not included, nor are folders outside Murage.
- Engines and their sign-ins. Not included. Keep important files that live elsewhere in your own backup.
- Skipped items. Shortcuts, unusual file names and rebuildable folders such as
node_modulesand virtual environments don't stop a backup. They're left out, and Murage lists by name what it skipped.
Every sentence a stopped backup or restore can show, with what to do, is on Backup and restore errors.
See also: Backups and export.
