backup design question / iSCSI SAN

[Pilow]

HI there,

My only repository for backups available are iSCSI SANs (HPE MSA 2700)
As remotes in XCP-NG can't be iSCSI, only NFS/SMB/or S3 I did it this way :

a VM with minio to emulate S3, with a SDB disk multipathing to a LUN on my SAN.

I just read in another post in the forums that you could actually tweak an XO PROXY to use it's own local storage...

So what is better ? should I mount the iSCSI multipath volume locally on the XO PROXY ?
Or keep my S3 minio ?

Backups transfers, using an XO PROXY (or XOA as a unique proxy) goes this way :
XCP HOST ---network---> proxy ----network---> S3 ---iSCSI storage---> MSA

Could be this way :
XCP HOST ---network---> proxy ---iSCSI storage---> MSA

any idea of the best design ? performance wise ?

[Andrew]

@Pilow You could mount an iSCSI LUN on the XO VM and use a local backup remote.... If your XO VM is local to your SAN. This should offer a little more performance as it's directly attached to the XO VM doing the backup.

Using a VM running MinIO with an iSCSI LUN to act as a S3 remote is good too. It does add an intermediate step but gives you some options and flexibility.

[florent]

@Pilow You can use local storage on proxy, it's disabled by default since it's easy to mis configure it, between the local on XO (where you do the config ) and the local on the proxy

the S3 road will be a little less performant, but will offer some nice bonus, the main one is that your proxy won't have any specific conf and can be redeployed/ updated easily

If you go to the iscsi mount in xo-proxy , you will have to create a config file config.localfile.toml in /etc/xo-proxy/ containing

[remotes]
disableFileRemotes = false

then setup a iscsi mount
then configure the remote from XO

[Pilow]

thanks for advice, i'll keep my minIOs running