Spent nine hours trying to recover a set of two NTFS partitions from a VHDX file that was the result of a Veeam Hyper-V backup.

Let me tell you, this SUCKED. Veeam gives a SHIT about recoverability; because their backups are ACTUALLY only mimicking the real deal; p1 and p2 are fake. p1 stores rough metadata while p2 is a somewhat compressed/encrypted blob of whateverthefuck and no amount of testdisk, badblocks, fdisk, gdisk, parted, chkdsk, ntfs-3g tools and the likes was able to get anywhere. Hell, I even re-aligned p1 because it was at offset 33, so I knocked it down to 32 and also aligned p2.

This has caused me literal headache and frustrated screams. This propeitary crap is fucking annoying and drives me mad... can't believe we deploy this at like 30+ customers. X.x

Even my eye hurts from sifting through partition tables, offsets, rescue logs and what not... i tried literally everything I had in my books for this. Bah.

Reply to this note

Please Login to reply.

Discussion

I had never heard of Veeam, sounds painful

tl;dr: "Veeam Backup & Rescue" is both a free and enterprise solution to build a backup solution; local, cloud - local, offsite... there are parts that use Kopia (FOSS backup tool) too. However, as it also handles things like virtual disks and other crap, they probably couldnt help themselves - and so, Veeam is effectively an ecosystem you buy into...literally.

So yes - it IS bad. xD