メインコンテンツへスキップ

バックアップの再設定後に ONTAP SAN VMware 仮想マシンにアクセスできなくなる

Views:
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
san
Last Updated:

環境

  • ONTAP 9
  • VMware vSphere
  • Veeam

問題

  • Veeamバックアップの再設定とテスト後、データストアや仮想マシンにアクセスできなくなる
  • 複数のVMware VMにアクセスできなくなり、ブートに失敗しました。
  • 複数のVMの電源をオフにできず、応答していません。
  • 複数のVMが「File system specific implementation of Ioctl[file] failed」でブートできません。
  • ESXiホストでVMFSハートビートのタイムアウトとアプリケーションのクラッシュが確認されました。
 
ログ出力の例:
  • ONTAP監査ログ:
    PATCH /api/storage/volumes/ab12a23:{ "restore_to.snapshot.name": "daily.2025-1-1_0000" }
  • ESXiログ:
    [vmfsCorrelator] [vob.vmfs.heartbeat.timedout] datastore1[UserWorldCorrelator] [esx.problem.application.core.dumped] An application (/bin/vmx) running on ESXi host has crashed.
  • VM パワーオン エラー:
    Filesystem specific implementation of GetObject[fS] failed.Moduledisk poweron failed. Cannot open disk or one of its snapshot disks it depends on. Could not open or create change tracking file.

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.

 

  • この記事は役に立ちましたか?