I suspect it was the extra slash at the end of the path that caused the issue. Id:, revisions:, tag:, showFiles: false, showChunks: false Using a static salt and 16384 iterations for key derivationĬhunk seed: 36a44ef1d058a5e57096fc226fbdaa9bb7c4acafd6fa82fec8542ef34dc1e9b3 Reading the environment variable DUPLICACY_PASSWORD Looks like this: D:\Restore>C:\Users\Timo\AppData\Local\Duplicacy\duplicacy_win_圆4_2.1.0.exe -d list -a It will print out files/directories while listing the snapshots directory. Run the list command as: duplicacy_win_圆4_2.1.0.exe -d list -a Output is: N:\Duplicacy\snapshots>dir N:\Duplicacy\snapshots /aĭatenträger in Laufwerk N: ist Sicherung IĤ Verzeichnis(se), 1.052.060.123.136 Bytes frei Duplicacy was backing up a folder called SymLinks which includes 4 symbolic links to folders and the. Is TIMO-LENOVO-Timo-SymLinks a symbolic link? What is the output of dir N:\Duplicacy\snapshots /a? Yes, 21 files in \snapshots\TIMO-LENOVO-Timo-SymLinks:Īnd another 39 files in my wife's backup snapshot - none of both backups is detected by Duplicacy.
#DUPLICACY RESTORE HOW TO#
Please advise me how to access my backup :'(Īre there any files under n:\Duplicacy\snapshots\TIMO-LENOVO-Timo-SymLinks? My chunks and snapshots folders are not empty. Listing revisions for snapshot TIMO-LENOVO-Timo-SymLinks With correct ID pre-entered: D:\Restore>C:\Users\Timo\AppData\Local\Duplicacy\duplicacy_win_圆4_2.0.9.exe -v list -id TIMO-LENOVO-Timo-SymLinks Thanks for your fast reply, but it didn't get my any further unfortunately.Į.g., I get this: D:\Restore>C:\Users\Timo\AppData\Local\Duplicacy\duplicacy_win_圆4_2.0.9.exe -v list -a The repository_id can be found under the snapshots directory on the storage. On macOS, the Duplicacy CLI executable is usually under /Applications/Duplicacy.app/Contents/Resources. On Windows, the Duplicacy CLI executable can be found under either C:\Program Files (x86)\Duplicacy or C:\Users\username\AppData\Local\Duplicacy, depending on if you installed Duplicacy for all users or for the current user only. You can always use the CLI version to restore: mkdir -p path/to/restore/to
Please help me, I don't wont to mess around with my precious backup. The verbose log looks fine until this line: I tried the process with the GUI as you described but "List revisions" and "List files" results in nothing.
#DUPLICACY RESTORE FULL#
I got into the same situation to restore after a full crash, but unfortunately it does not work as intended! I really need my backup now. You can find it out by listing the snapshots directory in the storage. You can also restore using the CLI version by running the following commands: mkdir -p path/to/restore/toĭuplicacy restore -r n # n is the revision number that you want to restoreįor the init command you need the repository id of the original repository. Under the restore tab you can click list revisions and select the repository id of the original repository and then you will be able to list all files in the original repository and select them to restore.
Hi, i was just wondering what would be the procedure to restore a full backup after a system crash?įor the GUI version, you can create an empty directory on another computer as the repository and then select the same storage. All issues How to restore after full system crash