Best practice for stretched ISCSI volume?

proudcanadianeh

New Member
Dec 13, 2025
5
0
1
New to PVE, coming here from VMWare. Hoping for some advice as to the best way to setup our ISCSI configuration on our storage arrays.

For context, we have two Pure storage arrays using ISCSI in an Active-Cluster configuration (Single stretched volume across multiple arrays, so one entire array can go offline and the volume is still online and intact).

Where I am having some trouble right now, first up is setting up the ISCSI Discovery for both arrays. In VMWare it was easy for me to add and manage ISCSI discovery portals and would just add an IP from each array and it would do the rest. In PVE, setting up ISCSI I can enter only a singular IP address. This works great for the array that IP resides on, but PVE seems to be blind to the second array existing. Whats the best way for me to add the secondary array? Is this as simple as adding another ISCSI target, and PVE will be smart enough to realise the LVM is across both, or am I going to need to dive into the CLI for this?

My second big question that I cant seem to find a clean answer for, the ISCSI LUN ID. By default the storage arrays choose a random LUN ID for the connection on both sides, and that works great for VMWare as my understanding is it identifies by the volume ID instead of the LUN ID. Does PVE behave the same, or do I need to make sure the LUN ID matches on each array when I set this up?

Thanks!
 
Hey and welcome to the forum :)

For iSCSI Multipathing you need to do it over the CLI with multipath-tools.
You can find a guide here:
https://www.starline.de/en/magazine...-lvm-on-top-of-iscsi-fc-sas-with-multipathing
This guide does not do it over the GUI and adds it directly. I like this approach more, as it does not clutter the GUI with all the iSCSI Connections.
=> but the iSCSI Connections are also not directly manageable over GUI
The official documentation:
https://pve.proxmox.com/wiki/Multipath

About the LUN ID, multipath will identify the LUN via its WWID as well. So no need to worry about that.

Cheers :)
 
  • Like
Reactions: Johannes S