Feature request: Move ReFS block cloned backup chains between extents without rehydration

[billcouper]

Microsoft in their infinite wisdom seem to have decided they don't really care about ReFS or developing it into a functional and supportable file system.
Case in point, they still don't have a way to easily identify how much of the raw underlying capacity block-cloned data is consuming.
Another one is the inability to move block-cloned data between ReFS volumes without rehydrating the data. The rehydration means you lose all of the block-clone space savings. Since I don't think we could ever trust Microsoft deduplication technology (especially when combined with ReFS block-cloning) this makes it extremely undesirable to move backup chains from one extent to another. The raw storage space costs us money and we don't want to waste any!

Can there be a way in VBR console to migrate a backup chain between extents and/or repositories, in a way that maintains the ReFS block-clone space savings?
We use per-VM chains. If we could choose move entire backup jobs, or just individual VM chains within a job, that would be great!

[Mildur]

They have announced on VeeamOn 2021, that such a tool (moving data to another Backup Storage) will come with Veeam V12. It will be content aware. Moving the data will not rehydrate the data.

We will get more information this Fall/Winter, what the end version of the tool can do for us

[billcouper]

Mildur, that makes me very happy! I can't wait!

[Rick_M]

Are there any updates when this may be released?

[Mildur]

Yes, with V12.

I don‘t expect V12 this year. Veeam has a yearly release cycle for major versions.

[FrankHa]

Sorry for bumping this old thread, but since V12 is now here: does moving of backup chains without rehydration work between XFS and ReFS?

[Gostev]

Yes. You may want to check out the What's New in V12 document though, as there's actually even more interesting scenarios that this new feature supports