Can't access path to backup VolumeShadowCopy


#1

Debug.log

2016-12-03 18:38:52: ERROR: Could not open path in os_get_final_path for "C:*"
2016-12-03 18:38:53: WARNING: Info not found at ‘c:’ - reindexing
2016-12-03 18:39:10: ERROR: Recvfrom error in CUDPThread::UdpStep
2016-12-03 18:39:10: ERROR: Last error: 10058
2016-12-03 18:39:10: ERROR: Could not open path in os_get_final_path for "C:*"
2016-12-03 18:40:00: ERROR: Recvfrom error in CUDPThread::UdpStep
2016-12-03 18:40:00: ERROR: Last error: 10058
2016-12-03 18:40:00: ERROR: Could not open path in os_get_final_path for "C:*"
2016-12-03 18:40:00: ERROR: Could not open path in os_get_final_path for "C:*"
2016-12-03 18:40:01: ERROR: Could not open path in os_get_final_path for "C:*"
2016-12-03 18:40:39: ERROR: Cannot access path to backup: “\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy2*” Errorcode: 123 - The filename, directory name, or volume label syntax is incorrect.
2016-12-03 18:44:10: ERROR: Could not open path in os_get_final_path for "C:*"
2016-12-03 18:44:10: ERROR: Could not open path in os_get_final_path for "C:*"
2016-12-03 18:44:40: ERROR: Cannot access path to backup: “\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy3*” Errorcode: 123 - The filename, directory name, or volume label syntax is incorrect.

Urbackup livelog:

12/03/16 18:44 DEBUG Leslies-Laptop: Connecting for filelist…
12/03/16 18:44 DEBUG Leslies-Laptop: Waiting for filelist
12/03/16 18:44 ERROR Cannot access path to backup: “\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy3*” Errorcode: 123 - The filename, directory name, or volume label syntax is incorrect.
12/03/16 18:44 ERROR Constructing of filelist of “Leslies-Laptop” failed: error - index error
12/03/16 18:44 ERROR Backup had an early error. Deleting partial backup.


#2

Windows 10, Anniversary update, 64bit

Server: Gentoo, Hardened 64bit.
Urbackup server compiled from source,
http s://github.com/uroni/urbackup_backend/commit/85153c77716bb75e76571e6702921f8dc725188b

Using the ebuild that I attached to this bug report: https://bugs.gentoo.org/show_bug.cgi?id=596870

Client, 64bit MSI downloaded from:
http s://www.urbackup.org/download.html#client_windows
http s://hndl.urbackup.org/Client/2.0.36/UrBackup%20Client%202.0.36%28x64%29.msi

Uninstalled, reinstalled, deleted Urbackup related files in Program Files\Urbackup, and AppData/Local

Also, how is “Cannot access path to backup: “\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy2*” Errorcode: 123” an Invalid title?!?!?! What the heck Discourse!?


#3

And only two links per post? Wow, how frustrating.


#4

Yeah, that’s a little problematic; however, once you become a basic user that restriction is lifted, I believe.

This is probably obvious, but it is having trouble mapping the C: drive; are you backing up more than just Leslies-Laptop?

If you are, and are not having any trouble with any of your other clients then it’s a client-side issue; things like your service isn’t running; something isn’t up to date; 8dot3 names (although I think that really only affects UrBackup Windows Servers).

Uroni could probably help more, but you may want to follow this:


#5

I disagree with the 8.3 names because I have this problem on only 1 client. I couldn’t backup a folder on a Windows 7 users desktop but if I moved that same exact folder to the root of the C drive I could back it up there (or at least 1 full and 1 incr). now I started getting the same error again. I’m not really sure what the problem is. The wierd thing is that the folder I’m backing up is C:\backup and in the error message it shows program files path but I’m not backing it up nor do I want to. I should also add that I am using an Ubuntu server 14.04 LTS running urbackup 2.1.19 and the client is Windows 7 x64 Home Premium 2.1.15

2017-03-10 21:41:39(error): Cannot access path to backup: “\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy73\program files (x86)\m1-sk\teamworks\manager\data” Errorcode: 123 - The filename, directory name, or volume label syntax is incorrect.


#6

I’ve apparently resolved the issue by upgrading the the latest release now that it’s out of beta.


#7

I’m already on the latest version of both client and server. Has anyone confirmed that it’s a bug or if it’s something that can be worked around?


#8

I uninstalled the client, deleted the client from the server, added the client again and a full backup worked. Time will tell if this does me any good. I’ll post results if anyone cares. If I can get 2 incremental backups, this would be a success in my opinion.