Re: Migration to new cluster nodes...

Heino> We have to migrate our existing AFF8080 which has NFSv3, ISCSI
Heino> and CIFS data on it to a new location.

How many nodes in your cluster?

Heino> The plan is to add a temp A300 in the new location, and add it
Heino> to the AFF8080’s cluster with two cluster switches (they are
Heino> sub 200M apart)

That should work, then you just failover LIFs and vol move volumes.  

Heino> ISCSI and CIFS should be fairly simple to migrate, but NFSv3 is
Heino> IP-centric, so as we start the migration volume by volume, the
Heino> data path for some of our vmware host will be extended
Heino> somewhat…

CIFS would be the problem child, since moving it from one node to
another is a client outage.  NFSv3 shouldn't really care.  

Heino> It will go via the AFF8080’s configured IP address over the
Heino> cluster network to the A300 controller that holds the volume,
Heino> and back again.

Until you move the LIF over to the A300... 

Heino> Has anyone tried this with success?

Heino> Of cause another way would be to migrate the VMs from the
Heino> VMWare side, which I would like to avoid if possible, but I am
Heino> a bit worried about the added latency over the cluster network…

I assume your real goal is to move a two node cluster without any
downtime, right?  If so, adding in the A300 (with enough storage!)  to
your cluster should do the trick.

Then it will jsut take time to vol move the data from one system to
another, and then once the physical move is complete, you move it back
again.

I'd probably remove the AFF8080 pair from the cluster before you shut
them down and move them.  Then you just power them up, re-add to the
cluster, and vol move back.

Tedious, but very doable.

_______________________________________________
Toasters mailing list
[email protected]
https://www.teaparty.net/mailman/listinfo/toasters