Moving Volume to another cluster in same management group

[Jim Silvia]

I saw another post on how to do this. I'm trying to migrate volumes to a newer starter kit that has more capacity.

if i edit the volume, goto advanced, and change the cluster it is very fast - much faster than remote copies within the same group take.

I accidentally did this with the VM powered up. I found the docs and it says all ISCSI connections need to be disconnected first though.

Did i just get lucky? Has anyone else run into this?

[Jim Silvia]

I contacted HP about this today and spoke with support.

I didn't/don't have to power down the VMS. Just need to add the new VIP and rescan so that it doesn't use the original VIP of the cold cluster.

Night and day difference on performance in the re-striping. 4 Hours vs a remote copy that was still chugging along after 16 hours.

[Gursanjit S Bajwa]

I am having touble with it when the volumes have dbs and one database becomes suspect while doing the log flush. 

[oikjn]

check to make sure you have configured the new VIP for discovery by the servers having the problem.  Then you have to connect the new iscsi connections to the new VIP for the LUNs in question and remove the old ones.