Question regarding VeeaMover and backup data salvaged out from an ReFS Volume

[massimiliano.rizzi]

Hello Community,

one of our customers has recently run into an issue with an ReFS Volume in Windows Server 2019 on a Lenovo server.

Essentially, a firmware issue resulted in storage becoming unavailable inside the OS. We ended up with an unmounted RAW ReFS Volume as the metadata was corrupted and we had to use the ReFSutil tool for data salvage, which allowed us to copy the existing backup data out from the affected volume to a helper volume, although we eventually lost all block cloning savings.

After importing the salvaged backup data (created by a backup copy job in the legacy periodic copy mode created in v11), we discovered that we cannot move backups created by backup copy jobs in the legacy periodic copy mode as described here: https://helpcenter.veeam.com/docs/backu ... imitations

Ideally we would like to be able to somehow move the salvaged backup data back to an existing XFS Repository by leveraging block cloning as there are several synthetic backups created using Fast Clone. Some extra steps and overhead are not a problem.

My understanding is that if we decide to upgrade the salvaged backup chain format as described here https://helpcenter.veeam.com/docs/backu ... ml?ver=120 (for example, by mapping it to a helper job), the salvaged backup chain used for mapping that will be placed to the orphaned node will be useless anyway in terms of being able to move it back by leveraging block cloning.

Am I missing something here ?

Thanks !

Massimiliano

[Mildur]

Hi Massimiliano

I apologize for the late answer.
Correct, the old backup chain (per-job/single-file backup, legacy periodic job) cannot be moved.

What about just leaving the backups on the old storage until they are aged out and start with a new repository?

Best,
Fabian