Hi folks!
The power failed twice in quick succession, but it seemed my media server which is running on Debian 12 with LVM, restarted successfully; no damage done, so I thought. Duplicati was set to backup to mega.nz but I retained only one backup, since I’m on a Pro 1 account.
The system when restarted failed, unable to boot load LVM modules. I decided to reinstall Debian since I had a backup on mega.nz
After many, many hours “restoring” only the folders were recreated with no contents. The errors mentioned a lack of disc space for the database. I noticed/ logical volume /tmp was almost full. Through this forum I discovered how to move to a bigger “temp” folder. I started recover again and monitored the Live log. There were no errors nor any warnings . After about nine or ten hours nothing more was appearing in the verbose live log. I checked on “top” where “unrar” was shown running. At which point I went to bed.
This morning no files were restored, only the empty folders.
It seems that Duplicati had backed up a damaged system? The question is , is it possible to recover the missing files?
Duplicati does not use unrar so I do not think that is related.
It should not matter if the backup is from a damaged system, in that case you can recover what is not damaged.
I have seen the problem with /tmp being filled a few times, so maybe this has caused issues. Have you tried rebooting and then settings --tempdir=/path/with/more/space when doing the restore?
If it is not possible to recover files the normal way, there is a recovery tool as well, that can handle almost any broken issue, but speed is not great:
The tool is commandline/shell based. If you are on 2.0.8.1 or earlier, you should have the file /usr/lib/Duplicati/Duplicati.CommandLine.RecoveryTool.exe.
Despite the Windows-like name, it is a portable executable, so you can run it with:
mono /usr/lib/Duplicati/Duplicati.CommandLine.RecoveryTool.exe help
If you are using 2.0.9.102 or newer, it is called duplicati-recovery-tool and has an entry in /usr/bin so you should be able to just invoke it.
I have heard of extremely slow “Starting to restore”, but I do not recall anyone reporting a stall in the middle. Any chance the WebUI is just stuck and the restore is still running?
That should not be a problem if you end up restarting the restore.
A step in the restore process is to check which files (and blocks) are already restored, and it will not touch those that are restored correctly already.