ISCSI Multiple Targets - Multiple

I would like to know if this configuration will cause me to experience file corruption. I have a server which is configured as raid 6. I have windows 2012 installed and configured 3 iscsi targets. If I connect a separate server to each target will
I run into any issues with file corruption? I have seen that multiple connections to a single target will cause corruption but cannot confirm if multiple targets on a single server will cause the same corruption.
GY

You can only connect one initiator to a target unless you have multipath enabled.
This is incorrect. MPIO enabled or disabled has nothing to do multi-initiator connect. It's a question to file system, is it cluster-aware or not (NTFS w/o a CSV filter is not BTW). More info here (common SAN concept), see:
iSCSI instead of SMB
http://www.starwindsoftware.com/forums/starwind-f5/trying-clear-this-use-iscsi-instead-smb-t1392.html
Good luck :)
StarWind VSAN [Virtual SAN] clusters Hyper-V without SAS, Fibre Channel, SMB 3.0 or iSCSI, uses Ethernet to mirror internally mounted SATA disks between hosts.

Similar Messages

ISCSI Software Target - Disk is corrupt (locally) not on on the target

Hi,
I have a Windows 2008R2 server on which i have installed Microsoft iSCSI Software Target. I have created a Virtual Disk and an iSCSI target configuration on this server.
The target is a virtual server running Windows 2012R2. The target has the virtual disk mounted succesfully as a R: drive and i can use it, create files, delete files with no apparent problems.
However on the Win2008R2 box where i have created the virtual disk, i cann see that the virtual disk is also mounted and generates hundreds of errors in the system logs: "The file system structure on the disk is corrupt and unusable. Please run chkdsk
utility on the volume n" The goal is to have the Virtual Disk mounted on the target server but not on the server where the Vdisk is created. Any help would be greatly appreciated.

Hi,
I have a Windows 2008R2 server on which i have installed Microsoft iSCSI Software Target. I have created a Virtual Disk and an iSCSI target configuration on this server.
The target is a virtual server running Windows 2012R2. The target has the virtual disk mounted succesfully as a R: drive and i can use it, create files, delete files with no apparent problems.
However on the Win2008R2 box where i have created the virtual disk, i cann see that the virtual disk is also mounted and generates hundreds of errors in the system logs: "The file system structure on the disk is corrupt and unusable. Please run chkdsk utility
on the volume n" The goal is to have the Virtual Disk mounted on the target server but not on the server where the Vdisk is created. Any help would be greatly appreciated.
If you're trying to mount iSCSI disk from the multiple initiators @ the same time it's not something you can do straightforward because NTFS is not a cluster-aware file system and has no clue about somebody else changing metadata in-place. There many
options (using CSV, using SMB on top of iSCSI, using cluster-aware file system and using distributed lock manager), see detailed description and options listed here:
iSCSI instead of SMB
http://www.starwindsoftware.com/forums/starwind-f5/trying-clear-this-use-iscsi-instead-smb-t1392.html
(hosted on StarWind site but is true for any Windows and SAN implementation including one you use)
Hope this helped a bit :)
StarWind VSAN [Virtual SAN] clusters Hyper-V without SAS, Fibre Channel, SMB 3.0 or iSCSI, uses Ethernet to mirror internally mounted SATA disks between hosts.

My Windows 2012 ISCSI Target service needs to be restarted every time the server starts.

Every time I restart my Windows 2012 server, the ISCSI Target Service is unavailable to the clients even though it appears to be running.
I have to restart the service, then the clients can connect to it.
I tried to change the startup Type to Delayed, but I get an error 87: parameter is incorrect.
I've tried to delete and recreate the VHD and ISCSI Target.
I've tried to uninstall the Role, and reinstall it.
Anybody have any additional ideas to try and troubleshoot this?
Thank you
James Roper

