Restore from config file: Warnings concerning unsupported options

onurbi · December 19, 2021, 11:47am

Hi,

trying to restore a backup from the config file prints warnins about not supported options when I try this from the web gui.

I created the json file just short before.

Normally I run the backup from the generated command line.without any error or warning messages.

The mentioned options are

snapshot-policy
log-file
log-file-log-level
no-encryption

Regards,

Onurbi

ts678 · December 21, 2021, 10:50pm

Does it sound like the issue below?

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 ] ```

Do you mean you normally have a GUI job defined, but backup with its Export As Command-line?

Is this a test? Do the warnings prevent the restore, or are they noise about things you don’t need?

onurbi · December 22, 2021, 7:42am

Yes it is a very similar issue. Next time I’ll look first in the bug reports

Yes.right.

Yes I wanted to be sure, that using the json file alone restoring is possible as well.

No, it does not. A standard restore operation does work.