AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Duplicacy windows preference file4/11/2024 I believe it's a wiki, so you could do other users a great favour by adding a page about "central vs decentral preference directory" or something like that. ![]() It sounds like your setup should be described in all necessary detail in the duplicacy instructions as a kind of step-by-step guide. You might as well link to your more detailed explanation of your setup here -) If I understood correctly, is this what you are talking about? So when I want to restore something to a different folder I just copy that little file (or create, it's just a txt file with one line) to the new folder and run duplicacy restore. I use the settings in a centralized folder (the -pref-dir option), then in each repository there is no duplicacy folder, cache, keyrings, etc., only a small file with one line: the path to the settings folder. Of course it would be great to have the -restore-to option, but it is perfectly possible to do the restore to any desired location without it. I'm not sure if I understood the difficulty of doing the restore to a different location. ![]() From a usability perspective, this seems like a better use-case. I'll steal this thread to say that i also think duplicacy should let us restore wherever we want to, not only to a new (empty) repository. Initializing a new repository before running the restore command isn't too bad, and it is actually less error-prone than the -restore-to option. It is my personal preference not to implement this option for simpler logic and a unified way of restoring files. It is just a matter of providing a -restore-to option to the restore command. Why insist on the original location, going even so far as to force the user to initialize a new repository with the same name if the old one no longer exists? I'll update the GUI user guide once the beta becomes more stable.īut why not let let the user choose whether the files(s) in question should be restored to the original location or somewhere else? Any backup program I know does that. In beta 2.1 to restore to a different location you'll need to initialize a new repository on the new location with the same repository id. I think if we allow the history command to take a wildcard pattern then it can be used to search files within a range of revisions. I was sure that once I clicked "restore" I would be asked where to restore it to, but this was not the case so I frantically had to stop the process to prevent stuff from being overwritten. Any chance that search across revisions will become available?Īlso: I miss the possibility to restore a file to a different location. OK, I figured out that the search function already exists, at least in the latest GUI beta 2.1, but you have to know your search wildcards and you can only search within one revision at a time. Not to mention that I have to lookup the relevant revision numbers (because, usually, you want to search a particular time frame rather than particular revisions). Even if I'd work with CLI only, it's not possible to do a search and then say: yes, please restore that file? Can we expect to get that search function as part of a proper restore interface in the GUI? It's extremely cumbersome having to search for one or multiple file paths using CLI and then basically having to re-enter them into the restore interface. Otherwise, use the list command and grep: duplicacy list -r 12 -files | grep patternĭuplicacy list -r 1-100 -files | grep patternīut even so: it looks like i've found the big minus for duplicacy. If you know the exact file name, then the history command is the best option: duplicacy history -r 12 path/to/file ![]() How can I search for a particular file name (or parts thereof) However, I don’t see why all normal FS interactions are fine, but Kopia cannot see it.This questions is relevant both for the CLI and the GUI version. I suspect the reason for this is that I’m using btrfs on my F drive (via WinBtrfs). Snapshot includes 0 files, total size 0 B : unable to stat directory entry "System Volume Information": CreateFile F:\/System Volume Information: Access is denied. Note that I set the policy to ignore errors. I’m using Windows 10 (a fresh installation), and all the native Windows utilities can read my data drive, and I’ve tested restic successfully on it as well.Įrror reproduced below, along with a successful ‘dir’ listing. I’ve recently discovered Kopia while trying to decide between restic and duplicacy, and Kopia looks to better meet all my needs! Unfortunately, it appears that Kopia is unable to read my main personal data drive.
0 Comments
Read More
Leave a Reply. |