The service is not starting correctly, even though it does start. If I restart the service, everything works correctly. Here is the event in the ISCSI Target.
Log Name: Microsoft-Windows-iSCSITarget-Service/Admin
Source: Microsoft-Windows-iSCSITarget-Service
Date: 5/8/2013 3:11:10 PM
Event ID: 10
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: SRV-ISCSI1
Description:
The Microsoft iSCSI Software Target service could not bind to network address 10.5.4.31, port 3260. The operation failed with error code 10049. Ensure that no other application is using this port.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-iSCSITarget-Service" Guid="{13953C6E-C594-414E-8BA7-DEB4BA1878E3}" />
<EventID>10</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2013-05-08T22:11:10.899843800Z" />
<EventRecordID>38</EventRecordID>
<Correlation />
<Execution ProcessID="976" ThreadID="1448" />
<Channel>Microsoft-Windows-iSCSITarget-Service/Admin</Channel>
<Computer>SRV-ISCSI1</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="IpAddress">10.5.4.31</Data>
<Data Name="dwPort">3260</Data>
<Data Name="Error">10049</Data>
</EventData>
</Event>

ISCSI targets for the Mac

I setup a VMware vSphere 4 Server with RAID 10 direct-attached storage and 3 virtual machines:
- OpenSolaris 2009.06 dev version (snv_111b) running 64-bit
- CentOS 5.3 x64 (ran yum update)
- Ubuntu Server 9.04 x64 (ran apt-get upgrade)
I gave each virtual 2 GB of RAM, a 32 GB virtual drive and setup a 16 GB iSCSI target on each (the two Linux vms used iSCSI Enterprise Target 0.4.16 with blockio). VMware Tools was installed on each. No tuning was done on any of the operating systems.
I ran two tests for write performance - one on the server itself and one from my MacBook Pro (10.5.7) connected via Gigabit (mtu of 1500) iSCSI connection using globalSAN 3.3.0.43.
Here’s what I used on the servers:
time dd if=/dev/zero of=/root/testfile bs=1048576k count=4
and the Mac OS with the iSCSI connected drive (formatted with GPT / Mac OS Extended journaled):
time dd if=/dev/zero of=/Volumes/test/testfile bs=1048576k count=4
The results were very interesting (all calculations using 1 MB = 1,084,756 bytes).
For OpenSolaris, the local write performance averaged 86 MB/s. I turned on lzjb compression for rpool (zfs set compression=lzjb rpool) and it went up to 414 MB/s since I’m writing zeros). The average performance via iSCSI was an abysmal 16 MB/s (even with compression turned on - with it off, 13 MB/s).
For CentOS (ext3), local write performance averaged 141 MB/s. iSCSI performance was 78 MB/s (almost as fast as local ZFS performance on the OpenSolaris server when compression was turned off).
Ubuntu Server (ext4) had 150 MB/s for the local write. iSCSI performance averaged 80 MB/s.
One of the main differences between the three virtual machines was that the iSCSI target on the Linux machines used partitions with no file system. On OpenSolaris, the iSCSI target created sits on top of ZFS. That creates a lot of overhead (although you do get some great features).
Since all the virtual machines were connected to the same switch (with the same MTU), had the same amount of RAM, used default configurations for the operating systems, and sat on the same RAID 10 storage, I’d say it was a pretty level playing field.
At this point, I think I'll be using Ubuntu 9.04 Server (64-bit) as my iSCSI target for Macs.
Has anyone else done similar (or more extensive) testing?

I had a lot of trouble with SimCity4 on my iMac. It became such a headache that I returned it to compUSA. It ran very choppy and crashed repeatedly when the city began to develop. My system FAR exceeds the system requirements for the game, and after some online research I discovered that I am not the only person to have this trouble with SimCity running on 10.4. I have also read problems concerning the SIMS2. Some of what I have read indicates that 10.3 runs the games fine, but 10.4 causes them to crash. I don't know if this is the case, but I do know that I am now very weary before dropping $50 on a game that may not perform on my computer as it claims to on the box. Some people trying to run games are talking about waiting for Mac OS updates that will allow them to run smoother.
I would check out what gamers are saying before buying anything
http://www.macosx.com/forums/showthread.php?t=226286

ISCSI Target Settings - disabling automatically enabled IP addresses

Hey guys,
I could find a way to disabling the "new network addresses will automatically be enabled" function within the iSCSI Target Settings or via powershell.
Can anyone provide a good solution? For several reason I can't avoid to get new IPs regulary (dynamic IPv6 Environment)

