The backup nfs storage class is skipped over PVC. Procedure

[zhangdeshuai1999]

I backup my entire ns in my k8s cluster, velero backup create --include-namespaces . Then I looked at the backup logs and found that the pvc had been skipped. （I saved the backup to minio ，My storage class is nfs ）

[kaovilai]

You need to be using File System Backup or CSI Snapshot Data Movement

No other methods in velero supports NFS volume.

[zhangdeshuai1999]

velero backup create NAME --snapshot-move-data OPTIONS...

[reasonerjt]

Looks like this is working as expected. You chose to use velero to backup the PV via volumesnapshotter plugin and there's no volumesnapshotter for nfs.

Please consider using FS level backup as Tiger suggested.

Let me know if you need more help.

[zhangdeshuai1999]

看起来这正在按预期工作。 您选择使用 velero 通过volumesnapshotter 插件备份PV，并且没有适用于nfs 的volumesnapshotter。

请考虑按照 Tiger 的建议使用 FS 级备份。

如果您需要更多帮助，请告诉我。 Is there any case?

[zhangdeshuai1999]

看起来这正在按预期工作。 您选择使用 velero 通过volumesnapshotter 插件备份PV，并且没有适用于nfs 的volumesnapshotter。

请考虑按照 Tiger 的建议使用 FS 级备份。

如果您需要更多帮助，请告诉我。

You mean to use File System Backup for backup, is there any case that can be used, I think I need help.

[reasonerjt]

@zhangdeshuai1999 https://velero.io/docs/v1.13/file-system-backup/

[zhangdeshuai1999]

This is the process I install, whether I backup file storage class's ns, or I backup ceph block storage's ns. My velero backup describe state is normal without any error, but the following error will occur when I check in logs. After restoring to invalid ns, I find that the data in my pv does not exist.

[blackpiglet]

The error means the Velero backup still tried to back volume by the Velero-native snapshot. https://velero.io/docs/v1.13/file-system-backup/#to-back-up Please check this section. Either use the opt-in or the opt-out way to filter the volumes back-up by filesystem uploader.

[zhangdeshuai1999]

该错误意味着 Velero 备份仍尝试通过 Velero 本机快照备份卷。 https://velero.io/docs/v1.13/file-system-backup/#to-back-up 请检查此部分。 使用选择加入或选择退出的方式来过滤文件系统上传程序备份的卷。

I have tried choosing to join or exit, but there is still a problem.

[zhangdeshuai1999]

该错误意味着 Velero 备份仍尝试通过 Velero 本机快照备份卷。 https://velero.io/docs/v1.13/file-system-backup/#to-back-up 请检查此部分。 使用选择加入或选择退出的方式来过滤文件系统上传程序备份的卷。

nroad: resource: /pods name: /dstp-cas-service-5b8d6f5785-fjblv message: /volume volume-uvvnjm is declared in pod nroad/dstp-cas-service-5b8d6f5785-fjblv but not mounted by any container, skipping

Errors: Velero: name: /ioc-postgres-0 message: /Error backing up item error: /pod volume backup failed: get a podvolumebackup with status "InProgress" during the server starting, mark it as "Failed"

This is an error during join or exit execution

[reasonerjt]

@zhangdeshuai1999 What do you mean by "join or exit"?

To make sure you understand how to use fs backup, could you install velero v1.13.2, try create a workload with one namespace and one PVC with your NFS storageclass and backup that namespace?

If that still fails please collect the debug bundle and we can take a look.

[sseago]

Errors: Velero: name: /ioc-postgres-0 message: /Error backing up item error: /pod volume backup failed: get a podvolumebackup with status "InProgress" during the server starting, mark it as "Failed"

This means that the node agent restarted in the middle of processing a volume. When that happens, the volume backup cannot be restarted, so it will be marked failed.

[github-actions[bot]]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days. If a Velero team member has requested log or more information, please provide the output of the shared commands.

[github-actions[bot]]

This issue was closed because it has been stalled for 14 days with no activity.