New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows backup - error: invalid node type "" #4560
Comments
Seeing this as well and just came into report. Rolling back and the error goes away. Windows Server 2012R2 (don't ask). |
Same here - problem appeared when upgraded restic from 0.15.2 to 0.16.1. |
Same for me, I'm using Restic 0.16.2. |
Same here, problem appeared after upgrading from 0.15.2 to 0.16.2 |
Same |
The error seems to be caused by files that are reported as Trying to access these files (via WSL, Explorer and notepad++) results in errors, self contradicting results. However, its apparently possible to execute those files. I don't know enough about Windows to say whether its possible in some way to backup those files and what magic would be necessary to attempt restoring those files. From what I can tell so far, it likely won't be possible to back up these files (Didn't work either in previous restic versions). But at least we can fix the error message to be more useful. Te proper solution, however, is likely to just exclude the |
I saw warnings about files with absolute paths in the log being unable to backup under WSL being symlinks when using version <=0.15.2 of restic. I suspect that in 0.16.2 they are the same type of files (symlinks under WSL), but are just reported with an empty string instead of an absolute path like before. |
Same here on 0.16.2 |
Same here, also on 0.16.2 but on Fedora 39 |
#4620 will fix the error message to include the filepath, but besides that there's probably not much we can do here. |
Output of
restic version
What backend/service did you use to store the repository?
REST server: https://github.com/restic/rest-server
Problem description / Steps to reproduce
As described in the Forum:
When running a backup on Windows 11 with:
I get the following output (truncated a bit):
Same result as unprivileged user without --use-fs-snapshot option. Machine is a Windows 11 virtual machine.
Expected behavior
Return without error
Actual behavior
Without
--json
, the error messages (one per unreadable file) iswhich is not helpful for identifying what's wrong. The backup succeeds nontheless, which is good!
Do you have any idea what may have caused this?
nope :/
Did restic help you today? Did it make you happy in any way?
Oh dear, it helps almost every day!
It's just being way less nervous about day-to-day sysadmin stuff, because there's always a restic backup there, just in case.
The text was updated successfully, but these errors were encountered: