Skip to main content
NetApp Knowledge Base

2 node MetroCluster switchover fail aggregate is busy

  1. Last updated
  2. Save as PDF
Views:
51
Visibility:
Public
Votes:
0
Category:
metrocluster
Specialty:
MetroCluster
Last Updated:

Applies to

  • 2 node MetroCluster
  • ONTAP 9

Issue

  • metrocluster switchover or metrocluster switchover simulate fail with error aggregate is busy

  • Discrepancy between volume location database (VLDB) and WAFL seen with
    ::> set diagnostic
    ::*> debug vreport show
    volume Differences:
         
    Name             Reason   Attributes
    --------         ------- ---------------------------------------------------
    Node-01:vol_CVclone Present in VLDB and WAFL
                     volume busy
                              Node Name: Node-01
                              Volume DSID:1104
                              MSID:123456789
                              UUID: unknown
                              Aggregate Name: aggr_data_is_busy
                              Aggregate UUID: XX-XX-YY-YY-ZZZZ
                              Vserver UUID: XX-XX-YY-YY-ZZZZ
                              AccessType: READ_WRITE
                              StorageType: CLONE
                              Constituent Role: none
     

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.