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

SnapManager for Hyper-Vバックアップが次のエラーで失敗しました:VMの所有者が見つかりませんでした

Views:
10
Visibility:
Public
Votes:
0
Category:
snapmanager-for-hyper-v
Specialty:
snapx
Last Updated:

環境

 

  • SnapManager for Hyper-V(SMHV)

問題

バックアップジョブが次のエラーで失敗する: Could not find owner of VM 

[12/03/2025 8:00:24 PM, (87)] Retrieving VSS Component information...
[12/03/2025 8:00:24 PM, (87)] VSS Component Path : \CD4F115A-F5DE-47FF-926D-E4635164A850
[12/03/2025 8:00:24 PM, (87)] Retrieval of VSS Component information completed successfully.
[12/03/2025 8:00:24 PM, (87)] Retrieving snapinfo information ...
[12/03/2025 8:00:24 PM, (87)] SnapInfo path is: S:\Hyper-V__CD4F115A-F5DE-47FF-926D-E4635164A850\03-12-2025_20.00.01
[12/03/2025 8:00:24 PM, (87)] Checking if [Cluster)_name] is a clustered system..
[12/03/2025 8:00:24 PM, (87)] Owner of VM [VM_name_1]
[12/03/2025 8:00:24 PM, (87)] Could not find owner of VM VM_name_2[Hyper-V].
[12/03/2025 8:00:25 PM, (87)] Owner of VM [VM_name_3]
[12/03/2025 8:00:25 PM, (87)] Due to error in finding the VM owner, backup will be marked as failed for VMs: NetApp.SnapManager.SmObject, NetApp.SnapManager.SmObject

 

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.