2.1.0.4_stable_2025-01-31 unsupported "zip" compression method lzma while restoring

Ilgaz · February 15, 2025, 4:55pm

I am trying to restore Linux backed up files to Windows NTFS disk. I selected LZMA (thanks for support!) since I am dealing with several uncompressed TIFF files.

When I try to restore via the .json configuration, it displays:

----zip-compression-method=LZMA
----allow-missing-source=true
----disable-on-battery=true
----auto-vacuum=true
----auto-cleanup=true
----no-encryption=true
–retention-policy=1W:1D,4W:1W,12M:1M
–dblock-size=50mb
–compression-module=zip
–encryption-module=
and after finding the backup dates, it says:

image509×115 2.51 KB

Ilgaz · February 15, 2025, 6:03pm

Interestingly, I have dual booted into Linux now, the OS I created the backup and when I click “restore”, it simply worked.
IMHO there is something with “backup configuration import → restore” process.

ts678 · February 15, 2025, 8:24pm

github.com/duplicati/duplicati

Discrepancy with advanced options in "Restore from configuration"

opened 05:43PM - 18 Jul 17 UTC

ingul-buz

bug UI minor change reproduced

I have: - [x] searched open and closed issues for duplicates ---------------…------------------------- ### Version info **Duplicati Version:** 2.0.1.73_experimental_2017-07-15 **Operating System:** Windows 7 **Backend:** SFTP/SSH ### Bug description Using the option "Restore from configuration" in the Restore menu results in some options (specifically "Advanced options") containing two extra hyphens in front of them. ### Steps to reproduce - Normally export your settings to a file from an existing backup configuration. The configuration must contain at least one "Advanced option" in the "Options" tab (5), e.g. _log-file_ or _upload-verification-file_. - Select "Restore", then "Restore from configuration", select the .json file you just exported, and import it. **Actual result:** Check out the "Encryption" tab (2). The advanced options you added contain two extra hyphens in front of them, i.e. four in total: ----log-file. Other options derived from common form settings seem to only have the two expected hyphens. **Expected result:** Importing should either remove the extra hyphens found in the configuration file or not add more of them if they already exist. **Extra info** Using the same configuration file for adding a new backup doesn't seem to have any similar ill effects, everything seems to be in place. If you edit the configuration .json file by hand and remove the two hyphens from every option containing them, and then import the configuration within the Restore dialog, also the advanced options only contain the two common hyphens. On the other hand, this tampered .json file doesn't work that well for adding a new backup any more, since the options from which you removed the hyphens don't appear into the new backup configuration at all. So, the problem is you can't use the same configuration file for both purposes. Or maybe you can, if any of those options wasn't crucial when it comes to actually restoring the files, in which case you only get some warnings: ``` Warnings: [ The supplied option ----log-file is not supported and will be ignored, The supplied option ----upload-verification-file is not supported and will be ignored ] ```

is probably the bug that turned two dashes into four (assuming that was in Advanced options).

What Duplicati version? Your LZMA compression complaint might be a bug in a 2.1.0.4 feature.

Config tried to set --zip-compression-method=LZMA, but it was ignored due to extra dashes.
You can try on Windows after fixing, or adding --zip-compression-library=SharpCompress.

Ilgaz · February 16, 2025, 12:40am

Hello again. You are correct, in fact I somehow managed to have 4 dashes this time on Windows 10 and when I edited them, everything got fixed.
I am using the exact same version on Linux (opensuse tw), I downloaded from the “downloads” page.
Thanks for saving me from days of downtime as I have like 450GB of restore with 49 mbit VDSL2.