#Has anyone upgraded from a single-node ONTAP Select to a cluster?

1 messages · Page 1 of 1 (latest)

flint marten
#

Has anyone upgraded from a single-node ONTAP Select to a cluster?
If so, what steps did you follow?

sly moth
#

I don't think this is possible without deploying a new cluster and migrating all data over. So, create a new 2-node cluster, configure it as you would normally, then useyour favorite migration method to copy the data over (e.g. for VMs use Storage VMotion, for CIFS / NFS data use SnapMirror, or client side copy tools like RoboCopy or xcp)

flint marten
#

Hi, due to limited space, I am unable to retain the existing node while creating a new 2-node cluster. However, we have a backup NetApp available, where I can transfer all the data using SnapMirror. Once the data is transferred, I will delete the current node, set up the 2-node cluster, and then transfer everything back. After that, breaking the SnapMirror should hopefully make the volumes read-write. I hope this plan makes sense.

Thank you for the response btw.

sly moth
#

yeah, that makes sense. SnapMirror always works. For VMware I would still prefer svmotion, since it is nondisruptive.

cyan lintel
#

sadly, this is correct.
Both CVO and Select do not allow a single node to be migrated to a cluster and you must deploy a new system.

exotic forge
#

SVM DR.

#

Just saying.

glossy fulcrum
#

You meant to say Snapmirror SVM.
Netapp changed the name. I think we all prefer what the original

#

And there’s also the newer SVM mobility

#

(Aka migrate which is not the same as svm-dr/snapmirror svm as you cannot convert it to sm mobility unless something changed)

exotic forge
glossy fulcrum
#

The debating we went through for an exam we wrote. It’s supposed to correct and we spent time to be sure. I still say svm-dr since it sounds Sooo much better then snapmirror svm