I see. What I would then suggest, is download the CLI version to your local drive, on whatever OS you use, and play with it. Create a test folder, fill it with dummy files, initialize duplciacy repository there, check what files does it create, backup test folder to some other folder, restore, prune, etc., make mistakes, and read documentation – well designed command line tool (including duplicacy) provide sufficient diagnostic to figure out the issues.
Stuff that gets glossed over in most of tutorials is stuff that is easily discoverable. It’s an extremely important skill to have – diagnosing an issue and discovering direction to the solution. It’s way more important than learning any specific workflow in a specific skill with a specific OS. And discoverability starts with a habit to read error messages. Error messages get you to a solution 99% of times.
Example at hand --at that your screenshot duplciacy told you what’s missing, and not only that, printed documentation for the command, so you don’t have to go fish for it online.
Then, you made next step – saw a conflict in what you think you have provided (which was correct to add storage) to what duplicacy received (that included incomplete --copy argument).
Next step would be to step back and try to construct the command line again, using the manual just dumped, to add the storage, and then add --copy flag, at which point you would catch that you forgot to add the argument to --copy the first time, perhaps because you got distracted.
That’s the most important skills to acquire, and in fact, that’s precisely what I did when looking at your log – I don’t remember duplicacy command (or anything else for that matter) off hand, but having developed a habit to methodically step back and evaluate what software is telling you.
At some point yes, you woudl need external help, if you face some non-trivial situation, but that won’t happen until after you are so comfortable with the tool that you start venturing into unsupported configurations and breaking things (in a positive sense). At this point however forums would likely be useless, and you will end up figuring it out on your own, (and then hopefully writing your own blog post to help others, and/or sending pull requests with a fix)
That’s the idea.
And a side note - on windows making sense of command line interface is for some reason way harder than it is on macOS and Linux than it should be (and I’m former 15+ windows user who migrated 12+ years ago to macOS, so maybe I’m biased. Maybe not ), partly because of CMD/ PowerShell diffences (you have powershell on your screenshot which is way more than just a command line), and now Windows has whole linux runtime environment – you can use that, there is way more resources available to help navigate linux command line thats it is for windows. That last paragraphs is purely my subjective opinion.
Regardless, do reach out if you are stuck along the way – that’s why the forums exist, and nobody is born with all skills and knowledge. That wasn’t to discourage, but rather optimize efforts.