iSCSI initiator 2. How to configure?

0 like 0 dislike
11 views
Situation
Is —
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 problem:

0) Both the initiator see the store equally (only at the time of mounting)

1) When creating file on XP, on Server it is not visible. The file becomes visible when the Server will remount the resource.

2) you Cannot delete the created resource (the same on both initiators): Access Denied. Target in RW.

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

XP mounts the share as a local folder. Then work with her.
When XP crashes, the Server mounts the share as a local folder. Then work with her.
When XP will return Server unmounts the resource (or remount it into Red-only) and XP mounts the resource on RW.

Dear guru, advise how in this case to build an iSCSI architecture.
asked by | 11 views

5 Answers

0 like 0 dislike
As far as I know — 1 target 2 initiator at a time. The limitation of the technology, so to speak.
Even in failover cluster from hypervi to shared disks access is carried out by one node, the other go "through him", i.e. simultaneous access to the target itself is not.
\r
Here already was discussed, Bystrova the gugleniya ™ — www.vmgu.ru/articles/starwind-enterprise-ha-vmware-esx
answered by
0 like 0 dislike
Once a month this question here appears stable =)
1 target 2 initiator. And 3, and 10.
But on target it is necessary to create a distributed FS. And all initiators need to be able to cook.
NTFS, of course, does not apply to distributed.
answered by
0 like 0 dislike
And by the way, if that's all you need:
"XP mounts the share as a local folder. Then work with her. When XP crashes, the Server mounts the share as a local folder. Then work with her. When XP will return Server unmounts the resource (or remount it into Red-only) and XP mounts the resource on RW.", it all fits and on NTFS, it is not clear what problems you are having. Mounted on the main machine, when it crashes, mounted on backing. When raising the first first ammonium to spare, then mounted the main. In General, the analogue of physically moving the disk from the server in the server =)
answered by
0 like 0 dislike
I suspect that you want to re-invent the microsoft clustering service. It may well be that there is no code you do not need to, but just in case msdn.microsoft.com/en-us/library/Aa372859
answered by
0 like 0 dislike
Stupid question summarized:
There are obstacles to that would traverse the iscsi volume on winserver, but since his by the PSC to distribute filero?
answered by

Related questions

0 like 0 dislike
0 answers
0 like 0 dislike
1 answer
24,509 questions
45,932 answers
0 comments
397 users