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

renaming _recent Snapshot の実行中に「 Error : Volume busy 」が発生したあとに SCV バックアップが失敗する

Views:
39
Visibility:
Public
Votes:
0
Category:
snapcenter
Specialty:
snapx
Last Updated:

環境

  • SnapCenter Plug-in for VMware vSphere ( SCV ) 4.4
  • _recent サフィックス付きのバックアップは、同じボリュームで同時に実行されます

問題

  • Error: Volume busy最近のバックアップ名の変更中に「」という警告が検出されました。
Warning: Unable to update backup on SnapCenter Server: Failed to rename the snapshot on volume <VOLUME> on storage system <SVM>. Error: Volume busy. Backup renamed to <BACKUP> to avoid duplicate backup names.
 
4ab9e7b3-9894-4d4b-945f-a04588325c2c.PNG
  • 同じリソースグループのそれ以降A Snapshot copy with that name already existsのバックアップはで失敗します。
  • Job-<JOB_ID>.log エラーを表示します。

[ERR] Snapshot copy operation failed for volume <VOLUME>. Reason: Error: A Snapshot copy with that name already exists.

  • wfe_<JOB_ID>.log エラーを表示します。

Error: Snapshot operation failed [Storage System: <SVM>]Snapshot operation failed for some of the volumes [Storage System: <SVM>] [Volume:<VOLUME>] Error: Snapshot copy operation failed for volume <VOLUME>. Reason: Error: A Snapshot copy with that name already exists. Failed in volume '<VOLUME>', Snapshot copy operation failed for volume <VOLUME>. Reason: Error: A Snapshot copy with that name already exists.

 

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.