Move backups from ReFS repo to HPE StoreOnce or Hardened Linux Repo

[romulanvox]

I've several clients who would like to move their Veeam v11a backups currently on Windows ReFS repos, to either HPE StoreOnce (Catalyst Stores on 10G ethernet) or to hardened Linux repos (to use the immutable backup feature).

Are such backup movements from one type of repo to another type, technically possible by using SOBR? For example, I have the following repos.

1. REPO1_Windows-ReFS (contains the backups to be moved)
2. REPO2_HPE-StoreOnce-Catalyst
3. REPO3_Hardened-Linux-Repo (configured for immutable backups)
4. REPO4_Hardened-Linux-Repo (configured for immutable backups)

Can I create something like below?

A. SOBR_1 : REPO1_Windows-ReFS (performance tier) + REPO2_HPE-StoreOnce-Catalyst (capacity tier). Then put REPO1_Windows-ReFS into maintenance and evacuate the backups on it?

B. SOBR_2: REPO1_Windows-ReFS (performance tier) + REPO3_Hardened-Linux-Repo (performance tier) + REPO4_Hardened-Linux-Repo (performance tier). Then put REPO1_Windows-ReFS into maintenance and evacuate the backups on it?

[HannesK]

Hello,
and welcome to the forums.

Technically it's possible today. The question is, whether your clients want to do it now, or wait until V12 is out. In V12, backups can be moved between different repositories while preserving block cloning space savings (e.g. REFS to XFS). That "Veeamover" works between different repositories without SOBR.

A: capacity tier must be object storage. No option for catalyst as capacity tier. Storeonce can be used for backup copy jobs
B: yes, that works. But you lose block-cloning space savings.

Best regards,
Hannes

[romulanvox]

Hi Hannes,

Is there any ETA for v12 to go GA?

For option A, can StoreOnce Catalyst also be used as a performance tier within the SOBR with the ReFS repo already on the performance tier?

[veremin]

- We cannot provide any concrete ETA as of now, but you can check our best estimations here
- Technically it's possible, but don't forget to enable the Data Locality placement policy for the scale-out backup repository. If backups are stored on different extents, Fast Clone or deduplication will not be used

However, originally you were thinking of moving away from ReFS extent in favor of StoreOnce, has anything changed? Or the last question regarding ReFS and StoreOnce extent coexistence is more like a general interest?

Thanks!