Backing up System Reserved (SYSVOL) partition failed. Image backup failed

client
1

First of all, thanks for creating this software. The combination of file and image backups, windows and linux support, incremental and full backups, all making the best possible use of the native OS features is really great and something I haven’t seen anywhere else.

Today I have tried to install UrBackup on my Windows 10 tablet. Unfortunately the image backups don’t work. I have tested client version 2.1.16 and the 2.2.2 beta, with server version 2.1.9.

The backup fails with error message “Backing up System Reserved (SYSVOL) partition failed. Image backup failed”.

Just before this happens, the debug log shows:

2017-08-16 18:44:06: ClientService cmd: #IHmRm75gZDQVVt4FXNH3v#FULL IMAGE letter=SYSVOL&token=O373sNLh4Xwufb9YIcrQ&bitmap=1&status_id=51&running_jobs=1
2017-08-16 18:44:06: ERROR: Error reading data from device (\\?\Volume{6800d510-b9da-4963-a054-d781c54f6382}). Errorcode: 87
2017-08-16 18:44:06: ERROR: Opening filesystem on device failed. Stopping.
2017-08-16 18:44:06: Device file: "\\?\Volume{6800d510-b9da-4963-a054-d781c54f6382}"

During startup it lists the discovered filesystems:

2017-08-16 18:43:52: urbackupserver: Server started up successfully!
2017-08-16 18:43:52: FileSrv: Backup privileges set successfully
2017-08-16 18:43:52: FileSrv: Backup privileges set successfully (SE_SECURITY_NAME)
2017-08-16 18:43:52: FileSrv: Backup privileges set successfully (SE_RESTORE_NAME)
2017-08-16 18:43:52: FileSrv: Server started up successfully
2017-08-16 18:43:52: Started UrBackupClient Backend...
2017-08-16 18:43:52: Filesystem. Vol="\\?\Volume{1d459ca0-7b12-4212-a6fb-33f7c3a2d883}\" Name="os" Type="ntfs" VPaths=1 Size=52770631680
2017-08-16 18:43:52: Filesystem is System partition. Skipping...
2017-08-16 18:43:52: Filesystem. Vol="\\?\Volume{705334e6-2374-11e6-957a-806e6f6e6963}\" Name="data2" Type="ntfs" VPaths=2 Size=63847788544
2017-08-16 18:43:52: Bootable flag not set for volume
2017-08-16 18:43:52: Filesystem. Vol="\\?\Volume{6800d510-b9da-4963-a054-d781c54f6382}\" Name="recovery" Type="ntfs" VPaths=0 Size=943714304
2017-08-16 18:43:52: GPT formated hard disk encountered. No bootable flag. Attributes = -9223372036854775807
2017-08-16 18:43:52: Do not automount is set
2017-08-16 18:43:52: System partition is set
2017-08-16 18:43:52: Bootable flag set for volume
2017-08-16 18:43:52: Found potential candidate: \\?\Volume{6800d510-b9da-4963-a054-d781c54f6382}\ Score: 3
2017-08-16 18:43:52: Filesystem. Vol="\\?\Volume{dad27528-5f1d-4a57-a503-ce789a9da68d}\" Name="restore" Type="ntfs" VPaths=0 Size=8589930496
2017-08-16 18:43:52: GPT formated hard disk encountered. No bootable flag. Attributes = -9223372036854775807
2017-08-16 18:43:52: Do not automount is set
2017-08-16 18:43:52: System partition is set
2017-08-16 18:43:52: Bootable flag set for volume
2017-08-16 18:43:52: Found potential candidate: \\?\Volume{dad27528-5f1d-4a57-a503-ce789a9da68d}\ Score: 3
2017-08-16 18:43:52: Selected volume \\?\Volume{6800d510-b9da-4963-a054-d781c54f6382}
2017-08-16 18:43:52: System dir: C:\WINDOWS
2017-08-16 18:43:52: Volpath: \\.\C:
2017-08-16 18:43:52: EFI partition with type UUID {C12A7328-F81F-11D2-BA4B-00A0C93EC93B}
2017-08-16 18:43:52: EFI System Partition is at \\?\GLOBALROOT\Device\Harddisk0\Partition1

I am not really sure what UrBackup is looking for when talking about SYSVOL, but in my case it seems to find some kind of manufacturer recovery partition (“recovery”). “os” is the primary parition (C:) which contains the OS and data files (only partition to be backed up in image mode), data2 is an SD card (backed up in file mode for now), “recovery” and “restore” probably contain recovery data from the manufacturer or Windows.

