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

TridentProtect バックアップが Kopia のアクセス許可拒否により失敗

Views:
Visibility:
Public
Votes:
0
Category:
astra_trident
Specialty:
snapx
Last Updated:

環境

  • NetApp TridentProtect(Kubernetes/OpenShift)
  • Kopia Data Mover Pods
  • SecurityContextConstraints(SCC)を使用するOpenShiftクラスター
  • バックアップリポジトリとしてS3/Generic S3を使用する環境

問題

  • TridentProtectバックアップジョブは、バックアップ前のWebhook、ボリュームスナップショット、およびPVCクローン操作が正常に完了しているにもかかわらず、Kopiaデータムーバー段階で失敗します。Kopiaポッドのログに以下のエラーが記録されています:

Unable to createlogs directory: mkdir /app/logs: permission denied

ERROR errorconnecting to repository: repository not initialized in the provided storage

write error: unableto open log file: open /app/logs/cli-logs/...: no such file or directory

ERROR unable toconnect to repository: unable to write config file: unable to create configdirectory: mkdir /app/config: permission denied

ERROR openrepository: repository is not connected. See https://kopia.io/docs/repositories/

  • TridentProtectコントローラーのログには以下が表示されます:

failed to get kopiasnapshot ID from pod logs: summary line with snapshot_id not found in Kopia logoutput

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.