You can avoid a full sync replication by using the Incremental Attach feature of Replicator.  To do this, you create user checkpoints on both sides of the replication you wish to preserve (in your case, the VG2 and the VG8), then you refresh the checkpoints to get them in sync.  Take a look at the VNX document,Using VNX Replicator.  There's a section on creating a Cascading Replication with Common Base Checkpoints.  This is similar to what you're doing - you want common base checkpoints between the VG2 and VG8 to incrementally start a replication.  Look at the procedure, then test it out with a VNX simulator, to get the process down. Let us know if this helps!  Karl
Hello,  I have a Celerra NSX in Production. It has LUNs on CX3-80. The NSX replicates using Replicator to a VG2 at a DR Site. I am going to migrate Production NSX to new Production VG8. The VG8 is brand new and it will have new Block LUNs on a VNX Disk Array.  The NSX is mostly VDMs acting as CIFs Servers.  I plan to migrate using Replicator following the procedures described in Whitepaper "Migrating data from an EMC Celerra arrya to a VNX Platform using Celerra Replicator". See this link [URL]  This means the NSX will act as source for 2 destinations for sometime. It will act as source for DR VG2 and new Production VG8. Now I do switch over. This means (old) Production NSX becomes Read Only and new Production VG8 becomes Production and read write.  Do I have to do a completely new DR replication with new Production VG8 acting as source and DR VG2 as destination? I would like to avoid this as it affects the DR RPO and RTO.  Any information much appreciated.  Kevin.
NSX to VG8 migration affect on DR Solution