iSCSI - 2 initiators. How to set up correctly?

Question

Microsoft

Situation
Yes -
iSCSI target - on FreeNAS (IP: 192.168.10.1)

iSCSI Initiator - Windows XP x64 (Microsoft iSCSI Initiator ver. 2.08) - IP: 192.168.10.2

iSCSI Initiator - Windows Server 2008 R2 (Microsoft iSCSI Initiator) - IP: 192.168.10.3

The essence of the problem:

0) Both initiators see the storage in the same way (only at the time of mounting)

1) When we create a file on XP, it is not visible on the Server. The file becomes visible when you remount the resource on the Server.

2) You cannot delete what was created on the resource (the same on both initiators): Access Denied. Target in RW.

What I need:
XP - primary mail-server
Server - secondary.

XP mounts the resource as a local folder. Then he works with her.
When XP crashes, Server mounts the resource as a local folder. Then he works with her.
When XP is back up and running, the Server will unmount the resource (or remount it to Red-only), and XP will mount the resource on the RW.

Dear gurus, please advise how to build iSCSI architecture in this case.

Answer 1

Once a month this question appears here stably =)
2 initiators are allowed for 1 target. And 3 is possible, and 10.
But at the same time, you need to create a distributed FS on the target. And all the initiators should be able to prepare it accordingly.
NTFS, of course, does not apply to distributed ones.

Answer 2

I suspect that you want to reinvent the microsoft clustering service. You may well not need any code there at all, but just in case msdn.microsoft.com/en-us/library/Aa372859

Answer 3

As far as I know, 2 initiators are not allowed for 1 target at the same time. The limitation of technology, so to speak.
Even in a failover cluster, one node accesses shared disks from a hypervie, the rest go "through it", i.e. there is no simultaneous access to the target as such.
It has already been discussed here, quick google ™ - www.vmgu.ru/articles/starwind-enterprise-ha-vmware-esx

Answer 4

And by the way, if this is all you need:
“XP mounts the resource as a local folder. Then he works with her. When XP crashes, Server mounts the resource as a local folder. Then he works with her. When XP gets back up and running, Server unmounts the resource (or remounts it to Red-only), and XP mounts the resource on RW.", then everything fits perfectly on NTFS, it's not entirely clear what problems you have. We mount on the main machine, when it falls, we mount on the backup. When raising the first one, we first unmount it on the spare one, then mount it on the main one. In general, an analogue of the physical movement of a disk from server to server =)

Answer 5

Stupid question for those in the know:
Are there any obstacles to forwarding an iscsi volume to a winserver, and then distributing it to a file share via SMB?