Hi Duhaas Yes, it is possible to add an individual TDEV to multiple storage groups and unique MV's as you are suggesting, providing that the TDEV is not assigned to an SG in a FAST VP Policy - in this case the TDEV can only belong to a single SG in a FAST VP policy. 
I'm looking to do the following:  Storage Group A - TDEV A Storage Group B - TDEV A  Masking View A::IG-A::PG-A::SG-A  Masking View B::IG-B::PG-B::SG-B  The only thing unique about the masking views are the devices inside the storage groups even those they are two different storage groups.  Each initiator group is a group of VMware hosts and the device/devices are VMFS volumes.  Right now my masking views look like:  [IMAGE] The top and the bottom views are the ones i'm looking at, I'm using the same storage group right now, and would prefer to use a different storage group with the top one but with the same devices inside it as the bottom one.  It will give me the ability that as I complete the migration and prepare to enable replication using recoverpoint, I can remove the device from the top view that doesnt have its ports exposed to recoverpoint, essentially eliminating a message like this from recoverpoint:  [IMAGE]  The fact that I used the same storage group for each VMware cluster doesnt allow me to remove the devices from the top group that I'm looking to retire, hence those ports continue to be tagged to the device and I cant seem to actually unmap those ports without unisphere barking, so I'm wondering if my multiple storage group approach would work?
Multiple Storage Groups, same tdev, different masking view...