[V13] Hardened Repository

[AbdelO]

Hi Experts !!

I’m currently design a deployment with Veeam Backup & Replication v13, where a backup repository server is directly connected to a storage array using SFP28 DAC cables.

According to the official documentation , JeOS ISO requirements only locally attached block storage (SAS, internal drives, etc.) is supported.
Connections through SFP28 ports are usually iSCSI or Fibre Channel, which would classify them as network-based storage, not local block devices.

My questions are:
Can the JeOS deployment recognize and support storage attached via SFP28 DAC if it presents LUNs as block devices to the OS (for example, using iSCSI direct attach without switches) ?
Or is it mandatory to use SAS direct attach with a hardware RAID controller to stay compliant with the JeOS requirements ?
Is it supported to deploy a standard Ubuntu Server (not JeOS) with XFS-formatted disks for backup volumes in a hardened repository configuration ?
Has anyone successfully deployed a similar setup using SFP28 direct attach with either JeOS or Ubuntu Server ?

Thanks in advance

[Gostev]

Correct, iSCSI storage is not supported for VIA-based hardened repositories in principle (FC storage should work though).
And yes, of course you can continue using BYO Linux approach for hardened repositories, this is fully supported.

[AbdelO]

Even from the VSA linux-based (like VeeamSoftwareAppliance_13.0.0.4967_20250822), are immutable directories supported (BYO Linux), or do we have to wait for Veeam v13 on Windows ?

[Gostev]

Yes they are supported. Both VSA and V13 installable software for Windows are running the same exact cross-platform code, so there won't be any differences like that in principle.

[chaos]

(FC storage should work though).

But this wouldn’t be a supported solution, right?

[Gostev]

Only in a sense that our Customer Support will not be able to provide assistance in setting up or troubleshooting fabric connectivity or any storage array related issues outside the server where Veeam is installed.

But the beauty of FC SAN is that it should "just work" with the corresponding volumes appearing in the OS as disks without any OS-side configuration required (unlike with iSCSI SAN). At which point it makes no difference for our software if backing those disks are internal drives, SAS enclosure or FC SAN.

[chaos]

That sounds great!
You now opened another can of worms for me - in regards planing our greenfield deployment - as I was under the assumption that this isn't a "supported" config.
Okay i have to dig deeper, next problem might be multipath.conf don't know how "good" the out of the box one is.
But this would be an easy fix via elevate to root or veeam pushes a modified one for the verified block system in partnership with the vendors.

[wombat77]

Only in a sense that our Customer Support will not be able to provide assistance in setting up or troubleshooting fabric connectivity or any storage array related issues outside the server where Veeam is installed.

But the beauty of FC SAN is that it should "just work" with the corresponding volumes appearing in the OS as disks without any OS-side configuration required (unlike with iSCSI SAN). At which point it makes no difference for our software if backing those disks are internal drives, SAS enclosure or FC SAN.

Thanks Gostev! But how can multipathing and automatic provisioning of partitioning and formating work? I'm not sure but i will give it a try with our new fujitsu servers next week.

[Gostev]

Any SAN capabilities that require additional software installed and configured on the server will not work of course. I don't know however if the things you listed require such software, I'm not really a SAN expert.

[juanmachado]

So to confirm (sorry, I am having a hard time finding the answer):

Hardrepo on v13 does NOT support iSCSI volumes, only Fiberchannel. Is that correct?

Thanks

[Gostev]

Correct.

[BrentO]

If I have a hardened repo right now that leverages iSCSI on Ubuntu for the restore points should I not upgrade to v13 then?

[Gostev]

Please read my first reply.

[BrentO]

Thanks Gostev! I read the first reply and thought that was in regards to the VIA implementation. That I get. This isn't a VIA though. This is a standalone Ubuntu server.

[Gostev]

Now read the second line of the same reply

[AbdelO]

Thank you for your previous feedback, and apologies for not responding earlier.
We are currently running Veeam Backup & Replication v13 and planning to deploy a Hardened (immutable) Linux repository.
Can you please confirm whether Rocky Linux 10 is officially supported for this role (or if we should stay on Rocky Linux 9.x for full support?) (BYOL)

[HannesK]

Hello,
the system requirements list Rocky Linux 10 as supported, yes.

Best regards
Hannes

[Gene-MN]

We went through the trial and error of attempting to use the VHR ISO with a DAS server and failed multiple times. We waited 8+ months before attempting to DIY a hardened repository out of fear of complexity. When we finally decided to just go for it, it took 3 hours the first time as a proof of concept and 2 hours the second time to show the entire Backup team how it was done. We are now in production.

We followed the series: https://cucafrescait.com/2025/02/10/ste ... ig-part-1/
and took what we needed from it. Multipath was reasonably easy to configure and get working via Google searches. There were missing pieces in the referenced guide, like dkms, which are needed but VBR errors put us on-track.

I am in the process of creating detailed documentation, but I have the rough notes we used during the final build if you are interested. They are rough and reference a few settings unique to our Server/DAS but they should be able to give you a general guide. Let me know and I will share them with anyone who is interested.

[chris.childerhose]

Correct, iSCSI storage is not supported for VIA-based hardened repositories in principle (FC storage should work though).
And yes, of course you can continue using BYO Linux approach for hardened repositories, this is fully supported.

So FC is now supported? Last time I tested, it still did not work correctly and was still being worked on.

[HannesK]

the question is about the scenario... we have a mix of Hardened Repository ISO, Veeam Infrastructure Appliance with Hardened Repository and BYO Linux with Hardened Repository in this thread

Hardened Repository ISO & Veeam Infrastructure Appliance with Hardened Repository: FC doesn't work / not supported. While I had slight hope that it might work, I tried it out some weeks ago and it fails.
Hardened Repository ISO & Veeam Infrastructure Appliance with Hardened Repository: iSCSI doesn't work / not supported
BYO Linux with Hardened Repository: FC & iSCSI are supported as the software just takes whatever volume it sees

[chris.childerhose]

Thanks for the clarity Hannes.