Hi,
I’m a little unclear the issue. Do you want to the iSCSI Initiator always use a static IP address to connect the iSCSI Target even the IP address is automatically obtained? I cannot find there is such function.
You could refer to the article below to configure network connections between the initiator and Microsoft iSCSI Software Target.
Microsoft iSCSI Software Target 3.2: Known Issues and Updates
http://technet.microsoft.com/en-us/library/dd904411(v=ws.10).aspx
Best Regards,
Mandy
If you have any feedback on our support, please click
here .
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

ISCSI Target Issues

I am running MS Server 2012 and am only using this as a iscsi target server. I run VMware vspher 5.5 as the initiator. So every night around 12:30 am, my server restarts many of the services, one of them being the iscsi target service. No
errors are produced, just informational logs about the services stopping and starting again. However, when they stop my vphere client and vm's on the iscsi target lose connection. I just want them to run all the time, these are production systems.
When I come in the next day I just do a refresh on the iscsi target gui and everything reconnects. Then I have to go to the vsphere client and answer the guest question about why they lost contact with the targets and the vm's all restart without
a problem. Does anyone know about this problem and how to resolve it?

No, but I think 2012 has built in virus checker, I'll check that. Nope, but this is the info log published.
At 12:31 I got "The Microsoft iSCSI Software Target service entered the stopped state." Then when I came in this morning and hit refresh at 6:01 I got "The Microsoft iSCSI Software Target
service entered the running state.". Both were the event id below. Sometimes it puts it back in the running state automatically, but sometimes I have to manually do it, either way, when it goes into stopped state my vsphere client makes me
answer the "guest" question to bring it back live in the vmware client side. Checked antivirus, no problems there. Again, these are not errors, they a re calling these basic service operations as shown below. How can shutting down
productions systems be a normal operation, must be some way around that or who would want to use this. The nice thing is how easy it is to set up a target, but this is a problem. People use are systems around the clock sooo...any other thoughts?
Event ID 7036 — Basic Service Operations
73 out of 202 rated this helpful - Rate this topic
Updated: December 11, 2007
Applies To: Windows Server 2008
green
Service Control Manager transmits control requests to running services and driver services. It also maintains status information about those services, and reports configuration changes and state changes.
Event Details
Product: Windows Operating System
ID: 7036
Source: Service Control Manager
Version: 6.0
Symbolic Name: EVENT_SERVICE_STATUS_SUCCESS
Message: The %1 service entered the %2 state.
Resolve
This is a normal condition. No further action is required.
Related Management Information
Basic Service Operations
Core Operating System
So how c

OEL 4.5 iSCSI Target notes wanted

I'm about to build an iSCSI target based around an OEL 4.5/Dual Opteron/8GB/2.5TB Sata machine. Distro is flexible, but I would prefer to stick with OEL 4.5 or OEL 5.0.
I'd appreciate pointers and links to good documentation, howtos, notes, etc. that you have encountered. This is a learning opportunity for me.

Hans,
we can start with installation HowTo :-)
1. Install kernel-devel package
2. Download "iSCSI Enterprise Target" from http://sourceforge.net/project/showfiles.php?group_id=108475
3. tar xvzf iscsitarget-0.4.15.tar.gz
4. cd iscsitarget-0.4.15
5. make
6. # make install
7. Modify /etc/ietd.conf and set mandatory parameters:
- Target (iSCSI qualified name aka IQN - in format iqn.yyyy-mm.reversed domainname:identifier)
- LUN (storage)
Assume that your domain is acme.com and my shared device /dev/sda, no authentication. So config will be as following:
Target iqn.2008-01.com.acme:storage.disk1
Lun 0 Path=/dev/sda8. # chkconfig iscsi-target on
9. # /etc/init.d/iscsi-target start
10. "man ietadm" "man ietd" "man 5 ietd.conf" and cup of coffee :-)
A Quick Guide to iSCSI on Linux - http://www.cuddletech.com/articles/iscsi/index.html
Setting Up an iSCSI Enviroment - http://www.howtoforge.com/iscsi_on_linux
Message was edited by:
Ivan Kartik
Of course you may consider to use this: http://www.openfiler.com

Help with solaris 10 iscsi

