Aller au contenu

BackupFailed#

This alert is used to indicate all the failure states for the velero backup.

Solutions#

  • See the description of backups using : velero describe backups <backup-name>

Example :

toolbox install velero
velero backup get (List Backups)
velero backup describe gitea-daily-schedule-20201123020047 (exp: description of specific backups)
velero backup logs gitea-daily-schedule-20201123020047 ( Retrieve Backup Logs )

  • Check if velero's pods are running : kubectl get pod -n velero

  • Launch the backups to see if the problem persists:

    • Gitea: velero backup create "backup-gitea-test" --include-namespaces gitea --snapshot-volumes=true

    If it is possible to manualy create a backup for Gitea, it means the problem is not present anymore.

  • If the first command doesn't work, try: velero backup create --from-schedule gitea-daily-schedule

    Nb: for other schedule, you can check the name with: velero get schedule

  • Once you've completed the test, don't forget to delete it with: velero delete backup <backupname>

Note

If the alert persists, check if there are any backups other than the scheduled ones.

  • To ensure data consistency, it is imperative to restart Velero after deleting test backups.
kubectl rollout restart -n velero deploy/velero