Remote Copy new features 3.1.2

[Simi]

Does anyone have tested the new ability of Remote Copy (starting 3.1.2 GA) to move a Virtual Volume from a Remote Copy Group to another without performing a full resync ?
It was announced in the release notes (p.6 http://bizsupport2.austin.hp.com/bc/docs/support/SupportManual/c03607749/c03607749.pdf), but I don't find any procedure in the User Guide ...
This feature could be usefull as it isn't possible to rename a Remote Copy Group.

[xusarmy]

I would also like to know if this is possible. I have a 2TB LUN replicating that is almost 50% done and hate to have to have it start over.

Thanks in advance,
Todd

[hdtvguy]

It can be done, I am going through it right now for like a dozen RC groups. It is a painful process, but does work.

You run a dismissrcopyvv command with the -keepsnap option that changes the name fo the rcpy snapshot

You then run an admitrcopyvv command passing the source volume and snapshot as well as the target volume and it will use that snapshot for the sync.

One caution, it does not get rid of the saved sv snapshot created when you used the -keepsnap even after you syn several times, you will have to go clean that up yourself after you know wthe RC group has synced.

See pages 269 and 289 of the RC USers Guide for 3.1.2 MU2

[xusarmy]

When you do this, if you are going through the initial sync, this will not work, right?

[hdtvguy]

I have never tried it with inital sync, but I woudl suspect it would not because as soon as you stop the RC group if there was arcpy snap on the target it will get rolled back. Finish the initial sync and then do these steps.