Thank you.
I got some ideas and I'm using Disk2vhd as well as WindowsBackup for restoring such tens of TB partitions.
I'll take a look to your tool from time to time.

PS: Sorry to respond late: I was on holidays

Hi, Sad to say again same results: VHDX successfully terminated and mountable,but 4/5 partitions not just one and all of them unreadable. Here's the log file, as you can see in the end it wasn't that faster either. Manuel F. The log file name: 'logs\V2V_Log-20210712-173557.log' (PID 15976) 7/12 17:3...

Thanks Yaroslav,
It'll take some days, but for now I can say it looks faster.
Manuel F.

Hi, If you mean the block size it's the Windows formatting default for an under-16TB partition (F:) Here is the truncated log. I didn't mention it because there's nothing relevant in those 5 days. Thank you, Manuel The log file name: 'logs\V2V_Log-20210610-134628.log' (PID 19676) 6/10 13:46:28.297 2...

Hi Yaroslav After 5 days, it finished again with no errors but this time the VHDX had again not one (like in the successful small partition K: I did for testing) but several partitions, and none of them valid NTFS replica of the original F: (seen in the first screenshot). Let me know what we can do ...

Thanks for the update. Please keep me posted. Also, if the conversion does not go for some reason or there is any other trouble, collect the logs and share them here. It's taking much longer than expected (3 or 4 times that of Disk2VHD) using just 0.3 Gbps. The size looks good for now and seems it'...

Hi, Have just resent that link. Thanks Yaroslav. I got it and I'm already testing it. The results for now are the following: W2012R2 (HP): I succeeded creating a valid and mountable VHDX from an small test partition that belongs to a 75TB RAID6 Physical Disk. With that I have just started the same ...

Sorry Yaroslav, but I cannot find it this time on my PM Inbox

No worries

yaroslav (staff) wrote:Hi,
We are still working on a custom build for you. WIll keep you posted.

Thank you Yaroslav.
Take your time: I have a lot of other tasks with the new server ....

Of course the most important thing is that the VHDX which contains the only partition I'm interested can be mountable (now it's not because the other "empty" partitions make the VHDX bigger than 64TB). Secondary would be not to "dehydrate" the partition if it's deduplicated. Thanks

No, no errors at all.
Just what I said: Deduplication is not kept judging by the bigger size of the resulting file compared to the partition being backed up. Also the VHDX cannot be mounted due to the fact , I guess, it contains all the partitions and not just the target one.

Hi Yaroslav, The latest build that you provided me finished well without errors but: 1) The resulting file is dehydrated if the "physical" partition is deduplicated, so it may be much bigger (28TB) than the original (20TB) 2) I cannot mount the resultant VHDX in our case, so it's not valid...

Hi Yaroslav,
Have you been able to reproduce the issue?
Thanks

Thanks Jaroslaw, here you are. This log example is on another machine and the new NTFS test partition to convert is just 1GB with no drive letter assigned (the whole RAID6 being 65TB). The destination storage is local this time (D:) One more hint: Disk2VHD creates the VHDX but cannot be opened (size...