メインコンテンツまでスキップ

Snapcreatorがバックアップを開始すると、ONTAP ノードがパニック状態になります

Views:
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core<a>2009187170</a>
Last Updated:

環境

  • ONTAP 9.8
  • Snapcreatorのこと
  • ZAPI
  • 整合グループ(cg)

問題

  • ONTAP ノードのCPU利用率が高く、長期間にわたって100%に近い。
  • Snapcreatorバックアップジョブは、複数のボリュームを整合グループ(cg)としてバックアップするように設定されます。
  • Snapcreatorがバックアップジョブをトリガーし、次に示すcg-commitタイムアウトを参照するSnapcreatorログでバックアップジョブが失敗する場合があります。
[2022-06-06 18:29:11,123] ERROR: STORAGE-02006: Committing consistency group Snapshot copy on controller [cluster] with CG Id [12345678] failed with error [netapp.manage.NaAPIFailedException: Connection timed out (errno=60)]
  • Snapcreatorバックアップジョブに含まれるボリュームを1つ以上ホストするONTAP ノードで、次の状況でパニックが発生します。
Mon Jun 06 19:05:08 +0200 [node-03: splog_main: mgr.stack.string:notice]: Panic string: prod/common/adminapi/ontapi-d/od_volume_exec.c:2504: Assertion failure. in SK process svc_queue_thread on release 9.8P11 (C)
Mon Jun 06 19:05:08 +0200 [node-03: splog_main: mgr.stack.at:notice]: Panic occurred at: Mon Jun  6 18:30:24  2022

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.
Scan to view the article on your device