Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FS backup Kopia uploader -- fallback to full backup if previous snapshot is not found #7094

Closed
Lyndon-Li opened this issue Nov 14, 2023 · 0 comments

Comments

@Lyndon-Li
Copy link
Contributor

Lyndon-Li commented Nov 14, 2023

For FS backup, a repo snapshot ID from the previous backup is passed to Kopia uploader as the parent of the current backup, so as to run the current backup incrementally.
Then Kopia uploader tries to get the snapshot from the repo, if the snapshot is not found, the backup will fail. Ideally, if the previous snapshot is not found, it should fallback to a full backup.

Error logs are like below:
time="2023-11-06T04:00:56Z" level=error msg="Error backing up item" backup=velero/backup-xxxxx error="pod volume backup failed: data path backup failed: Failed to run kopia backup: Failed to load previous snapshot 889cc6da7944acb1326a71a2ecdbed1c from kopia: snapshot not found" error.file="/go/src/github.com/vmware-tanzu/velero/pkg/podvolume/backupper.go:324" error.function="github.com/vmware-tanzu/velero/pkg/podvolume.(*backupper).BackupPodVolumes" logSource="pkg/backup/backup.go:448"

Only FS backup is affected, data mover backup doesn't have this problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant