iSCSI storage on VIA and VSA

[matteu]

Hello,

If I understand correctly, since v13.1 it's possible to connect iSCSI from Veeam appliance.
I tried to connect it on my VSA server, but then I see I cannot use it for Hardened linux repository but only as "Normal" linux repository.

Is it something expected ?

That mean if I add storage on my VSA as iSCSI/FC I can only use it as "normal" XFS filesystem and use fast clone to save some space (better than nfs) but no immutability.
If I use VIA and connect storage, it should work with immutability enabled it should work right ?

[matteu]

Can you also confirm me if I have to choose veeam hardened repisitory during installation as role or veeam infrastructure appliance with iscsi / fc ?
Thanks

[unsichtbarre]

You will need to build a hardened Linux system to mount iSCSI. THe Linux system mounts the iSCSI LUN(S), formats as XFS and creates the mountpoints. You can then add to VSA as a hardened Repo. with all of the bells and whistles.

-JB

[matteu]

Hello
Thanks for your answer.
On my home lab I probably had a a bug the first time I tried because it didn t work and I rebuikd from scratch and work fine.
I also opened a case but they asked me to use veeam infrastructure appliance and select infrastrastructure appliance with iscsi/ fe . They probably missunderstand what I need...

The drawback is a new vm is needed for it while it s not if I want to use nfs / smb... it s for a small customer with a LHR at first target for backup ans the overhead for iscsi is a little too high compared to nfs used on the VBR directly ... only 15 vm to backup with proxmox and already 1 VBR + 2 worker as virtual and 1 physical hlr and then a synology for backup copy (this is the nfs one)

[pma]

Hi matteu, John,

Good news: for this scenario you don't need an extra appliance at all.

On the VSA, iSCSI block storage attached in the Host Management Console can hold immutable backups. The "Linux" repository type you saw is the right one - a Linux-based backup server acts as an immutable repository without additional
preparation, and you set the immutability period in the repository settings (https://helpcenter.veeam.com/docs/vbr/u ... mutability). The reason the "hardened repository" path wasn't offered for the VSA's own storage is that a hardened repository is by definition a dedicated machine carrying no other Veeam roles (except for VMware proxy role), and your VSA is also running the backup server. So it was the label you were hitting, not a missing capability.

On the overhead point, it's worth flipping around: NFS and SMB volumes can't be used for Linux/Hardened repository on VSA/VIA, so block storage over iSCSI is precisely what buys you an immutable target that NFS can't - and attaching it to the VSA you already have costs you no additional VM.

The honest trade-off: a dedicated hardened repository on its own appliance remains the stronger posture, since the VSA also runs the backup server and so has more services and fewer restrictions around it. With a physical LHR as your primary target and 15 VMs, using the VSA's own iSCSI storage for the second copy is a reasonable call.

[matteu]

@pma

Hello,

Thanks for your complete answer

It's good to know it because I would never have been done this test !

It works fine yes after adding the iSCSI target IP from the VSA and add it as "Linux" Repository and not "Hardened repository" and check I can't remove any backup because they are immutable