Unsolved
This post is more than 5 years old
5 Posts
0
3391
May 11th, 2012 08:00
VPLEX and Mirrorview/A or /S coexistence
What are the caveats (if any) of mixing Mirrorview with VPLEX on the same VNX arrays?
No Events found!
Unsolved
This post is more than 5 years old
5 Posts
0
3391
May 11th, 2012 08:00
What are the caveats (if any) of mixing Mirrorview with VPLEX on the same VNX arrays?
Top
aap1
12 Posts
1
June 2nd, 2012 19:00
Hi
In general, backend replication technologies are supported with VPLEX Local and VPLEX Metro. Here is a white paper that describes a use-case with SRDF.
Broadly, with the release of the native VPLEX RecoverPoint splitter with GeoSynchrony 5.1, that is another option available to consider to meet the use-case you are describing.
A couple of things to remember in the config you are describing:
1. If you are intending to use VPLEX Metro and Mirrorview between the same two sites, then use only one technology to protect a given volume
2. For volumes that you protect with MirrorView, if the VPLEX virtual volume is migrated then the MirrorView relationship will need to be altered. This is also true when you tech refresh the backend VNX array
3. In this config, we strongly recommend strong change control processes since a change at either the VNX layer or the VPLEX layer will impact the backend replication.
If there are other questions, please let us know.
Regards
Ashish
dkepplin
5 Posts
0
June 3rd, 2012 07:00
For the 2nd scenario: "Alering the relationship following a migration". Are you referring to a Mirrorview volume that is also being used by VPLEX?
aap1
12 Posts
0
June 3rd, 2012 15:00
Yes that is correct - scenario (2) is for a MirrorView protected volume that has also been claimed under VPLEX.
Regards
Ashish
dkepplin
5 Posts
0
June 3rd, 2012 17:00
Do you know of any documents which explain best practices for "coexistence" of Mirrorview and VPLEX?
aap1
12 Posts
0
June 4th, 2012 10:00
I am not aware of any documentation specific to MirrorView with VPLEX.
Regards
Ashish
ankur.patel
2 Intern
•
286 Posts
0
August 22nd, 2013 05:00
I assume VPLEX doesnt see the target lun because its part of the MV relationship, so VNX is likely keeping control of the volume. If you break the mirrorview relationship or promote the volume which you would in a DR scenario VPLEX should see the volume.
When you normally mask a lun to a host that is the secondary, VNX does not allow read or write access to the volume until you failover.
laurent.parasot
6 Posts
0
February 21st, 2014 07:00
Sorry to come back on this old thread... but very few information for coexistance of MV and VPlex .
Iwould know if we need to dedicate specific interfaces to separate MV and VPLex traffic on the SPs ?