Search

Volume move job suspend at decision point when NDMP restore operation running
https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/Volume_move_job_suspend_at_decision_point_when_NDMP_restore_operation_running
Command: "volume move show" disappears job suspend at decision point Volume move job at decision point Error: Preparing the source of the volume move for transfer: Restore running on the volume being ...Command: "volume move show" disappears job suspend at decision point Volume move job at decision point Error: Preparing the source of the volume move for transfer: Restore running on the volume being moved NDMP restore operation is running rst Tue Jan 18 16:29:37 CST 2022 /SVM01/volume_prd/ Options (b=0, d, y, H, TCP recv buffer size = 33580, TCP send buffer size = 33580) rst Tue Jan 18 16:29:37 CST 2022 /SVM01/volume_prd/ Tape_open (ndmp)
Slow volume move in Cloud volume ONTAP
https://kb.netapp.com/on-prem/ontap/Perf/Perf-KBs/Slow_volume_move_in_Cloud_volume_ONTAP
Applies to Clustered Data ONTAP (cDOT) Cloud Volumes ONTAP (CVO) Amazon Web Services (AWS) Issue Volume move is slow in CVO
Deleting the FabricPool "[NAME]" will result in orphaned objects
https://kb.netapp.com/Cloud/BlueXP/Cloud_Tiering/Deleting_the_FabricPool_NAME_will_result_in_orphaned_objects
Warning: Deleting the FabricPool "[NAME]" will result in orphaned objects because there is either a pending volume move operation or a pending metadata cleanup after volume move. Use the "volume move ...Warning: Deleting the FabricPool "[NAME]" will result in orphaned objects because there is either a pending volume move operation or a pending metadata cleanup after volume move. Use the "volume move show" command to check the status of the volume move operation or wait for the pending metadata cleanup to complete. If the error persists for more than a few minutes after the volume move operation is complete, contact technical support for assistance.
Volume move fails with error: Tiering not allowed due to FabricPool license
https://kb.netapp.com/on-prem/ontap/DM/FabricPool/FabricPool-KBs/Volume_move_fails_with_error__Tiering_not_allowed_due_to_FabricPool_license
Applies to ONTAP 9 FabricPool Issue Volume move fails with Replication encountered an unknown error. Volume access error. (Tiering not allowed due to FabricPool license.)
Volume move of ONTAP s3 capacity tier volume results in object.store.unavailable
https://kb.netapp.com/on-prem/ontap/da/S3/S3-KBs/Unable_to_connect_to_the_object_store_local_ontap_s3_Reason__Internal_server_error
Applies to ONTAP 9 ONTAP s3 Issue During volume move of capacity tier volume (ONTAP s3) the object store becomes unavailable.
Volume move fails with error "Not enough space in the volume or aggregate"
https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/Volume_move_fails_with_error_Not_enough_space_in_the_volume_or_aggregate
Source and destination aggregate avail size also exceeds volume total size. /vol/volume_move/.snapshot 0B 0B 0B 0% --- tpemisfs32 aggr_ssd_dst/.snapshot 0B 0B 0B 0% Volume move still fails with error ...Source and destination aggregate avail size also exceeds volume total size. /vol/volume_move/.snapshot 0B 0B 0B 0% --- tpemisfs32 aggr_ssd_dst/.snapshot 0B 0B 0B 0% Volume move still fails with error "Not enough space in the volume or aggregate" in EMS log 5/17/2021 12:57:29 Netapp-2 ERROR mgmt.vopl.move.nospace: The 'volume move' operation with ID '14748' for volume 'volume_move' present on Vserver 'vserver' cannot proceed (Reason: Not enough space in the volume or aggregate).
Why does volume move copy cloud tiered data on releases 9.6 and above
https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/Why_does_volume_move_copy_cloud_tiered_data_on_releases_9.6_and_above
However there are few conditions that can make the volume move to be unoptimized, where all the data in cloud tier will be copied to performance tier and then copied back to cloud tier based on the ti...However there are few conditions that can make the volume move to be unoptimized, where all the data in cloud tier will be copied to performance tier and then copied back to cloud tier based on the tiering policy. For configurations using AWS S3, if the source FabricPool was created on releases earlier than ONTAP 9.5 and the destination FabricPool was created on releases ONTAP 9.5 and above, then the volume move between these FabricPools will be unoptimized.
Why do volume names have (1) appended to the end of them after they are moved?
https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/Why_do_volume_names_have_1_appended_to_the_end_of_them_after_they_are_moved
If an existing volume is moved across aggregates within the same node by running the volume move command, the name of the moved volume will have a number such as (1) appended to the end of the volume ...If an existing volume is moved across aggregates within the same node by running the volume move command, the name of the moved volume will have a number such as (1) appended to the end of the volume name. If you have a CIFS Vserver with an "Engineering" volume and an NFS Vserver with an "Engineering" volume, and they are both on the same node, one of them would have a (1) appended to it from the node level, but from the cluster level (with a volume show), both would show "Engineering".
FlexClone parent volume becomes Unavailable after volume move
https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/FlexClone_parent_volume_becomes_Unavailable_after_volume_move
The output of "volume clone show" lists unavailable parent snapshots after a volume move of the parent volume. Parent Parent Parent Vserver FlexClone Vserver Volume Snapshot State Type vs3 flexclone_v...The output of "volume clone show" lists unavailable parent snapshots after a volume move of the parent volume. Parent Parent Parent Vserver FlexClone Vserver Volume Snapshot State Type vs3 flexclone_volA vs3 moved_parent_temp__3586__65835__volA (unavailable) online RW flexclone_vol1 vs3 moved_parent_temp__3603__66062__vol1 (unavailable) online RW FlexClone Parent Volume: moved_parent_temp__3586__65835__volA FlexClone Parent Snapshot: (unavailable)
SnapMirror updates are failing after moving the source volume to another aggregate
https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/SnapMirror_updates_are_failing_after_moving_the_source_volume_to_another_aggregate
SnapMirror is failing with the error after a successful volume move operation on the source: Failed to get transfer Snapshot information from source volume "Source_SVM:Source_Volume". (Failed to get v...SnapMirror is failing with the error after a successful volume move operation on the source: Failed to get transfer Snapshot information from source volume "Source_SVM:Source_Volume". (Failed to get volume attributes for 07hf1b4c-z3qc-12e6-a3c6-70f076a67jd8:Source_Volume. (Volume location not found. Either the system is busy or the peer cluster is not Available. If the volume is on a remote cluster, before retrying the operation, use the "cluster peer show" command to check the availability.))
Volume move too slow or not working
https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/Volume_move_too_slow_or_not_working
Applies to ONTAP 9.5 ONTAP 9.6 Volume move Issue Volume move operation appears not working or very slow when bandwidth throttling is enabled Volume move is stuck in replicating phase - after moving a ...Applies to ONTAP 9.5 ONTAP 9.6 Volume move Issue Volume move operation appears not working or very slow when bandwidth throttling is enabled Volume move is stuck in replicating phase - after moving a small amount of data the replication does not progress There is no error or failure/hang seen for the volume move