Is Storage Performance Impacting your volume Move or Cutover?
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 fromASUP volume-move-show-table.xml
or thevolume move show
command if still in progress.
- See when
- 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.
- Find low user workload times to help speed up the operation, as background traffic is automatically throttled in favor of frontend traffic.
- ONTAP is opportunistic and will use available IDLE CPU cycles (IDLE time) for background tasks.
- 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.
- The
- A failed disk being reconstructed can increase throughput on certain nodes, even if not on the same aggregate node utilization can be higher.
Additional Information
- Below are some good additional knowledge based articles addressing volumes move and storage monitoring: