Backup error, could not open output file

1

The server records the following error

Error saving metadata. Could not open output file at “/media/raid/backups/urbackup/Sonnys-Laptop/170502-1810/.hashes/C/Program Files/WindowsApps/Microsoft.MicrosoftOfficeHub_17.8010.5926.0_x64__8wekyb3d8bbwe/VFS/ProgramFilesCommonX64/Microsoft Shared/OFFICE16/1033”

I’ve seen several clients complain about the same filepath, not just this one.

Any insights into why MicrosoftOfficeHub hates urbackup?

2

Hmm, yeah, have seen the same issue with one Windows 10 client. What would be consistent with this error would be the directory being a reparse point but not a symbolic link or junction. Maybe you can check?

3

You mean the directory on the client?

Or the directory on the server? The server is Linux, btrfs filesystem.

How can I check if it’s a reparse point?

4

Directory on the client fsutil reparsepoint query 1033

5

I’m getting the same error for

C:\Users[User]\appdata\Local\Packages\Microsoft.Microsoft3DViewer_8wekyb3d8bbwe\LocalCache

and can confirm that this is a reparse point.

6

Could you post the full output please?

7

C:\Users\[User]>fsutil reparsepoint query C:\Users\[User]\appdata\Local\Packages\Microsoft.Microsoft3DViewer_8wekyb3d8bbwe\LocalCache
Reparse Tag Value : 0x80000018
Tag value: Microsoft

Reparse Data Length: 0x0000001a
Reparse Data:
0000: 01 00 00 00 00 00 00 00 d7 06 3a 57 8a 11 69 4c …:W…iL
0010: bf 5a c4 65 b2 06 ff 88 00 00 .Z.e…

8

Could you try if this fixes it: https://www.urbackup.org/downloads/Client/2.1.16/

9

After installing that client I don’t seem to be getting any backups at all.

It says it’s been successful but no files have been copied and it completes in around 20 seconds.

This is in Internet mode (no idea if that’d make any difference) as this is on my work laptop which I take home with me. I’m not going to be back in the office for 2 weeks in order to test on local connection.

10

Yeah, sorry. I updated it in place and it shouldn’t break completely now.

11

Downloaded… Installed… Now just waiting for a backup to complete…

I’ll hopefully be back to you with some news in the morning.

12

First backup with new version completed.

No error.

13

Did anyone successfully test the 2.1.16 client?

14

Yes. Looks to be working without the error now.