Restore fail mkdir folder and restoring

Question

Restore fail mkdir folder and restoring

Closed this issue 5 months ago · 5 comments

Note: if you have a question or need support please post in the discussions area.

Describe the bug
Hello Tried on Windows Server backup on QNAP.
Backup always perfect,
restore a nightmare.

"mkdir \\?\d:\restic-restore-2024-04-24T16-35-32\D\D:: The filename, directory name, or volume label syntax is incorrect."
mkdir write this piece of folders and sub \\?\d:\restic-restore-2024-04-24T16-35-32\D, then it lost the rest
and obliously the files

I'm afraid you got this error => D\D::

In my opinion there is a double root

Platform Info
Windows Server 2022 Over QNAP

Backrest Version [e.g. 0.15.1]

Additional context
Thank You

Answer 1 · 2024-04-24T21:32:36.000Z

Hey, what does the structure of the item you're restoring look like in the snapshot browser? Is this a backup that was created with Backrest?

The format of the path that I'm seeing passed to restic looks pretty strange, do you also see a double root while browsing the backup? Where is the ./ in ./test coming from? Is it visible when browsing in the UI?

Backrest 0.15.1 is also quite old. You might try a more recent release.

Answer 2 · 2024-04-24T21:56:48.000Z

Hello. Yes, i can See a double root browsing the backup. D without colums and D: just below, then all the structure correctly disposed. I'll give a try to the new version but I was quite sure to have download the current one from github. Ho can i make an in place update? Thank you for your support. Inviato da Outlook per Android

Answer 3 · 2024-04-25T04:12:11.000Z

Just tested on my Windows install and top level directories for snapshots created using Backrest look like

and these seem to restore correctly.

Did you make your snapshots with Backrest? If you did, can you provide details about how you've configured it? It might also be interesting to see the output of restic ls for the top few directories of your repo (make sure to anonymize this as it will contain paths from your backed up dataset).'

How can I update

You'll want to stop your running backrest instance, then delete the installed binary and replace it with the latest version. Right now there isn't an updater / installer for Windows but this is something I'm interested in adding in the future.

Answer 4 · 2024-04-28T10:34:26.000Z

Ok found the error I formerly put in PLANS the D: folder in PATHS, and it caused the double D Now I've changed the D: in D:\ (with shlash at the end) and it works perfectly both indicating the repository and recovering files (better to put in the KB, I suggest) Thank you for your support ! Just a couple of question. 1. Is there a method to update in place the version of backrest? 2. Setting up the REPOS I noticed that there is Just the password to login and not the password. Who is the user of this passoword ? In another environment I've put the password of "admin" of the user but after few days it stopped working, stating Fatal: unable to open repository at //192.168.1.10/RESTIC: ReadDir: open \\?\UNC\192.168.1.10\RESTIC\keys: Nome utente o password non corretta. translating: username or password incorrect. But the UNC is correct and the also password for the admin user Any clue ? thank you

Answer 5 · 2024-04-29T04:18:28.000Z

Hey, I went ahead and edited your comment to snip out some email / phone number info you're leaking when replying with the email client -- please take care with how you've set that up with github as your footer is getting included in replies!

Re: the question,

there is not any inplace update support for backrest on Windows at the moment, upgrades are manual. #163 is tracking possibly creating a windows updater.
re passwords I think you're talking about the UI password vs the repository password. The password on the UI protects access to your Backrest installation. The password on the repo is an encryption key which protects your data in storage, this key must be backed up somewhere safe for you to be able to restore your data. Make sure you have it written down :)
Re: access to the repository, it looks like you're accessing a NAS mount which became unavailable? Afraid I don't have much knowledge re: how smb / nfs mounts should work on windows so this will need some debugging on your end, Backrest requires your backup locations to be accessible.