glacial slate
I am currently overseeing a migration project in which we are transitioning from FAS2554 to FAS8300 using volume move.
The FAS2554 serves as the destination site for SVM-DR, and we have encountered a limitation with the maximum volume size, capped at 60TB.
Running ONTAP version 9.7P22.
I would like to inquire if there are any potential solutions or workarounds to temporarily increase the volume size limit during the migration process. Recommendations would be greatly appreciated.
bronze iron
No. Is your plan to move data from another model to the 2554 and then to the 8300?
glacial slate
We have temporarily added a CN1610 pair with cluster switches. So, FAS2554 and FAS8300 are now in the same cluster. Using volume move to transfer volumes from FAS2554 to FAS8300, but one volume on FAS2554 has now reached a size of 60TB. This volume is an SVM-DR destination volume.
The volume move on the secondary (to 8300) has copied all data but is stuck at
"cutover_soft_deferred" with the message "Detailed Status: Waiting to Cutover (59.71TB Sent)::
Reason: Preparing source volume for cutover: The volume is involved in a SnapMirror operation and cannot be moved until the SnapMirror operation is complete. Wait for the SnapMirror operation to finish or abort the SnapMirror operation by issuing a 'snapmirror abort -hard true' command. Volume move job at decision point."
Tried snapmirror abort -hard true -destination-path xxx:xx
Error: command failed: Relationship with destination "xx:xx" is not a valid relationship for this operation because it is a
constituent relationship of a vserver SnapMirror relationship.
young quarry
Since it's a SVM-DR relationship you need to use the following for the destination-path:
-destination-path vservername:
So without the volume name but with the colon.
glacial slate
Thank's will look into it 🙂