Skip to main content
NetApp Knowledge Base

Is Storage Performance Impacting your volume Move or Cutover?

Views:
2,029
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
Perf
Last Updated:

Applies to

  • ONTAP 9
  • Volume move slow, stuck at 98%, or not cutting over in time and retrying

Answer

  • Check CPU and disk utilization and latency, and volume latency before and during the volume move via both monitoring tools or live CLI commands.
    • See when vol move was started /triggered and when it completed from ASUP volume-move-show-table.xml or the volume move show command if still in progress.
  • Volume Move is a background process by default and will throttle to user workload when active on the system.
  • If user workload is too high, there may be seen some delays that prevent the volume move from progressing.
  • Volume size can substantially prolong  vol move operations.
    • The vol move operation will be hindered if data is being accessed at the time, i.e. volume in production.
    • Scheduling more than one vol move operation at a time will likely have a negative impact.
  • A failed disk being reconstructed can increase throughput on certain nodes, even if not on the same aggregate node utilization can be higher.

 

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.