Microsoft iSCSI initiator Data synchronization with target - Storage

This is a discussion on Microsoft iSCSI initiator Data synchronization with target - Storage ; Hi, I have couple of queries regarding iscsi initiator behaviour. I shall describe the setup that I have. Initiator PC: iSCSI initiator (installed using Initiator-2.06- build3497-x86fre) running on a pc with XP. Target PC: Third party target software on a ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: Microsoft iSCSI initiator Data synchronization with target

  1. Microsoft iSCSI initiator Data synchronization with target

    Hi,

    I have couple of queries regarding iscsi initiator behaviour. I shall
    describe the setup that I have.

    Initiator PC: iSCSI initiator (installed using Initiator-2.06-
    build3497-x86fre) running on a pc with XP.
    Target PC: Third party target software on a XP pc installed using Star
    Wind Software 3.5.1 Build 20071204.

    I made a USB Pen drive as a target using the Start Wind software and
    set it up for shared read write access.
    On the initiator side I made an "add target" and a "login target" from
    the command prompt to form a session to the Pen drive.

    Now there are two observations I made which I would like to confirm if
    they are correct.

    a) I copy a file to the pendrive at the initiator end. I check the Pen
    drive at the target end to see if the newly added file is seen, but it
    is not.

    I would have to logoff from the session at the initiator end,
    safely unplug the Pen drive from the target machine and then plug it
    back. Only then will I be able to see the file that got copied.

    Does this mean that the target has to be unplugged and plugged
    again to see the changes on the target machine?

    b) Now in this scenario, I copy a file in the target on the target
    machine. I dont see the change at the initiator side.

    I would have to logoff from the session and login again to see the
    updations.

    So, when something is added in the target, does it not reflect
    straight away at the initiators.


    Is using a third party Target software the cause for the above
    problems OR what I see is what everyone else gets?

    Looking forward to comments on these.

    Thanks in advance.

    Regards
    Srinivas




  2. Re: Microsoft iSCSI initiator Data synchronization with target

    You cannot do this with only target and initiator. Period. There's
    nobody either at the target or
    at the other initiator side who'd tell Windows (or other OS) it has to
    purge and invalidate caches
    and re-read MFT as volume content was changed by network writer. You
    either need to use
    Sanbolic MelioFS or DataPlow SAN FS or use NTFS with the third-party
    distributed lock manager
    like MetaSAN from Tiger Technologies. I don't know much about Melio
    cross-tests but from what
    I know StarWind and DataPlow and Tiger Technology have their products
    cross-certified and
    Rocket Division Software guys even have SFS and MetaSAN integration
    manuals available to
    the public download. I think this one:

    http://www.rocketdivision.com/info/StarWind_SFS.pdf

    and also this one:

    http://www.rocketdivision.com/info/StarWind_MetaSAN.pdf

    Good luck and happy SAN-ing

    Arigato!

    -ichiro

    On Mar 13, 8:26*am, srinivas wrote:
    > Hi,
    >
    > I have couple of queries regardingiscsiinitiator behaviour. I shall
    > describe the setup that I have.
    >
    > Initiator PC:iSCSIinitiator (installed using Initiator-2.06-
    > build3497-x86fre) running on a pc with XP.TargetPC: Third partytargetsoftware on a XP pc installed using Star
    > Wind Software 3.5.1 Build 20071204.
    >
    > I made a USB Pen drive as atargetusing the Start Wind software and
    > set it up for shared read write access.
    > On the initiator side I made an "addtarget" and a "logintarget" from
    > the command prompt to form a session to the Pen drive.
    >
    > Now there are two observations I made which I would like to confirm if
    > they are correct.
    >
    > a) I copy a file to the pendrive at the initiator end. I check the Pen
    > drive at thetargetend to see if the newly added file is seen, but it
    > is not.
    >
    > * * I would have to logoff from the session at the initiator end,
    > safely unplug the Pen drive from thetargetmachine and then plug it
    > back. Only then will I be able to see the file that got copied.
    >
    > * * Does this mean that thetargethas to be unplugged and plugged
    > again to see the changes on thetargetmachine?
    >
    > b) Now in this scenario, I copy a file in thetargeton thetarget
    > machine. I dont see the change at the initiator side.
    >
    > * * I would have to logoff from the session and login again to see the
    > updations.
    >
    > * *So, when something is added in thetarget, does it not reflect
    > straight away at the initiators.
    >
    > Is using a third partyTargetsoftware the cause for the above
    > problems OR what I see is what everyone else gets?
    >
    > Looking forward to comments on these.
    >
    > Thanks in advance.
    >
    > Regards
    > Srinivas



+ Reply to Thread