I'm considering the migration separately from the design, so I asked the question.
This time, we are considering data migration using Snapmirror. The current configuration is below.
A. Production storage (current) Ontap: 9.5P6 FAS8020 Usage for migration: FileServer (CIFS/NFS), ProfileServer (CIFS, NFS)
B. Backup storage (current) Ontap: 9.5P6 FAS2554
C. New production storage Ontap 9.11P3 AFF250
Now from A to B, Snapmirror is implemented.
In order to avoid the current business impact as much as possible, data migration to the new production storage We are considering migrating from B to C using Snapmirror. (It's a Snapmirror cascade.)
I am considering implementing the following flow, but is it correct? Are there any other points to note?
1. Backup storage (current) Ontap version upgrade (9.5 → 9.7) We expect to update to a version that supports Snapmirror to 9.11. Since it is an OEM product and the minimum version that can be downloaded from the support site is 9.7, this version is used.
2. Snapmirror implementation from B to C Create and implement a peer relationship between the cluster and svm. Assuming XDP.
Since various operations are performed only on B and C, it is assumed that there will be no operation or impact on A. After version upgrade of B, SnapMIrror from Ontap:9.5(A) to Ontap:9.7(B) is also supported configuration.
1. I am not using SnapMirror synchronous. All will be Async MIrror. 2. All will be XDP. 3.AFF250(C) will be the Primary storage. I didn't write it down,FAS2720 is present for new backup storage (D). However, there is no need to back up the data migrated from B to C with Snapmirror. Snapmirror to D is not required.