Restoring backups:
NOTE: When restoring backups Velero will not restore objects that are already existing, so whatever you need to restore must be deleted first.
If you are restoring pods from a deployment/statefulset/daemonsets/etc make sure to delete them too. Velero will not delete them automatically and will hang.
Manual:
- Clear up any resources you wish to restore
- Run
velero restore create uptimekuma1 --from-backup uptimekuma --restore-volumes=true
From Schedule:
- Clear up any resources you wish to restore
- Run:
velero restore create --from-schedule general --restore-volumes=true. Optionally add:--include-namespaces postgresql
Troubleshooting
Velero Restore has hanged
Make sure that it is really hanged up, by checking the --details, there is a chance it is just working.
If it is really hanged, follow these steps:
- RUN:
kubectl rollout restart -n velero deploy velero- See if it continues now, if not continue. - RUN:
kubectl rollout restart -n velero daemonset restic- See if it continues now, if not continue. - Delete the restore with
velero delete restore RESTORE_NAMEand confirm the prompt.- After this, delete all the resources that you were trying to restore
- Create a new restore.