Hi all,
i'm a solaris newbie and new user so, let's go.
I have difficult in configuring/installing iscsi target on solaris 10
My uname -a is
SUNOS 5.10 generic_118822-02 sun4u sparc
if i launch pkginfo | grep iscsi it returns :
system SUNWiscsir sun Iscsi device driver (root)
system SUNWiscsiu sun Iscsi management utilities (usr)
but i cannot find iscsiadm in no system path neither other file concerning iscsi.
I installed pkg-get too but i'm unable to find this package.
Could u help me ?
Thank u all for reading a for supporting
Darktux....

hi all
1st of all, thank u for support...
then i need some explaination for the installation of 119090-25 (iscsi driver + target) installation
this patch requrires kernel patch (118833-36-1) that requires 3 other patches 118918-13, 119042-09 and 119578-30
now i have some questions for kernel installation patch... on my server is running oracle and i ask if this upgrade should give some problem with services running.
could u guide me through this adventure? I repeat i'm totally newbie and i'm reading as much as possible to understand as best i can solaris 10
thank u
sorry for my english

ISCSI-to-FC routing in Cisco MDS 9000 Family

Hi,
I'm puzzled about support for iSCSI-to-FC routing in the MDS 9000 family. Earlier hardware such as the 9216i switch and the MPS-14/2 module had a feature to allow an iSCSI Initiator to connect transparently to an FC target. This equipment is now EOL and has been replaced by models such as the 9222i switch and the 18/4 Port Multiservice Module. The datasheets for these replacements strongly imply that they support iSCSI-to-FC routing in a similar way to the earlier products - for example "iSCSI for extension of the SAN to Ethernet attached servers - Extends the benefits of Fibre Channel SAN-based storage to Ethernet attached servers".
I tried to find some hard technical info to confirm this. Chapter 4, "Configuring iSCSI" in "Cisco MDS 9000 Family NX-OS IP Services Configuration Guide Release 5.0(1a)" says that the feature is only available on the IP Storage Module, the 9216i switch, and the MPS-14/2 module, all of which are now EOL. It doesn't mention the replacement models in connection with this functionality, though they are mentioned elsewhere in the book for other features such as FC over IP. I've searched for documentation of the iSCSI support on the new models and the only document which seems relevant is this chapter - but it says it doesn't apply to these models.
Do the replacement models support iSCSI-to-FC routing or not? The datasheets use wording nearly identical to the earlier models in this area, so I assume they do. If they do, how is it configured and where is it documented? I sent feedback on this to the documentation feedback address a while ago, but haven't had a reply.
Many Thanks,
                            jjf

The "Configuring iSCSI" chapter in both 3.3.3 and 4.1.1 documentation similarly talk about IPS and 14/2 modules but make no mention of 18/4, however I've used iSCSI on the 18/4 with both releases. I can only guess the same is true for 5.0 since I have yet to load 5.0 on any switches.
In terms of other documentation I don't think there is any, but all the required information is presented in the "Configuring iSCSI" chapters however it's not the easiest thing to understand from the documentation. Following is the overview I sent to a teammate on how to setup iSCSI.
1. configure Ethernet ports with ip addresses
1a. add a route to the host, iSCSI client, via the gigabit interface 2. enable iscsi on the switch
2a. enable iscsi on the module with the gige port
2b. 'no shut' the iscsi interface corresponding to gige port
      e.g. gige3/4 -> iscsi3/4
2c. no additional configuration of the interfaces is needed, although at some point turning on authentication would be a good idea
3. create iscsi initiator
3a. use the clients ip address as the initiator name, using the node name would be better but I haven't tried it that way so ymmv
      e.g. 'iscsi initiator ip-address xxx.xxx.xxx.xxx'
3b. use a "system assigned" nwwn and set it static
      e.g. 'static pWWN system-assign'
3c. allocate one "system assigned" pwwn and set it static
      e.g. 'static pWWN system-assign 1'
3d. assign vsans, an iscsi initiator can be in more than one vsan
      e.g. 'vsan xxx'
4. create targets
   spcsw1(config)# iscsi virtual-target name iqn.000190300646.fa02cb
   spcsw1(config-iscsi-tgt)# pwwn 50:06:04:8a:d5:f0:79:a1
   spcsw1(config-iscsi-tgt)# initiator ip address xx.xx.xx.xx permit
5. zone the iscsi initiator's pwwn to the target pwwns, use 'sh iscsi initiator configured' to see the pwwn
6. configure the hosts iscsi initiator, usually not much more than specifying the ip address of the gige port on the MDS

Present iSCSI LUN to MDS 9222i

All,
I am in a lab environment and do not have access to FC attached storage. I do have an OpenFiler, which is an iSCSI storage target device. I also have a FC attached host. Can I use the OpenFiler via iSCSI to the MDS and present its LUNS to the faric?

Hi Donnie,
I don't think you will have any luck - You could however pop your HBA into your linux machine and set it up as a FC target :)
Cheers

ISCSI Issue - Help in debugging

Hello,
I have an issue where a Windows 2000 iscsi client receives an error in the event log saying "Target sent an iSCSI PDU with an invalid opcode"
The iscsi target is a Solaris x86 box attached to a SATA JBOD.
Any advice on debugging the root cause of the problem would be appreciated.
I am thinking a debug at the client side will help but I don't know how to enable on Windows to get it.
Per my understanding, on the target one would see iscsi errors on /var/adm/messages right? But I don't see any relavent errors there.
Any way to enable debug on the target? Will it help and can it be sorted for this particular client?
Thanks in advance.

Thanks for your reply.
I'll check the other things which you have suggested.
Here is the iSCSI header
Target sent an iSCSI PDU with an invalid opcode. Dump data contains the entire iSCSI header.
Data:
0000: 00 00 30 00 01 00 8a 00 ..0...?.
0008: 00 00 00 00 18 00 00 c0 .......À
0010: 00 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: 00 00 00 51 07 71 14 05 ...Q.q..
0030: 14 1a fd 42 38 35 42 03 ..ýB85B.
0038: 00 01 00 01 16 00 00 00 ........
0040: 00 00 00 00 00 bb 05 9c .....».?
0048: f2 8d 16 1a fd 6a 91 e0 ò?..ýj?à
0050: 44 03 00 01 00 01 16 00 D.......
Does it show opcode as B85B ?
Thanks

Server 2012 R2 iSCSI Target - Multiple targets per iSCSI Virtual Disk with CHAP

Scenario I am trying to achieve is this:
Windows Server 2012 R2 serves as iSCSI Target configured to have 1 iSCSI Virtual Disk
2 Hyper-V servers connecting to this target with iSCSI Inistator and have multiple targets for that iSCSI Virtual Disk using CHAP
**These 2 are nodes in fail over cluster, this iSCSI is added as a CSV.
Issue that I have, is that you can only have 1 target per iSCSI Virtual Disk
Both Hyper-V servers can connect to this LUN without issue when I add both initiator IDs to the target, but once I enable CHAP, you can only put one initiator ID in the "Name" field, so I can only connect from 1 Hyper-V server.
Do you know of a way around this?

From my understanding, "chaptest" is a single target, my goal was to make 2 targets to the same iSCSI virtual disk.
So if you were to right click the iSCSI virtual disk that "chaptest" is assigned to and click "Assign iSCSI Veritual Disk...", then select "New iSCSI Target, and proceed with the wizard it removes the "chaptest" target
and adds the new one just created.
My goal was to have 2 targets to 1 iSCSI VD, but seeing your screenshot, with 2 initiators connected, that goal doesn't seem needed anymore.
I was under the impression that the "User name" = the iscsi initiator IQN name, which had to be unique. That is why I thought I would need 2 targets.
Thanks

DFS & multiple iSCSI targets

Hiya,
A bit of a hypothetical question here.
I have a ReadyNAS Pro connected to my 2008 R2 server via iSCSI (I connect with iSCSI so that I can use MS shadow copies), this target holds my DFS namespace and works well. I now have a 2012 R2 server and have added that as an additional namespace
server, again fine.
What I now want to do is add some failover capacity should the 2008 server go down/need reboot and I was wondering what would be the consequence of adding another iSCSI connection to the same target from the 2012 server? I realise that normally this
would involve clustering to avoid corruption (no experience here) but because it's a DFS would this still apply?
TIA
Baz

