Hi, same issue with restoring a smaller (120Gb PC), going to change that setting to VHD, back it up then try and restore that to see if its a VHDX issue.
UPDATE
Looks like an issue with the VHDX store, we changed a small PC (150Gb) from VHDX Compressed to to VHD compressed), then run an incrementable image backup. When completed, booted the recovery USB on a separate system (the one used thats failing earlier), started a complete image recovery of the one just backed up, it completed ok (GREEN TICK)…
I believe VHD will not backup over 2Tb, the only way to backup volumes above 2Tb is to use VHDX, from what i see, looks like we cant recover those systems.
I’m able to reproduce a problem. It seems to be vhdx in combination with the compression.
The data is still there, it is (just) the mapping that has issues, so this might be recoverable, though it would be some effort.
Hi, this raises 3 questions…
- Is there going to be a fix moving forward using VHDx with compression that will fix those containers (that are currently in use that are live)
- How would i recover this one system that stopped backing up thats is using the current VHDx compressed container?
- Should we stop using VHDx with compression until a fix is seen?
I assume server v2.5.35 is the fix for the VHDX, was there issues with both Compressed and non compressed VHDX file store methods?
Will i bet able to restore my backup that was VHDX compressed before this version if i upgrade the server as i still need to restore that PC
Yeah.
Restoring your corrupted VHDXZ is currently not possible. As said the data is there, but it also has some garbage pointers which would need to be ignored via some heuristic.