Skip to content

Velero

Needs object store provider for backup

Limitations

  • hostPath volumes are not supported, but the local-path volume type is supported.
  • Volumes that are mounted with subPath are still backed up as a whole, not only the subPath

Install

Arch: pamac install velero-bin

Usage

Important: A root-level backup bucket needs to exist. Create a bucket:

mc mb varac/velero

Manual backup:

velero create backup BACKUP_NAME --exclude-namespaces velero --wait

List backups:

velero get backups
kubectl get -A backups

Details of backup:

velero backup describe --details manual-test1
velero backup logs velero-daily-20240924153213

List backupstoragelocations:

kubectl get -A backupstoragelocations.velero.io
velero get backup-locations

List backuprepositories:

k get -A backuprepositories.velero.io
velero repo get

List podvolumebackups:

kubectl get -A podvolumebackups.velero.io

List podVolumes in backup set:

velero backup describe --details -o json manual3 | jq .status.backupVolumes.podVolumeBackups.podVolumeBackupsDetails

Delete backups

Docs: Deleting Backups

Delete the backup custom resource only and will not delete any associated data from object/block storage:

kubectl delete backup <backupName> -n <veleroNamespace>

Delete the backup resource including all data in object/block storage:

velero backup delete <backupName>

Delete whole backuprepository:

kubectl -n velero delete backuprepositories.velero.io/monitoring-default-restic-tqx9l

File System Backup

Restic/Kopia repositorz password:

Solution:

Restic integration

Issues:

Monitoring