Tag Archives: MirrorView

Cisco Smart zoning – part II: examples

Posted by on November 5, 2015 4 comments

Smart zoning examples

In my smart zoning post from last February I already presented the way to get started with Cisco smart zoning. I initially planned to give a more detailed calculation on how much time you can save if you were using smart zoning compared to SIST zoning.

SAN fabric

I was talking to an EMC SAN instructor (Richard Butler) this week and after I did a little white-boarding and used my hands to picture how massive a traditional SIST zone environment would be, we agreed smart zoning is the way to go.

Read more »

Checking VNX mirrorview replication progress from the CLI

Posted by on April 1, 2015 No comments

It’s a very short post, but in case you’re looking for the command:

naviseccli -h [SPx ip#] mirror -sync -listsyncprogress -name [LUN name]

 

It’s that simple!

Oh, I’m assuming you already have the logon credentials in a security file, if not, you need to add these to the command:

naviseccli -h [SPx ip#] -user [username] -password [super secret password] -scope [0-1-2] mirror -sync -listsyncprogress -name [LUN name]

CX or VNX Mirrorview with Snapview active on the remote side

Posted by on January 21, 2014 No comments

If you have a primary LUN which is replicated using MirrorView/S and you decide to run SnapView snapshots on the remote side, consider that writes to the secondary LUN may have to wait for the COFW activity to complete before an acknowledgement is sent back to the primary array.

So if you’re performing tests on the remote site by using SnapView snapshots, you may want to consider suspending the MirrorView session(s) first in order to guarantee performance on the production site.

A good scenario would be to create clones from the temporary fractured mirrors and as soon as the clones are fully in sync, split the clone from its primary – being the MirrorView secondary – and start the resync in MirrorView.

MirrorView has to wait for SnapViewAfter the write from the primary array (1) a COFW (Copy On First Write) (2) must take place if the write (1) overwrites a block that hasn’t been written to yet in order to maintain the point in time of the snapshot. After the COFW (2) is complete the acknowledgement (ACK) (3) can be sent back to the primary array.

So even if the snapshot isn’t used by a host, there’s already an increased activity on the remote array.

If the snapshot is in use by a host that writes to the snapshot, an unchanged block on the secondary LUN need to be copied to the RLP (Reserved LUN Pool) first before the overwrite can take place. This will also slow down any ACKs that need to be sent back to the primary array.

Conclusion

Be very careful when starting SnapView sessions on a secondary LUN and even more careful when using the secondary LUNs since it can have a severe impact on the response times of the primary LUN.

EMC VNX Replication

Posted by on October 16, 2012 No comments

I want to bring the discussion about “VNX data replication” to your attention. It’s on ECN and the URL is https://community.emc.com/thread/149825. If you want to ask about replication specifically, you can post your questions here or on ECN.

The author, Rupal Rajwar is USPEED certified and works for EMC eServices Customer Support division since 2010.