Hi Jakub,

i was thinking about this idea as well

we are using repositories with ISCSI - physical box attached on VM - so VM is acting as repository

so as into appliance you cannot do changes - or maybe to ask officially statement from Veeam

So my idea is to attach over ISCSI to the esx hosts on vmdk and then vmdk to add to appliance, what is ok from my point of view

I've been considering this too. I'm currently deciding whether to install Veeam as a software appliance or on Windows Server. If I knew how to get iSCSI working on Linux, I'd go for it, but if not, I'll probably choose Windows Server, where it works without any problems.

VBR it does not matter - i would go with appliance

but you can have linux VM with ISCSI, what i have now - on redhat and is working fine.

So oyu can combine VBR and some components as appliances, but some backup components - VMs with linux, which is managed by yourself

Make sure you download the correct Infrastructure Appliance.

• For Linux-based proxies deployed from Veeam Infrastructure Appliance ISO or for the Linux-based backup server that acts as a proxy, you must enable an Open-iSCSI Software initiator (iscsid).

https://helpcenter.veeam.com/docs/vbr/userguide/jeos_install_select_product.html?zoom_highlight=iSCSI&ver=13

https://helpcenter.veeam.com/docs/vbr/userguide/storage_configure_proxy.html?zoom_highlight=iSCSI&ver=13#iscsi-protocol

From a “more global” DR perspective: Think twice for production backups on “somehow” iSCSI mounted deviced. From a recovery standpoint you have an additional source of errors which would be your iSCSI connections and in case you have a global outage of your ESXi you might lose your iSCSI access as well.

For lab or small SMB environments I’d follow the approach to have a “non-ISOed” Linux host that manages that iSCSI connection and that host will be connected to your VBR.

​@randyweis thanks for sharing, i was not aware, that appliance with ISCSI protocol could be used.