0

将 velero 从 1.3.2 升级到 1.7.7 后，备份开始失败。在描述失败的备份时：

velero backup describe mypod-20220204170020 --details


Name:         mypod-20220204170020
Namespace:    velero
Labels:       velero.io/schedule-name=mypod
              velero.io/storage-location=default
Annotations:  velero.io/source-cluster-k8s-gitversion=v1.21.2
              velero.io/source-cluster-k8s-major-version=1
              velero.io/source-cluster-k8s-minor-version=21

Phase:  Failed (run `velero backup logs mypod-20220204170020` for more information)

Errors:    0
Warnings:  0

Namespaces:
  Included:  mypod
  Excluded:  <none>

Resources:
  Included:        *
  Excluded:        <none>
  Cluster-scoped:  auto

Label selector:  <none>

Storage Location:  default

Velero-Native Snapshot PVs:  auto

TTL:  168h0m0s

Hooks:  <none>

Backup Format Version:  1.1.0

Started:    2022-02-04 18:00:20 +0100 CET
Completed:  2022-02-04 18:00:41 +0100 CET

Expiration:  2022-02-11 18:00:20 +0100 CET

Total items to be backed up:  64
Items backed up:              64

Resource List:  <backup resource list not found>

Velero-Native Snapshots:  <error getting snapshot info: file not found>

乍一看，备份似乎是正确的：
错误：0
警告：0
项目备份：64 个，共 64 个

但是，在底部（并且仅在使用 describe 命令添加 --details 标志时），您会看到以下两个提及：

Resource List:  <backup resource list not found>
Velero-Native Snapshots:  <error getting snapshot info: file not found>

有没有一些聪明的方法可以进一步解决这个问题？或者有人对这里可能出现的问题有什么想法吗？

  • 在 AKS (1.21.2) 上运行
  • 使用 velero-plugin-for-microsoft-azure:v1.3.1 将快照转换为 azure

非常感激！

4

2 回答 2

0

Not sure if this solves the issue for everyone, but it worked for me. After searching inside the velero source code repo, I located the following go package velero/pkg/cmd/util/output/backup_describer.go that contained the error message I found when describing the failing backup.

See line 328 (1) enter image description here

The hints at (2) in the source code led me to search on upload issues. As I am using the velero-plugin-for-microsoft-azure to handle uploads to Azure the following GitHub issue finally gave me the nudge in the right direction.

Seems like the velero-plugin-for-microsoft-azure required more memory (512Mi) since v1.5.3 (if I understood it correctly). The limits on my one were still at 256Mi and failing, I increased the limits to 512Mi and, presto! It started working again.
A big shout out to David L. Smith-Uchida whose breadcrumbs led me to the solution!

于 2022-02-13T13:37:41.713 回答
0

我需要知道您的数据驻留在哪里意味着它正在使用 azure 磁盘或文件共享。 Velero 不支持 azure 文件共享数据

于 2022-02-26T16:08:31.017 回答