Can't access path to backup VolumeShadowCopy

[ttrammell]

@jonesmz

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

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

@jonesmz

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.

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:

@uroni

Log files

The server log file is per default located at C:\Program files\UrBackupServer\urbackup.log. Change warn to debug in C:\Program files\UrBackupServer\args.txt to create a debug log file. Debug log files are preferred. The log file on Linux/FreeBSD is located per default at /var/log/urbackup.log. The log level is an argument to the server program (urbackupsrv run -v debug) or can be configured via /etc/default/urbackupsrv or /etc/sysconfig/urbackupsrv.

The client log file is per default located at C:\Program Files\UrBackup\debug.log on Windows. Run C:\Program Files\UrBackup\enable_debug_logging.bat as admin to enable debug logging. On Linux/FreeBSD the client log file is located at /var/log/urbackupclient.log. To enable debug logging run the backend with urbackupclientbackend -v debug or it can be configured via /etc/default/urbackupclient or /etc/sysconfig/urbackupclient.

Attach the log files to your new post or send them to bugreports@urbackup.org, because they may contain data which should not be public.