migration from H500 to F800

[Anubhav Ahuja]

Hi Folks, 

We are migrating from H500 to F800 soon. I am trying to understand the process here and have a few questions and need validations to the below steps. Please add if i missed something. 

As per process

1) We will stack the new F800 nodes to the existing cluster with H500 nodes - Question on connectivity - How will the front end connectivity work, will we connect the F800 to the front end switches and leave the connection for the H500 as is. or we take one connection from H500 and move it over to F800. 

2) There will be a node pool created ones the F800 joins to the cluster and data copy/rebalance will take place

3) We will create new file pool policy - so the new writes will only happen on the F800 nodes - Do we need to do any tiering

4) Run the smart pools job so that data can move from the old node pool to the new node pool

5) Once the number of connections drop to 0, begin to remove the interfaces from the smartconnect pool by suspending the nodes

6) Once all the nodes are suspended, smartfail the nodes one at a time and remove them from the cluster 

Please provide any inputs/recommedations. 

Thanks

Anubhav

[mandar kolhe]

Hello Anubhav,

While adding node I would recommend you to add one node at a time and wait for few hours to add another new node. if its non sed node wait at least 2 hour and if its SED node wait for 4 hours before adding another new node. if you add all nodes at a same time cluster might loose a quorum if new nodes and old nodes are in same nodepool. as while adding new node it remains down for instance then comes up. However if you dont have existing f800 node in a cluster you can add them all together but its safe to add one by one.

1 ) You can add the new nodes interfaces in existing network pool, but you should have a sufficient IP address available in that pool. so once you have added new nodes interface you can suspend old nodes from smartconnect so once all clients are drained out from old nodes you can remove old nodes interface from network pool. In case you don't have a sufficient IP address available in network pool which is more likely to be a scenario you can smartconnect suspend one node from all network pools and let all clients drained out from that node then remove old node from network pool and add new node and follow this process for renaming nodes.

yes new node will be formed however data from old nodes will not move unless you target new nodes in file pool policies and let smartpool or setprotect job complete.

Creating tearing it all depends upon your requirement.

6) Remember you have to smartfail last two nodes in pool at a same time. you can refer to KB article (there is one to smartfail nodepool)

Thanks,

Mandar

[Coolgoose]

  Article Number: 000019003 Print Isilon: OneFS 6.5 and later-How to replace nodes in a cluster with nodes of a different type using SmartPools