Brownout woes - version being updated to already exists

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?

Is it worth my posting the logs?

John

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:

Thank you that gives me hope to know that

Yes I had set tempdir to a logical volume with ample storage.

How do I run Duplicati.CommandLine.RecoveryTool on debian 12? It’s a headless server.

Very grateful for your help .

John

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.

Thanks again for your help
John

I followed your advice to reboot after setting a new location for the temp folder.

I started restore and within twelve hours files were being restored to their original locations. That was Friday night UTC.

BY 09:15 on Saturday morning over 50% of the files had been restored, but there has been no progress since. Server State shows:

lastPgEvent : {“BackupID”:“23f006db-2297-40f1-9afe-2392cfbc070c”,“TaskID”:13,“BackendAction”:“Get”,“BackendPath”:“duplicati-b83aa88edca344d1a861d34c3bdf52961.dblock.zip.aes”,“BackendFileSize”:52366573,“BackendFileProgress”:52166656,“BackendSpeed”:601,“BackendIsBlocking”:false,“CurrentFilename”:null,“CurrentFilesize”:0,“CurrentFileoffset”:0,“CurrentFilecomplete”:true,“Phase”:“Restore_DownloadingRemoteFiles”,“OverallProgress”:0,“ProcessedFileCount”:17488,“ProcessedFileSize”:287016571076,“TotalFileCount”:30462,“TotalFileSize”:866835860388,“StillCounting”:false

and has not changed since Saturday morning.

Running task: Restoring: 12974 files (540.00 GB) to go at 594 bytes

The backup files are on mega.nz

Please advise to continue without jeopardising the existing recovered files.

Many thanks

John

Is it still stuck?

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.

Can this be done from the webui?

AFAIK it’s not something you ask for – it’s always there when you restore.