UrBackup stores each volume of an image backup separately. If you want to boot an image backup, without using the restore CD, as an virtual machine you have to re-assemble multiple volumes into one disk VHD image. On Windows this can be done by running C:\Program Files\UrBackupServer\assemble_disk_image.bat. In a first step it will ask for the VHD images to assemble. Select e.g. Image_C_XXXXX.vhd and Image_SYSVOL_XXXXX.vhd. The source images can also be incremental or compressed. Then it will ask where the output VHD disk image should be saved. After that it will write the master boot record from Image_C_XXXXX.vhd.mbr and the contents of the volumes into the output disk image at the appropriate offsets.
On Linux the same thing can be done with
urbackupsrv -a /full/path/Image_C_XXXXX.vhdz -a /full/path/Image_SYSVOL_XXXXX.vhdz\
-o full_disk.vhd
This tool can also be used to decompress images without decompressing their parents by selecting a single VHD file as input.
Because I don’t personally use this, it has been buggy in the past.
Does it make any difference if I put the SYSVOL first and image_C second (in the command line)? Would this determine the order of the partition in the “rebuild” disk?