Odd iSCSI Initiator Problem

SteveOBHave · 15 Jul 2011 at 11:38

I'm getting some issues with seeing disparity between two servers connected to the same SAN Volume via Windows iSCSI Initiators. One one server I can see files, delete files and see them shift to the Recycle Bin. On the other server I can't see the same files or when adding new files they don't turn up.

Is it bad to have two servers talking to the same SAN Volume via iSCSI?

paradigm · 15 Jul 2011 at 11:42

SteveOBHave said:
Is it bad to have two servers talking to the same SAN Volume via iSCSI?

Typically, yes.

You need to be using cluster services or DFS to have multiple connections to the same volume.

SteveOBHave · 15 Jul 2011 at 11:51

ah - that'd explain Veeam having issues as well. Cheers mate.

Dr. Pain · 15 Jul 2011 at 12:58

What??

ESX and ESXi are designed for exactly that. LUN sharing should be no issue whatsoever.

Also doesnt the new MS Iscsi Target support Persistent connections?

paradigm · 15 Jul 2011 at 14:17

Hyper-V in a failover cluster (using SCVMM) supports persistent reservations yes. Hence me saying a clustered services environment OR DFS (if he is just after a filer solution).

Hyper-V/SCVMM failover clustering is based off Windows Failover Cluster services, a standalone Hyper-V server would need to use the normal iSCSI initiator, with no intelligent reservation handling.