06-15-05 10:50 PM
dave_roland_mann@yahoo.com wrote:
> I am trying to settle an argument at the office and I am hoping that
> one of you can answer the question for me. It is fairly basic as I am
> new to this whole SAN thing.
>
> Suppose that I have two windows servers, each connected to a sepearte
> LUN on an MSA1000 (each server can see his LUN but not the other
> servers). Both servers and the disk are connected to a SAN switch.
>
> Suppose I want to copy data from the SAN LUN on servera to the SAN LUN
> on server b.
>
> Does it work this this
> servera -> SAN -> serverb
>
> or
> servera -> SAN -> LAN -> serverb
>
> What data goes over the LAN and what goes over the SAN?
>
> Thanks
> Dave
>
Think of the SAN as a very complex IDE or SCSI cable.
Now think of the LUN's in your SAN as an IDE or SCSI disk drive on that
cable.
For your scenario above it's the same as transferring data from an
internal disk on one PC to an internal disk on a second lan attached PC.
There is no way for the first PC to see the hard disks in the second PC
without going through the LAN and OS.
Note this is not the case in Clustering where 2 or more hosts are
attached to the same LUN for failover. But I don't think this is where
you were headed.
There does also exists Snap copies and mirroring and other such
functions to copy LUNs across the SAN but afaik these are not used on a
file level, but on a LUN level.
So let's see if I can draw your scenario.
ServerA attached to LUN-A, OS calls it the D: drive
ServerB attached to LUN-B, OS calls it the G: drive
ServerA maps a drive across the LAN to ServerB's G: drive calling it E:
On ServerA you xcopy a file from D: to E: and this is the path it takes:
LUN-A -> SAN -> ServerA -> LAN -> ServerB -> SAN -> LUN-B
FWIW, here's what happens with a LUN mirror/copy which is a function of
your SAN's storage processor.
ServerA attached to LUN-A, OS calls it the D: drive
ServerB attached to LUN-B, OS calls it the G: drive
A LUN mirror/copy is initiated to mirror LUN-A to LUN-B. This data
transfer is done over part of the SAN(inside the SAN's storage
processor). When it's completed, and provided there has been no IO to
the source and destination LUNs, ServerA's LUN-A and ServerB's LUN-B
will be identical. Effectively you've copied data across the SAN.
So data flows like this:
LUN-A -> Storage Processor -> LUN-B
Snap images are similar, but the snap image is an array of pointers to
the source data for reading vs. full IO. Takes up less space than a
full mirror of a LUN.
ServerA attached to LUN-A, OS calls it the D: drive
ServerB attached to LUN-B, OS calls it the G: drive
LUN-B is a snap image of LUN-A instead of a separate LUN.
On ServerB you copy a file from G: to a local C: drive and the data
flows like this:
LUN-A -> Storage Processor -> SAN -> ServerB -> Local disk C: on ServerB
Effectively you've copied data from ServerA's LUN-A to ServerB without
going over the LAN.
hth,
tM
[ Post a follow-up to this message ]
|