-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Windows: Symlinks are not backuped #2699
Copy link
Copy link
Closed
Labels
category: restoreplatform: windowsstate: need implementingcause/request established, need work/solutioncause/request established, need work/solutiontype: bug
Description
Output of restic version
restic 0.9.6 compiled with go1.13.4 on windows/amd64
How did you run restic exactly?
1. restic -r symlinktest init
2. restic -r symlinktest backup resticsymlinktest
This prints
repository 17418abd opened successfully, password is correct
created new cache in C:\Users\JsBerbau\AppData\Local\restic
Files: 1 new, 0 changed, 0 unmodified
Dirs: 0 new, 0 changed, 0 unmodified
Added to the repo: 343 B
processed 1 files, 31 B in 0:00
snapshot 5f283900 saved
The folder resticsymlinktest contained:
File.txt containing
Hallo,
I'm the "real" testfile
A symlink to that file, created via
mklink link File.txt
Tested restore via
restic -r symlinktest restore -t resticsymlinkrestoretest latest
Only 1 file was restored, missing the symlink.
What backend/server/service did you use to store the repository?
Filesystem
Expected behavior
The symlink file is included in the backup and restored when restoring.
Actual behavior
Symlinkfile is not added to backup and thus also not restored.
Steps to reproduce the behavior
See above
Do you have any idea what may have caused this?
No
Do you have an idea how to solve the issue?
Include symlink files into backup and restore them
Did restic help you today? Did it make you happy in any way?
Restic is a very great tool and I hope that symlinks are also restored. Then I'm calm that the backup contains all my files and I can recover everything in case of a disaster.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
category: restoreplatform: windowsstate: need implementingcause/request established, need work/solutioncause/request established, need work/solutiontype: bug