I am trying out the new image assembly feature with urbackup server and have image backups of systems running Windows 2003, 2008 and 2012. All backups run fine without errors.
Assembly of images created from Windows 2008 and 2012 were great and the newly assembled vhds work as expected.
The problem only comes in when I tried to do the same for the image backups of Windows 2003. After running the image assembling batch file, the resulting vhd becomes corrupted. When i tried to mount it under Windows disk management, it is asking to format the disk instead of allowing direct access to the files inside.
After some assessment, here are some findings on the differences in the created images:
Windows 2008 and 2012 are running 64bit whereas Windows 2003 are 32bit. Urbackup server is 64bit running on a 64bit OS - Can 64bit server assemble an image created from 32bit version of urbackup client?
Backups for Windows 2008 and above come with sysvol. Both the sysvol and c_vol images were selected for the assembly. Whereas for Windows 2003, only the c_vol image were selected since there is no sysvol - Will this cause a problem?
Image is captured from an IBM x3650 server if there is going to make a difference.
By the way, just to add that all images captured are compressed by default to VHDZ. The Windows 2003 VHD only becomes corrupted when I tried to make it bootable by using the assembling batch file. If I simply uncompress the VHDZ, the resulting VHD works fine and I am able to mount in correctly in Windows Disk Management - the only problem here though is that the VHD will not be bootable if I simply uncompress it as the mbr is not present.
So it seems that the mbr file is causing the VHD to become corrupted after assembly. Is there a way we can manually recreate this mbr?
I took my Windows XP vhdz and assembled it with your mbr and it mounted, so it must be something else. The Partition size is not divisible by the cluster size (4096). I think this is unusual. Was this partition converted from FAT32?