Can I disable backing up the SYSVOL partition, or can I get UrBackup to ignore the recovery partitions somehow? I could not find a conclusive answer in the forums regarding this (or similar) issues.

2

Could be it needs to read 4096 bytes at a time. Could you post the output of fsutil fsinfo ntfsinfo C: ?

3 
NTFS Volume Serial Number :        0x6c74d7c574d78fe6
NTFS Version   :                   3.1
LFS Version    :                   2.0
Number Sectors :                   0x000000000624afff
Total Clusters :                   0x0000000000c495ff
Free Clusters  :                   0x0000000000411546
Total Reserved :                   0x0000000000007b77
Bytes Per Sector  :                512
Bytes Per Physical Sector :        4096
Bytes Per Cluster :                4096
Bytes Per FileRecord Segment    :  1024
Clusters Per FileRecord Segment :  0
Mft Valid Data Length :            0x0000000011ac0000
Mft Start Lcn  :                   0x00000000000c0000
Mft2 Start Lcn :                   0x0000000000000002
Mft Zone Start :                   0x00000000003d6760
Mft Zone End   :                   0x00000000003d9de0
Max Device Trim Extent Count :     1
Max Device Trim Byte Count :       0x8000000
Max Volume Trim Extent Count :     1
Max Volume Trim Byte Count :       0x8000000
Resource Manager Identifier :     A1303D45-DA0D-11E3-8F22-6868680079C9

Just for completeness:

C:\WINDOWS\system32>fsutil fsinfo ntfsinfo e:
NTFS Volume Serial Number :        0x14a43ef1a43ed548
NTFS Version   :                   3.1
LFS Version    :                   1.1
Number Sectors :                   0x00000000076ecfff
Total Clusters :                   0x0000000000edd9ff
Free Clusters  :                   0x00000000008c7963
Total Reserved :                   0x0000000000002420
Bytes Per Sector  :                512
Bytes Per Physical Sector :        4096
Bytes Per Cluster :                4096
Bytes Per FileRecord Segment    :  1024
Clusters Per FileRecord Segment :  0
Mft Valid Data Length :            0x0000000000b40000
Mft Start Lcn  :                   0x00000000000c0000
Mft2 Start Lcn :                   0x0000000000000002
Mft Zone Start :                   0x00000000000c0b40
Mft Zone End   :                   0x00000000000cc820
Max Device Trim Extent Count :     0
Max Device Trim Byte Count :       0x0
Max Volume Trim Extent Count :     62
Max Volume Trim Byte Count :       0x40000000
Resource Manager Identifier :     160A3A19-3FF1-11E4-9732-D3C8F34A274D

I don’t know if this is relevant, but I think ?\Volume{6800d510-b9da-4963-a054-d781c54f6382} is some manufacturer recovery partition, not C:

4

Your specific installation is weird, but newer Windows versions have a separate boot partition (from which e.g. the boot recovery starts) and it tries to backup that one.

See here: https://superuser.com/a/915724/89138

You seem to have that mentioned AF 4Kn disk. Congrats, seems you are one of the first ones :wink:

5

Good to know I did not miss anything in other forum posts. I did upgrade this one from Windows 8.1 to Windows 10. The missing partition may have something to do with the upgrade, or with the fact that it’s a tablet (Asus Transformer T100TA) with a relatively small SSD drive (and ASUS not wanting to “lose” another GB). The current partition layout is: 100MB EFI, 900MB recovery, 49GB OS/data, 8GB recovery (in that order).

6

Hello Guys,

did you find any solution for your problem.

I think i have the same problem with my 32 bit windows 10 tablet.

7

You probably don’t have the same problem.

8

Hey guys,
i have exactly the same problem, also with an old Windows 10 32 bit tablet.
Sorry for adding to an such old post. But the issue is the same!

Here is the log:

|Info|26.04.23 21:04|Starting unscheduled full image backup of volume "C:"...|
|Fehler|26.04.23 21:04|Backing up System Reserved (SYSVOL) partition failed. Image backup failed|
|Info|26.04.23 21:04|Time taken for backing up client Dintis-Tablet: 1s|
|Fehler|26.04.23 21:04|Backup failed|

I have this partition layout:
image

Which is the sames mentioned here on Windows 10 legacy/BIOS boot: partitioning - What is this Recovery Partition for on a fresh installation of Windows? - Super User

image

So it seems my partition layout is correct.

Sholdn’t SYSVOL be skipped on those systems?
Any hints how i can exclude the SYSVOL or solve this issue in another way?

thx