Hiya,
A bit of a hypothetical question here.
I have a ReadyNAS Pro connected to my 2008 R2 server via iSCSI (I connect with iSCSI so that I can use MS shadow copies), this target holds my DFS namespace and works well. I now have a 2012 R2 server and have added that as an additional namespace
server, again fine.
What I now want to do is add some failover capacity should the 2008 server go down/need reboot and I was wondering what would be the consequence of adding another iSCSI connection to the same target from the 2012 server? I realise that normally this
would involve clustering to avoid corruption (no experience here) but because it's a DFS would this still apply?
TIA
Baz
You can have DFS running between a pair of Windows boxes and these boxes keeping their content on an individual SMB/NFS shares or iSCSI volumes BUT you cannot easily have access to the same volume @ block level. You may build a cluster between Windows boxes
using your ReadyNAS as a shared storage (that would be a single point of failure BTW) and then you may spawn a failover SMB share between two Windows boxes (you'll have to have the same Windows version however) or continue playing with DFS. You may read more
here:
http://www.starwindsoftware.com/forums/starwind-f5/trying-clear-this-use-iscsi-instead-smb-t1392.html
(has nothing to do with StarWind directly, rather it's generic SAN question).
Hope this helped :)
StarWind VSAN [Virtual SAN] clusters Hyper-V without SAS, Fibre Channel, SMB 3.0 or iSCSI, uses Ethernet to mirror internally mounted SATA disks between hosts.

Multiple Hyper-V 2012 R2 servers to access a since ISCSI target

A couple years ago the community helped me configure a CentOS file server to connect to my VMWare and HyperV Servers for the purpose of backup. At the time I created 2 LVM devices, one to connect to Esxi via NFS, and one to connect to HV via ISCSI. This has worked GREAT!I have converted almost all my production environment to HV. I had to of course rebuild the arrays and make the larger one ISCSI rather than NFS. I just noticed that file the file structure of the connected HV drives is not the same. I have (3) HV Servers connected to the same ISCSI target which resides on the CentOS file server. When you view the connected drives, the same target has different files on it from different HV Hosts. Prior to rebuilding the arrays, the ISCSI target worked as intended. I suspect that I missed a step during the rebuild. The drives were...
This topic first appeared in the Spiceworks Community

Hello,
I have installed VMM 2012 R2, this is also not allowing me to add and manage Server 2012 R2 hosts. However it is perfectly able to manage Server 2008 host.
It gives following error when tried to add Server 2012 R2 hosts:
Error (2916)
VMM is unable to complete the request. The connection to the agent windows2012.test.com was lost.
WinRM: URL: [http://windows2012.test.com:5985], Verb: [INVOKE], Method: [Associate], Resource: [http://schemas.microsoft.com/wbem/wsman/1/wmi/root/scvmm/AgentManagement]
Unknown error (0x80338012)
Recommended Action
Ensure that the WS-Management service and the agent are installed and running and that a firewall is not blocking HTTPS traffic.
This problem can also be caused by WMI service crash. Ensure that KB 982293 (http://support.microsoft.com/kb/982293) is installed on the machine if it is running Windows Server 2008 R2.
If the error persists, reboot windows2012.test.com and then try the operation again.
Any suggestions please?

Question from SAN Newbie

Traditionally we've always used NAS based storage for our server load balancing solutions.
With SAN, is it possible to set up shared storage that can be accessed by multiple servers simultaneously for the purposes of load balancing ? (web/email) I know you can configure individual storage volumes for use by individual servers but this is of lesser importance to us.
Also, which Cisco solution would be required for iSCSI mirroring of SAN data from one site to another ? The throughput of the write-thru is only on the magnitude of about 50Mbps.
Thanks,
= K

In a SAN multi Targets(storage LUN's) can be shared and accessed by multi Initiators(hosts) Clustering software on the host or SCSI reserve methods are used to lock that area on the disk so only one write operation can be working at a time. For reads all can be readin at same time. There are many ways to balance the I/O's to the targets on the SAN. As for mirroring with iSCSI where there is a local SAN connected Target and a iSCSI connected Target the I/O is sent to both, local copy and remote copy for reason of backup, what the application is to do this could be as simple as NTbackup. If your really wanting to push a backup or replication of the data from SAN to SAN then you would use FCIP protocol along with a application data mover on the array or a package like Veritas.

ISCSI Multiple Targets - Multiple

Similar Messages

Maybe you are looking for