Duhaas, I don't think there is an easy way around this.  You have consistent lun on all of your IG.  But obviously there's a clash between lun addresses in your groups.  I guess you have the Host Initiators and RPA initiators in the same Views which is causing the conflict.  Per RecoverPoint Deploying with Symmetrix Arrays and Splitter Technical Notes  See bottom of Page 27 and Top Page 28.  (Paraphrasing here because the doc is locked and can't paste) It's best to have a separate masking view for your RP initiaors view, this give you the advantage of separating host and RPA group flag settings and the ability to use the consistent lun feature.  You should use the same storage group for host and rpa for convenience but different masking view and initator groups. HostView + RP_SG  + HOST_CLU_IG+HOST_PG RPView + RP_SG + RPA_CLU_IG+HOST_PG  So how do we get around this in your case...  It's not easy, but it can be done.  You will need to create a staging initiator group for the new host masking view, you need to remove initiators one at a time from the shared view with RP and into the new initiator group.  Since you're using VMware you can vMotion all the VMs off the host and do this with minimal real risk to the production cluster.  Put the host in maintence mode, remove it's initiators from the shared view IG group, rescan etc. Verify it can see datastores/luns etc  Bring host out of maintence mode, verify you can vMotion and run your VMs.  Repeat for other hosts in the cluster.  Hope this makes sense...
I'm getting a consistent lun violation when I try to move a VMware host from one initiator group to another.  I've learned the reason for this is because I have masking views that contains same lun ids.  My problem now is, how do I go about making it so that I can collapse these initiator and storage groups so the luns can live together.  Here is what I have:  [IMAGE]  I want to collapse DRG4_MV and DRG7_MV into the same masking view and collapse DRG4_R_MV and DRG7_R_MV into same masking view as well.  The _R masking views contain recoverpoint replicated Devices not sure if anything needs to be taken into account with those when moving things around.
Consistent Lun Violation