#How to migrate (iSCSI) SAN LUNs to new aggregates

1 messages · Page 1 of 1 (latest)

stoic osprey
#
  1. We have the following functioning setup:
  • Openshift with Trident Operator
  • BackEnd configurations using TridentBackendConfig CR
  • ONTAP SAN backends using iSCSI & MultiPath
  • NetApp SVM with 2 aggregates
  • 2 IP addresses/DNS are used for iSCSI

  1. Replacing NetApp aggregates
    The two NetApp aggregates are to be replaced by two new ones.
    The two new aggregates are currently available in parallel.
    2 new IP addresses/DNS have been provided for ISCSI.
    New SAN PVCs/PVs/LUNs are successfully created on the new aggregates.

  2. Migrating existing SAN LUNs to new aggregates
    What steps need to be completed so that the PVCs within Openshift are also consistent?
    Presumably a "move" of the LUNs within the aggregates will not be sufficient?

The official Trident documentation only describes an update of the Trident backend configuration using "tridentclt" to detect the new aggregates.

  • How do I proceed when using TridentBackendConfig CR instead of tridentctl for the backend configuration?
heady wagon
#

why not just vol move the volumes over to the new aggregates and keep the existing IP addresses? That's what I would do

stoic osprey
#

The Netapp aggregates and SVM are provided and managed by an external service provider.
Therefore, they are currently dependent on their design decisions.
According to the service provider, the new aggregates must use independent iSCSI IP addresses.
However, if there is an alternative option where, for example, the IP remains the same, a link to documentation that we could give to the service provider would be helpful.

heady wagon
#

well if they have configured a new cluster then they are right, they cannot use the same IP addresses. Everyone else usually does NDO cluster upgrades with new nodes that bring new aggregates into the existing cluster, which then can be migrated to non-disruptively.
In your case you need to migrate the data to completely new LUNs which is out of scope for Trident. You would need to manually copy everything over, or use SnapMirror and import the LUNs on the destination system.
I think it will be a manual process, and it will be painful (basically you have to migrate every pod/PVC manually)