Full volume backup of win10 C fails (SYSVOL error)

Hi all!

When I try to backup volume C of my windows 10 pro machine it fails. I tried another drive/volume (D) earlier and that worked.

The server version is " UrBackup 2.4.13", running on a ubuntu server 20.04.3 LTS. The client is “2.4.11” running on a win 10 pro.

Any ideas??

Its a nice tool, but I only selected it because of the advertised windows C: full-image backup capability!

FYI from the error logs:

Server log:
|11/08/21 12:10 |INFO |Starting scheduled full image backup of volume SYSVOL…|
|11/08/21 12:10 |WARNING |Request of SYSVOL failed. Reason: Creating shadow copy failed. See client log file for details.|
|11/08/21 12:10 |INFO |Transferred 869 bytes - Average speed: 2.328 KBit/s|
|11/08/21 12:10 |DEBUG |Script does not exist urbackup/post_full_imagebackup|
|11/08/21 12:10 |ERROR |Backing up System Reserved (SYSVOL) partition failed. Image backup failed|
|11/08/21 12:10 |INFO |Time taken for backing up client HPENVY: 4s|
|11/08/21 12:10 |ERROR |Backup failed|
|11/08/21 12:10 |DEBUG |Getting client settings…|
|11/08/21 12:10 |WARNING |Exponential backoff: Waiting at least 40m before next image backup|

Client interface log:
Starting scheduled full image backup of volume “C:”…
Backing up System Reserved (SYSVOL) partition failed. Image backup failed
Time taken for backing up client HPENVY: 4s
Backup failed

Client - Debug log
2021-11-08 12:10:55: ERROR: backupcom->AddToSnapshotSet(&(Server->ConvertToWchar(selected_vols[i])[0]), GUID_NULL, &additional_refs[i].volid) failed. VSS error code VSS_E_VOLUME_NOT_SUPPORTED
2021-11-08 12:10:55: ERROR: Creating shadowcopy of “Z:” failed.
2021-11-08 12:10:55: ERROR: Creating shadow copy failed. See client log file for details.

It looks as though you have more than drive C: being backed up.

The debug log seems to mention an E: volume.

Are there any Windows Event Log errors pertaining to VSS?

What edition of Windows are you running? (Build # and also 32 vs 64 bit)

-ASB

For some freakish reason, a registry entry pointing to the Bootdir, was pointing to a non-existent drive Z:. I corrected that to point to drive C: and now it works!

Thanks for looking into it anyhow!

3 Likes

Thanks for letting us know the issue has been solved.