Technically, it is impossible to use an active R2 as a source for RecoverPoint.  SRDF changes to the R2 device are bypassing the RecoverPoint splitter, so RecoverPoint cannot keep track of them.

However, you can perform a cold migration (even without a splitter), if you disable SRDF.  It would save on distance, but will require an extensive host downtime.  If you don't have a splitter at R1, the cold migration is the only option anyway, so you might as well do it from R2.

Another option, which you could employ in any scenario, is to pre-sync from R1 using RecoverPoint.  You can do it without a splitter, while your host is live.  It will creates an inconsistent copy of R1 on your VMAX, but that copy will be very similar to your production.  When you perform the actual migration, either from R1 or from R2, RecoverPoint will read both sides, but will copy only tracks that don't match.  Since most of data usually does not change quickly, it will considerably reduce the migration window.

You can reference RecoverPoint Deploying with Symmetrix Arrays and Splitter Technical Notes  -- A05 available on PowerLink.  See page 15: Replicating by both RecoverPoint and SRDF will not work in most cases, and it is likely to lead to data corruption. SRDF target LUNs are read-only to external I/Os. Any changes made to a LUN by SRDF bypasses the RecoverPoint splitter.

Dmitry Abramson