Pinned topic SVC to SVC Migration
AndersLorensen 270002KG7T156 PostsACCEPTED ANSWER
Re: SVC to SVC Migration2014-05-25T07:01:51Z in response to BrunoMelo
Normally when you move to a new SVC, you just add the new IO Nodes to the SVC cluster as new IO Groups. Then migrate volumes to the new IO Group and remove the old IO Groups.
If you already have 4 IO Groups on the old SVC Cluster, its a bigger issue of course. In that case you have to move the volumes with image mode migrations. In that case you really need to give us some more details to Work with.
chriscanto 120000F8G2279 PostsACCEPTED ANSWER
Re: SVC to SVC Migration2014-05-25T21:49:57Z in response to BrunoMelo
I'd suggest you could use the node replacement procedure to non-disruptively exchange each of the old nodes in the existing cluster for the new node hardware. The only caveat with this approach is that you will need to upgrade the existing cluster to the minimum software version supported by the node nodes, but as you'll need to be on that code level anyway then I don't see that being a problem.
This way your existing cluster lives on as-is, just running on the new node hardware. No host migrations etc to worry about.
BrunoMelo 060000R1NX2 PostsACCEPTED ANSWER
Re: SVC to SVC Migration2014-05-29T20:35:07Z in response to chriscanto
Thank you AndersLorensen and chriscanto,
both answers were very helpful.
I decided to present three options to our customer:
- Install a brand new cluster and use replication to migrate the volumes;
- Include the new nodes on the old cluster adding a new IO Group and then migrate the volumes;
- Use the node replacement procedure to substitute the old nodes by the new ones.
Now the customer is analising the risks and efforts involved on each procedure.
Again, thanks for the help!