Any way to create and export directory/file tree list from a backup only?

Support
#1

Hi all, so while doing some organizing, I moved the contents of a substantial (11.4tb) folder from one spot to another, and deleted the old one.

Of course, when I deleted it, it turns out some other files got deleted, at least 80, too quickly for me to notice and I forgot I could have saved my desktop history with shadowplay to see what the files were. (which I just thought about now, uhg).

I started a restore function but after letting it go for a while now it settled down on an ETA of 9 days.

I could go get the offsite machine and bring it here if needed, but I’m hoping that there’s a way I can just generate and dump a file/file list of specific directories, or worst case the whole backup set, and use notepad++ to compare it from one I generate locally to see what the differences are.

They might have been totally garbage ini files but I don’t know for sure which is the problem.

Running duplicacy in docker on unraid so command line access is a little odd if I recall correctly. Thanks in advance for any help.

edit: If I recall correctly there might be a way to run the restore as just a test, and if I use the overwrite command with the test, maybe it would go faster and the log would list everything?

#2

Initialize new repository in the empty folder. Add the same storage. Then this: list · gilbertchen/duplicacy Wiki · GitHub

#3

In addition to list, you can also use the diff command to directly compare 2 revisions. Or if you use list, I recommend Beyond Compare to compare lists side-by-side (has a very generous trial period).

#4

Ok, another question since it’s not worth making a new thread, it looks like the web ui defaults to using overwrite for the restore process.

And with docker I guess there’s no way to access the CLI.

Is there a way with the web ui to restore without overwriting? That’s why it was going to take 9 days, it was going to overwrite all 11.4tb…

Not sure if it’s as simple as putting --overwrite.

#5

The GUI doesn’t default to overwrite with restore, you should see this in the logs instead:

2025-03-xx xx:xx:xx.xxx INFO RESTORE_INPLACE Forcing in-place mode with a non-default preference path