如何确定卷移动是否已优化
适用场景
- ONTAP 9
- FabricPool
- 卷移动
问题解答
ONTAP 9.12.1及更高版本
::> event log show -node * -message-name mgmtgwd.volmove* -severity *
Time Node Severity Event
------------------- ---------------- ------------- ---------------------------
7/26/2022 02:52:05 node-01 NOTICE mgmtgwd.volmove.notoptimized: Volume move operation from source aggregate "aggr3" to destination aggregate "aggr2" of volume "vol1" on Vserver "vs1" might need to copy data from existing objects in the capacity tier.
7/26/2022 02:47:13 node-01 NOTICE mgmtgwd.volmove.optimized: Volume move operation from source aggregate "aggr2" to destination aggregate "aggr1" of volume "vol1" on Vserver "vs1" avoided copying data from existing objects in the capacity tier.
其他版本
在 mgwd.log 文件中搜索以下文本：
[kern_mgwd:info:2140] 0x82e8c1300: 8603e80000000378: WARNING: VOPL::VolMove: 105 Volume Move Job Configuration Information: job serialization id: 89c1038c-ed98-473d-93f3-b6ea92438b19 sourceVolume: myfg__0001 dstAggrName: fp_aggr2 isDestinationPresent: 0 cutover_window: 30 cutover_attempts: 3 cutover_action: 4 balancerMove: 0bypass-throttling: 0skip_delta_calculation: 0old_job_id: 0tiering_policy: alltiering_minimum_cooling_days: 0 isVolMoveByRef: 1 srcVolBufTreeUuid: 5fe73176-fd78-430b-8841-8ded61c44682srcVolUuid: 2e73f3ce-7f50-11ea-806f-00a098d6d485srcVolBtidCookie: 6541 srcPrimaryConfigId: 1srcMirrorConfigId: 0dstPrimaryConfigId: 1dstMirrorConfigId: 0
- 如果 isVolMoveByRef = 1，则卷移动针对FabricPool进行了优化。
- 如果 isVolMoveByRef = 0，则卷移动未针对FabricPool进行优化。