sanpad,

You can run an Open Replicator hot pull with a control R1 device, even while that R1 device is actively replicating (should be in acp_disk mode), but you won't be able to use frontend_zero detection (inline space reclaim), and you'll most likely have to use the -force flag when creating the ORS sessions. If you suspend the SRDF replication first, and keep it suspended throughout the duration of the ORS sessions, you'll be able to use frontend_zero. Then you can resume SRDF after you've terminated the ORS sessions (or after you've disabled frontend_zero).

Another commonly tactic is to leverage existing replication on the migration source/remote devices... e.g. if you're pulling from an old array that is replicating, use the ORS hot pull donor_update feature to mirror host writes back to the original/remote devices, so that realtime replication continues via the legacy replication technology. Then once your ORS sessions reach a Copied state, disable frontend_zero, create your new SRDF relationships, perform your initial full establish, and switch into your final SRDF mode. Then you can terminate the ORS sessions, and decomission the legacy replication.

Thanks,

- Sean

Thank you for the swift reply,

Can this be applied to the FLM target device which is also using the same OR hot pull technique to migrate the data.

Sanpad, I haven't done it with FLM myself, but yes it should work, with the same restrictions about frontend_zero noted previously.

Thanks,

- Sean