Move orphaned legacy backup copy chains using VeeaMover

[massimiliano.rizzi]

Hello experts and good day,

please forgive me in advance as I am afraid I already know the answer, and I won't like it , but I think it's worth asking once again.

Please consider the following scenario:

==================================================

==================================================

All orphaned backups highlighted in red above have been created by legacy backup copy jobs over time and are currently stored on disk on a simple backup repository (let's say "Repository A") that supports block cloning with ReFS. As a result, all synthetic full backups have been created leveraging fast clone.

"Repository A" is running low on space, so we would like to leverage VeeaMover to move these backups to a different simple backup repository ("Repository B") that supports block cloning with ReFS as well.

Is there any chance/script/trick to re-create separate metadata files linked to these orphaned backup copy chains in order for us to be able to leverage VeeaMover and block cloning benefits during move ?

Any advice on this matter will be greatly appreciated.

Thanks and regards,

Massimiliano

[Mildur]

Hello Massimiliano,

Unfortunately, existing legacy chain backup files cannot be converted to "chains with separate metadata files."
The only option I see is to use the pre-v12 approach: Use a third-party block cloning tool to migrate the entire Volume 1 from Repository A to Repository B.

Best regards,
Fabian

[massimiliano.rizzi]

Hi Fabian,

thank you very much for your reply!

Regards,
Massimiliano