If 69686263808 (corrected that) is exacly the size of the partition then this is probably not the cause of the error. (It’s about 65GB.) And if you use only 60-70% of space on the drive.
What might be interesting:
Do you have two Windows partitions, one of them the system restore partition? If yes, did UrBackup correctly backup both partitions, and correctly restore both of them?
Do you have a MBR parititon table. You could send me the .mbr file of the image you are restoring (firstname.lastname@example.org). Then I can confirm that.
Was the volume backed up and restored correctly? If you are able to, you could try to mount the restored volume in linux (e.g. in the restore cd Debian). You could also confirm if the created vhd is correct, by mounting it in Windows . See FAQ entry “I want to extract a file from the image backups. How do I do that?” http://www.urbackup.org/FAQ.php?lang=en
[quote=“zidvbelju”]EDIT- I just noticed that 2 MBR files are being created during the backup, Image_C and Image_SYSVOL.
Is that how it should be? There should have only been a single partition on the virtual disk.[/quote]
I can see in the file you sent me, that you have a restore partition. UrBackup needs to backup and restore that one, otherwise it won’t boot. Is there a Image_SYSVOL*.vhd as well?
I tried it with system recovery partition and WIP3 and it worked for me.
What happend though, was that it did not manage to backup the system recovery partition, i.e., there is a bug in 1.1.1. I fixed that now in 1.1.2RC. Are you sure you have both the SYSVOL_.vhd and SYSVOL_.mbr for the recovery partition with a time stamp fitting to the volume you want to restore?