You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps did you take and what happened:
On attempting to restore a successful velero backup of a namespace with restic enabled, I'm getting the following error in the restic logs:
What did you expect to happen:
A successful, clean restore of all my volumes.
The output of the following commands will help us better understand what's going on:
(Pasting long output into a GitHub gist or other pastebin is fine.)
velero backup describe <backupname>:
Name: knowledgehub-1571946878
Namespace: velero
Labels: velero.io/backup=knowledgehub-1571946878
velero.io/pv=pvc-c615f4f3-f67d-11e9-8225-068a97741dda
velero.io/storage-location=default
Annotations: <none>
Phase: Completed
Namespaces:
Included: knowledgehub
Excluded: <none>
Resources:
Included: *
Excluded: <none>
Cluster-scoped: auto
Label selector: <none>
Storage Location: default
Snapshot PVs: auto
TTL: 720h0m0s
Hooks: <none>
Backup Format Version: 1
Started: 2019-10-24 20:54:41 +0100 BST
Completed: 2019-10-24 20:54:47 +0100 BST
Expiration: 2019-11-23 19:54:41 +0000 GMT
Persistent Volumes: 5 of 5 snapshots completed successfully (specify --details for more information)
Restic Backups (specify --details for more information):
Completed: 2
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
I had the same issue today (backup contained only restic backups no volume snapshots).
When I checked the used backup (your command above) I could see that the volume was empty. I had the volume mounted to the wrong path in the pod, so the container did not write any data to it.
Once there was data on the volume, backup and restores went fine.
However, I think there should be a more graceful way for velero to handle this, instead of failing on restore.
@schaze thanks for that - it's possible we inadvertently introduced a regression around this, as empty restic backups/restores were supposed to be gracefully handled already. I'll look into it.
What steps did you take and what happened:
On attempting to restore a successful velero backup of a namespace with restic enabled, I'm getting the following error in the restic logs:
What did you expect to happen:
A successful, clean restore of all my volumes.
The output of the following commands will help us better understand what's going on:
(Pasting long output into a GitHub gist or other pastebin is fine.)
velero backup describe <backupname>
:Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:
velero version
):velero client config get features
):features: <NOT SET>
kubectl version
):EKS
The text was updated successfully, but these errors were encountered: