We have NFS, CIFS and ISCSI workloads. NFS and CIFS we can handle with SnapMirror, but iSCSI LUN we would like to migrate with at little down time as possible...
I guess adding the A300HA into the new MetroCluster is a no go?
Maybe we can add the C60 into the existing A300 Cluster, then migrate the data.. then remove the old A300, and convert the C60 to a MCCIP... ?
Suggestions are welcome 😉
#Is there an upgrade path from A300HA to AFF C60 MCCIP ?
amber charm
grand karma
there is no in-place way to do this. You need to set up the MetroCluster in parallel to the existing system and migrate the data. For iSCSI LUNs it will depend on the OS, if you have a Volume Manager or other software mirroring capability, it will be easy. If not, then you need SnapMirror + a short downtime
you cannot setup a MetroCluster if you have any existing data SVMs. The "metrocluster configure" command will fail unless you delete all SVMs on the cluster, that's why there is no way to convert an HA system to a MetroCluster in-place
amber charm
Bummer! 🙂 I though there was a sneeky way to do it... And what about adding the MCC into an existing cluster? If that is possible, moving the LUNs should be easy...
deft geyser
Perhaps setting up Snapmirror Synchronous is an alternative here?
amber charm
Perhaps setting up Snapmirror Synchronous is an alternative here?
Alternative to MCCIP? Well if NetApp would support NFS/CIFS in such a setup, then yes 😉
But yes I agree with you that SMAS in many ways are a better setup than MCCIP... especially with VMWare environments where you can have a setup where the user don't have to determine where their VMs are placed...
deft geyser
But yes I agree with you that SMAS in many ways are a better setup than MCCIP......
What do you mean when you say NFS/SMB isn't supported in SM-S?
grand karma
SnapMirror Sync is not SMas
but SnapMirror sync won't help here because you still have a downtime at some point to switch over your clients to the other side (unless, again, you have a volume manager in your OS that can handle this transparently)
amber charm
but SnapMirror sync won't help here because you still have a downtime at some po...
You are right, but SMas it might be an alternative to MCCIP just not sure if it would work on an AFF? We also have some CIFS and NFS workloads but they are not as critical as iSCSI...
grand karma
yeah, SMas will work with AFF
amber charm
While looking at the 9.17 news I stumbled over Foreign LUN import (FLI)... and it looks like it could be a "solution" to migrate LUNs from a HA system into a MCCIP... but have anyone tried this? Let alone from another NetApp? 😉
grand karma
it works fine, but only for Fibre Channel LUNs. You can expose the imported LUN via iSCSI, but the original LUN must be FC
and you still need a downtime with FLI to map your host to the new system, so it's not nondisruptive
amber charm
bummer
We are close to opting for SMas in favor for MCCIP which seems like a "downgrade"... but the alternative with snapmirrors of countless SQL LUNs and downtime left right and center just isn't an option...
grand karma
for SAN, SMas is actually an upgrade since you have all paths active and won't suffer from APD. It's not changing much in most cases, but when you are suffering from APD and slow re-connects, then SMas can help. It won't do anything for NAS though, which is unfortunate