Closed eemcmullan closed 1 year ago
Restic backup data basically include two parts: the snapshot and the data content (in the data
folder as you shared). The snapshot is a collection of references to the data contents.
For a Restic backup deletion process, which also implements Velero's backup deletion, it deletes the snapshot itself only and doesn't touch the data content. After the snapshot is deleted, the related data content will be orphan, and once a maintenance/prune process runs, the orphan data content will be deleted.
That is to say, it is the expected behavior that you don't see files in the data
folder been deleted.
Thank you for the response.
I'm closing this issue as it works as expected. Feel free to reopen it if you have any further questions
What steps did you take and what happened:
velero backup create backuptest --include-namespaces mssql-persistent --default-volumes-to-restic=true
What did you expect to happen: The Restic backup data to be deleted.
Environment:
velero version
): v1.9.1velero client config get features
):kubectl version
): OCP 4.10.6/etc/os-release
):Vote on this issue!
This is an invitation to the Velero community to vote on issues, you can see the project's top voted issues listed here.
Use the "reaction smiley face" up to the right of this comment to vote.