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.
For the 2nd scenario: "Alering the relationship following a migration". Are you referring to a Mirrorview volume that is also being used by VPLEX?
I wonder if you could answer a quick question for me ?
I have a customer who is using Mirrorview on a VNX which into which they are introducing a Vplex. The Vplex is seeing the primary Mirrorview Lun but not the secondary. I can't find anything relating to deployment of mirrorview in a Vplex environment so I'm hoping you may be able to help me.
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.
Thanks so much for taking the time to get back to me on this. As you say , Mirrorview is probably keeping control of the volume in this case. I assume his worry is that is the primary fails and the secondary (mirror) kicks in, will the fact that Vplex cannot see the secondary cause DU in some fashion. I can’t find anything specific anywhere. I’ll keep looking. Thanks again for your time. It very kind of you.
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 ?