This post is more than 5 years old
19 Posts
0
894
November 21st, 2012 07:00
MirrorView through single MV port
Hi,
Is it possible to configure MV, so that it repl traffic is only sent through one SP?
I'm looking to add MV to a preprod environment, and can only afford to upgrade a pair of switches to support IVR (replacing SPA side 9124s with 9222i). Is it possible to config MV to send through one SP?
No Events found!
christopher_ime
2K Posts
0
November 21st, 2012 15:00
Yes you can by simply not setting up the connection between SP B and SP B. However, keep in mind that SP A will need to own all LUNs on both the PROD and TGT array. In other words, MV can't be configured to send data via SP A for a LUN owned by SP B.
Hope this makes sense.
ScottHolmanColt
19 Posts
0
December 18th, 2012 01:00
I thought it might be possible. I had assumed the LUN would have to be owned by the connected SPs. Is this something that you've tested?
christopher_ime
2K Posts
2
December 18th, 2012 03:00
We wouldn't recommend it on the basis of lack of redundancy and having to run everything on one SP; however, I know you understand that. As for being tested, sure but only from the perspective of assuming it is a temporary condition. A test case would be to not only verify that the array works with both SP's talking to its peer (SP A -> SP A and SP B -> SP B) but also we have to assume and test for example, the connection between an SP and its peer being disrupted for whatever reason. We need to make sure that the array can at least temporarily handle this situation. What you plan on doing is no different, it is just intentional. Also, if you were to consider it, any reference to maximums (mirrors, cg's, etc.) I'd divide those numbers by two to be safe since they assume a (generally) balanced load and again if one SP pair were to handle the load it would be temporary.
Maybe we need to revisit the architecture. For instance, even though as I understand it you potentially will have just the one fabric for replication, unless you are also using the other MirrorView port for host connectivity and want to keep them separated (which we don't restrict you from doing, it is just SAN Copy we don't allow running simultaneously on the same port), you are probably better off putting both MirrorView ports on the same fabric. It is the same amount of traffic from the fabric's perspective but from the array's point of view, you are spreading the load and not having to assign all your source (and target) LUNs that you are mirroring to a single SP.
DELL-Sheron G
Moderator
•
228 Posts
0
December 19th, 2012 22:00
I have been working on a case where we had connectivity from only one SP port, it was via iscsi that these clariions talked and the delay was so slow, the delta time that I saw for the two clariion SPID's was over the roof.
Finally I had him convince that we gotta use bot the ports and balance the load, now as we had done this everything is good.
Hope this helps,
Sheron Godfred
ScottHolmanColt
19 Posts
1
January 9th, 2013 08:00
Doh! Of course! Obvious now you mention it. Slot both MV ports into the same fabric. Job done. This is preprod afterall. Sometimes I need someone to poke me with a stick to wake up.
Thanks, Scott