Moving from Windows to Linux Hardened Repositories in SOBR

[nmdange]

So, I have a Scale-Out Backup Repository that consists of several Windows Servers. I tried adding a Linux Hardened Repository that was created from the VHR ISO to the same SOBR, but I got an error that SOBR can't have extents with different immutability settings.

Would it be possible to add multiple VHR repositories as a "regular" Linux repository, and then once all the old backups have expired, remove the Windows-based extents and convert the Linux repositories to hardened repositories somehow? The main reason I want to do this rather than creating a new SOBR is that the capacity tier is in the cloud (Backblaze S3) and I don't want to either have to duplicate all of our offsite cloud backups (which costs $$$), or delete the cloud backups and be without the offsite backups during that time period.

[Gostev]

SOBR can't have extents with different immutability settings.

Actually, they can since last year from What's New in 12.3:

Scale-out Backup Repository
Enhanced migration experience — Extents from different object storage systems and/or extents with
different immutability settings can now coexist within the same Performance and Capacity tier, unlocking
many migration scenarios. For example, this allows you to easily move your backup from one cloud object
storage provider to another, or from non-immutable bucket to a bucket with immutability enabled. To add
an extent of a different type, you need to first put existing extents into the sealed mode.

[nmdange]

Ahhhh! Ok, so if all the existing extents need to be sealed, I'll need enough space to duplicate everything. I had originally planned to do one extent at a time and then redo the existing repositories with VHR ISO as each one was freed up. I need some additional planning, but I think it's doable with what I have. Thanks!

[HannesK]

Hello,
I believe you are looking for Upgrading Performance Extent to Hardened Repository. Additionally www.veeam.com/kb4636 might help.

From what I remember, the 12.3 feature is only for different object storage types. In the early days, we allowed mixing Hardened Repository with "everything" in SOBR, but we stopped that after some versions because it created many edge cases (we did not enforce sealed mode at that time).

Best regards
Hannes

[ViktorSavin]

Hi,

Based on Case #07683744 I would like to propose a feature request.
There is a need to migrate backups to hardened extents within a SOBR.
Currently, the SOBR contains only regular extents, and it does not allow adding hardened extents because they are of a different type.
Since a large amount of data needs to be migrated, the most automated approach is required.
This kb https://www.veeam.com/kb4636 doesn't fit due to a lot of manual operations.

It would be helpful to have an option to mix extents in a SOBR just for migration purpose.