Backup and restore errors
Every message a backup or a restore can show, what each one means, and what to do: wrong recovery key, damaged file, drive full, daily backups paused, off-site password file problems.
A restore stops
You see
Murage couldn't open this backup with that recovery key, so nothing was restoredDo this
Either the key is not the one made with this backup, or the backup file is damaged. Murage cannot tell the two apart. Try the copy of the key you saved, or choose another backup. Each backup opens only with the key that existed when it was taken, so a key you made later will not open an older backup.
You see
That file isn't a Murage recovery keyDo this
Choose murage-recovery-key.txt, or the copy of it you saved. A password file, an off-site password or an edited copy will not do.
You see
This backup file is damaged or incomplete, so nothing was restoredDo this
Choose another backup. If this one came from off-site storage, choose Find off-site backups and Download verified copy again.
You see
The backup file changed while Murage was checking itDo this
Something wrote to the file during the check, often a sync app. Choose the file again, then try once more.
You see
On Windows Murage can open a backup of up to 20 GB, and this one is biggerDo this
Restore it on a Mac or a Linux computer instead. The backup is fine.
You see
This backup is larger than Murage can restore in one goDo this
Contact support with the diagnostics folder. Choose Open diagnostics folder in the recovery window.
You see
A restored copy is waiting for your reviewDo this
A restore goes into a new folder and stays paused until you look at it. Choose Review restored installation, then Approve and open. Engines and messaging apps are connected again afterwards, and memory stays paused until you review it.
You see
That took too long, so Murage stopped it and nothing was changedDo this
Try again. A large backup can take several minutes to check.
A backup could not be written
You see
The drive ran out of space while the backup was being writtenDo this
Make room on the drive that holds your backup folder, then try again.
You see
This computer didn't let Murage write a file the backup neededDo this
Check that you can create files in your backup folder yourself. If you cannot, pick a folder you own.
You see
Another program was holding a file the backup neededDo this
Often antivirus or a sync app. Wait a few minutes and try again. If it keeps happening, pause the sync or antivirus for the backup folder.
You see
Murage couldn't make its private working folder inside your backup folderDo this
Choose a folder on this computer's own drive that you can create files in. On Windows, a network folder or a USB stick is refused for this reason.
You see
Murage couldn't finish writing the backup fileDo this
A plain file error on the backup folder or its drive, nothing to do with your recovery key. Try again. If it happens twice, open the diagnostics folder and send the newest log to support.
Daily backups are paused, or a backup can't start
You see
The last backup didn't finish, so daily backups are pausedDo this
Choose Clear and try again. Your existing backups are kept.
You see
Murage is running as administrator, and backups can't run that wayDo this
Close Murage, open it normally, then try again.
You see
Murage can't reopen itself because its AppImage file was moved or deletedDo this
Close Murage, then open it again from where the AppImage file is now.
You see
Backups while Murage is closed need the background job firstDo this
Tick Also back up when Murage is closed again, then try once more. If your system could not start the job, backups run only while Murage is open.
You see
The backup can't start because a bot is waiting for your answerDo this
Answer the bot, or end that run, then back up again. SettingsBackups and the Inbox name the bot.
You see
Your backup folder or recovery key has moved or changedDo this
Turn off daily backups, then choose the backup folder and your recovery key again.
You see
Murage couldn't find your recovery key fileDo this
Put it back where it was, or turn off daily backups and choose your key again. Then back up again.
Off-site password file problems
The off-site password file is a small text file, under 4 KB, with the password on one line and nothing else. It lives outside Murage's own folders and outside your backup folder, and only you can read it. Murage made it for you when you chose Create off-site password, and it is tied to the repository that was created at the same moment, so a password file from one destination will not open the copies at another. Don't keep it in the backup folder itself; a backup kept with its own password opens for whoever picks up the drive.
You see
The off-site password file does not open the backup repository in this folderDo this
Choose the password file you used when this repository was created. A password made later belongs to a different repository.
You see
Murage could not read the off-site password fileDo this
It may have been moved, renamed or changed. Put it back, or choose it again.
You see
That isn't a plain password fileDo this
Choose a small text file, under 4 KB, that is not a shortcut or link.
You see
That file doesn't hold a single-line passwordDo this
Choose a file with the password on one line and nothing else.
You see
Other accounts on this computer can open that fileDo this
Copy it into your home folder, which only you can open, then choose the copy and delete the original. On a Mac or Linux, you can instead make the file readable only by you and choose it again.
You see
That file is inside Murage's own folders or your backup folderDo this
Keep the off-site password somewhere else, such as your home folder, then choose it again.
Backups that will not turn on, a daily backup that did not run, and SFTP or S3-compatible connection problems are on Backups. Setting backups up is on Backups and export.