Closed mt190502 closed 1 month ago
I assume snapshot won't work for local provisioner, please use the flag --default-volumes-to-fs-backup
to use fs-backup for the data in your volume.
Yeah. That's worked. Thanks for helps. I reinstalled velero with this parameters:
❯ velero install --provider aws \
--plugins velero/velero-plugin-for-aws:v1.10.1 \
--bucket velero-backup \
--secret-file ./credentials-velero \
--use-volume-snapshots=false --backup-location-config region=minio,s3ForcePathStyle="true",s3Url=http://$(tailscale ip --4 m1):30010 --use-node-agent --default-volumes-to-fs-backup
I tried delete a deployment for backup/restore test. But i get this error
Edit: Postgresql official docker image changes default permissions to 999:999. I changed the folder permissions with this command and the restore was completed:
chmod 777 /opt/local-path-provisioner/pvc.......
Hello.
I am using local-path-provisioner in my Kubernetes environment. I created a local minio server for backups. I installed and configured Velero, but when I take a backup, I get the following warning.
I configured velero this params:
I followed this issue and i convert all pvs type local from hostpath: https://github.com/rancher/local-path-provisioner/issues/85 Is there any way to use velero with local-path-provisioner? Thanks.