Thanks for getting back to me, when i go into gizmo and select mount image, and browse to my image backup, it shows nothing, i have file type as “all mountable files”, that shows even if i uncompress the image backup it still doesnt show.
I tried in disk manager, and went to attatch vhd, i selected the vhdz but it gave me the error
“A virtual Disk support provider for the specified file was not found”
Got around to investigating this. It is a bug which adds garbage after the complete decompressed content during decompression. UrBackup itself is able to still read the VHD-files and no data is lost as it falls back (according to Microsoft VHD specification) to reading the header if it cannot read the footer at the end of the file. The Microsoft VHD reader does not seem to have this fallback.
I will push an update with decompression being fixed.
Hey mate, i updated to the latest version, both on server and client, but still cant mount a .vhdx after uncompressing, i changed the name also to .vhd but still gives same errors
Hey mate, i updated to the latest version, both on server and client, but still cant mount a .vhdx after uncompressing, i changed the name also to .vhd but still gives same errors frowning
Hey mate, i updated to the latest version, both on server and client, but still cant mount a .vhdx after uncompressing, i changed the name also to .vhd but still gives same errors frowning
I cannot reproduce your issue. Are you sure the images are newly created compressed images? Can you give a few details? (incremental, full, size, does it work with Gizmo etc.)
You can also try decompressing with the new assemble_disk_image.bat tool.
Hey mate, sorry a little bit more info on the issue, im running a full backup, both client and server are running 1.4.9
i used uncompress_image.bat
once uncompressed i tried to attatch in disk management, same error, a virtual disk support provider for the specified file was not found
i tried the assemble_disk_image.bat but it said could not open .mbr file
sorry the file is vhdz, not vhdx, i also tried with Gizmo and was able to mount the drive by changing the file name to .vhd
but if i attatch the vhd to a vitrual machine it wont boot
Ok, can you make sure there is a Image_C_XXXXX.vhdz.mbr or Image_C_XXXXX.vhd.mbr in the same folder and then use assemble_disk_image.bat? That should make sure the image is bootable (± Windows driver issues).
Looking at one of them I think it is GPT formatted, which is not supported by 1.4.x. VHDs also have a maximum size of 2TB, a larger volume size could perhaps also explain the issues.