跳转到主内容

由于xfer_state文件陈旧、根卷移动失败

Views:
2
Visibility:
Public
Votes:
0
Category:
snapmirror
Specialty:
snapx
Last Updated:

适用场景

  • ONTAP
  • 根卷
  • LS SnapMirror

问题描述

  • 根卷移动失败、并显示以下错误:
::> vol move show -volume SVM1_test_root -instance
              Vserver Name: SVM1_test 
               Volume Name: SVM1_test_root
         Actual Completion Time: -
             Bytes Remaining: -
          Destination Aggregate: aggr4
             Detailed Status: Volume move job in setup
Error: Setting up move operation: 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.
  • 无法执行中止、因为没有为此卷运行SnapMirror。
::> snapmirror abort -hard true -source-path SVM1_test _root -destination-path *
(snapmirror abort)
Error: There are no entries matching your query.
 
  • 常规SnapMirror 工作正常、但此根卷的LS SnapMirror失败、并显示目标无效错误。 

::> snapmirror create -source-vserver  -source-volume SVM1_test _root -destination-vserver SVM1_test  -destination-volume SVM1_test _root_LS -type lS
 
Error: command failed: Volume "Cluster1://SVM1_test/SVM1_test _root" not found. (Failed to query transfer status. (Destination is in
an invalid transfer state))

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

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.