Sorry for begging your help, but reading a lot of threads concerning this problem, i was not able to find a solution for my Problem.
Trying to make a image backup of my Windows 10 Home client, i get this error message: Backing up System Reserved (SYSVOL) partition failed. Image backup failed
My Client OS: Windows 10 Home
My UrBackup Client: 2.1.14
My Urbackup Server: 2.0.38 (OMV PlugIn on a raspberrypi)
File backups are done well.
Output of client debug.log:
2017-02-26 17:50:35: ERROR: GetVolumeInformationW failed. Volume: ‘\?\Volume{1e27f41f-6c59-4c61-9b19-e4231fa714a0}’. Das Gerät ist nicht bereit. (code: 21)
2017-02-26 17:50:35: ERROR: Error reading data from device (\?\Volume{1e27f41f-6c59-4c61-9b19-e4231fa714a0}). Errorcode: 21
2017-02-26 17:50:35: ERROR: Opening filesystem on device failed. Stopping.
Output of sysvol_test.exe (run as adminsitrator):
… schnipp …
Found potential candidate: \?\Volume{65093a03-c2e0-4f1d-9e3b-dd094726e006}\ Score: 3
Selected volume \?\Volume{1e27f41f-6c59-4c61-9b19-e4231fa714a0}
Found sysvol “\?\Volume{1e27f41f-6c59-4c61-9b19-e4231fa714a0}” Path: “”
Trying to open SYSVOL(\?\Volume{1e27f41f-6c59-4c61-9b19-e4231fa714a0})…
Successfully opened SYSVOL.
System dir: C:\WINDOWS
Volpath: \.\C:
EFI partition with type UUID {DE94BBA4-06D1-4D40-A16A-BFD50179D6AC}
EFI partition with type UUID {C12A7328-F81F-11D2-BA4B-00A0C93EC93B}
EFI System Partition is at \?\GLOBALROOT\Device\Harddisk0\Partition2
Found EFI System Partition “\?\GLOBALROOT\Device\Harddisk0\Partition2” Path: “”
Trying to open EFI System Partition(\?\GLOBALROOT\Device\Harddisk0\Partition2)…
Successfully opened EFI System Partition.
Other Things I have already tried or proofed:
Disabling all virus scanners, firewalls, etc.
The Services “UrBackup Client Service for Backups” and “Volumeschattenlopie” are running and set to start modus “Automatisch”
Making several new installations of the urbackup client (different versions)
Here’s the complete output of sysvol_test.exe:
(I hope there are hints in it )
C:\Programme\urbackup>sysvol_test.exe
Filesystem. Vol="\?\Volume{47a56d4a-15f4-48e5-8150-4dd26db0dcb6}" Name=“ti31411800a” Type=“ntfs” VPaths=1 Size=985237073920
Filesystem is System partition. Skipping…
Filesystem. Vol="\?\Volume{1e27f41f-6c59-4c61-9b19-e4231fa714a0}" Name="" Type="" VPaths=0 Size=-1
GPT formated hard disk encountered. No bootable flag. Attributes = -9223372036854775807
Do not automount is set
System partition is set
Bootable flag set for volume
Found potential candidate: \?\Volume{1e27f41f-6c59-4c61-9b19-e4231fa714a0}\ Score: 3
Filesystem. Vol="\?\Volume{b64c0ba1-e206-412f-8ac7-5a42fb54dad0}" Name="" Type="" VPaths=0 Size=-1
GPT formated hard disk encountered. No bootable flag. Attributes = -9223372036854775807
Do not automount is set
System partition is set
Bootable flag set for volume
Found potential candidate: \?\Volume{b64c0ba1-e206-412f-8ac7-5a42fb54dad0}\ Score: 3
Filesystem. Vol="\?\Volume{65093a03-c2e0-4f1d-9e3b-dd094726e006}" Name="" Type="" VPaths=0 Size=-1
GPT formated hard disk encountered. No bootable flag. Attributes = -9223372036854775807
Do not automount is set
System partition is set
Bootable flag set for volume
Found potential candidate: \?\Volume{65093a03-c2e0-4f1d-9e3b-dd094726e006}\ Score: 3
Selected volume \?\Volume{1e27f41f-6c59-4c61-9b19-e4231fa714a0}
Found sysvol “\?\Volume{1e27f41f-6c59-4c61-9b19-e4231fa714a0}” Path: “”
Trying to open SYSVOL(\?\Volume{1e27f41f-6c59-4c61-9b19-e4231fa714a0})…
Successfully opened SYSVOL.
System dir: C:\WINDOWS
Volpath: \.\C:
EFI partition with type UUID {DE94BBA4-06D1-4D40-A16A-BFD50179D6AC}
EFI partition with type UUID {C12A7328-F81F-11D2-BA4B-00A0C93EC93B}
EFI System Partition is at \?\GLOBALROOT\Device\Harddisk0\Partition2
Found EFI System Partition “\?\GLOBALROOT\Device\Harddisk0\Partition2” Path: “”
Trying to open EFI System Partition(\?\GLOBALROOT\Device\Harddisk0\Partition2)…
Successfully opened EFI System Partition.
This issue is solved (only a small problem ist still remaining).
About two days ago a new update for the Client-Software was available: Client 2.1.15.
The image backup started without any problems. The image backup finished with success about 2 days later:
Starting unscheduled full image backup of volume “C:”… Transferred 294.786 GB - Average speed: 13.4993 MBit/s Time taken for backing up client xxxxxx: 2 days 4h 7m Backup succeeded
The small problem:
After ~ 48 hours I observed that the yellow symbol in system tray changed to red. The client status reported “untätig” (no activity).
But nevertheless the update was running and finished about 4 hours later with success.
Thanks very much for the new verison of the client software!!!