I’m trying to restore an image. The image is an incremental one based on an incremental based on a full. I used the restore cd but when I select the newest image only the incremental get’s restored resulting in a nonfunctional state. In my understanding the sever shound not just deliver the newest delta but a “full” image consisting of full+delta1+delta2. Or is the way to restore the full, then delta1 and then delta2 manually?
I tried again and this time set the imagetype to vhdz, not vhdx as in my previous test. This time it worked as i was expecting. Is there a bug in the vhdx handling?
I used vhdx because of the vhd size limit of 2TB. Does this apply to vhdz in UrBackup as well? If not I would just use vhdz and problem would be solved.
I was using vhdx when taking the full and two incremental images. With these the restore of the incremental images wasn’t working. After switching to vhdz I took a full and the an incremental image. With these I could restore the incremental image without problem.
It seem there is a problem with vhdx, at least in my case.
Is there a downside to vhdz? Like a 2TB barrier like with standard vhd?
So it is not the known vhdxz issue with server version <2.5.35. For looking into a potential vhdx issue your posts do not contain enough information.
In my testing with vhdx(z) it obviously worked.