I've used SRDF/DM a lot. Actually I think it's included in the regular SRDF license, but instead of having data replicating synchronous or asynchronous, there the acp_disk setting which translates to SRDF/DM. And when data is al ost 100% replicated, you switch down your host in order to let the replica get to the full 100%, or you can switch to SRDF/S so it get to the full 100%.

OR Hot push is not an option ? We used to migrate between DMX3 and VMAX 20K, just as fast as RDF. Even thought we are licensed for SRDF/S , OR gave us an option to go to meta devices that had different construct vs the source volume. IE : 4 way meta --> 2 way meta.

I second Dynamox's suggestion of using OR for migration as it gives more flexibility than SRDF.

Thanks RRR,  do you have any documents on how to setup the SRDF/DM  .. we have   existing licenses for  SRDF  which i know we can use...

All i  am looking now is  how to configure  SRDF/DM  between 2 arrays  for data migration to happen...

if you have existing licenses for SRDF then why bother with /DM ? Create RDF pairs in acp_disk mode, when close to completion change mode to sync, shut the host down and you are done.

Dynamox, IMHO /DM is the same as acp_disk, right?

yes

dynamox wrote: if you have existing licenses for SRDF then why bother with /DM ? Create RDF pairs in acp_disk mode, when close to completion change mode to sync, shut the host down and you are done.

That's what I said (or meant to say)