velero: Could Not Recover data in my database

What steps did you take and what happened: [A clear and concise description of what the bug is, and what commands you ran.) When I restore my cluster, all has been restored (my destroyed MySQL pods pods comes back) but my database lose all the data. I use minio Storage and I don’t have any error.

What did you expect to happen: To restore my database’s data

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> or kubectl get backup/<backupname> -n velero -o yaml

Capture-dcran-de-2019-07-24-10-59-58-ConvertImage(2)

  • velero restore describe <restorename> or kubectl get restore/<restorename> -n velero -o yaml

Capture-dcran-de-2019-07-24-11-15-25-ConvertImage

Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.]

velero install \ --provider aws \ --bucket velero \ --secret-file ./credentials-velero \ --use-volume-snapshots=true \ --use-restic \ --snapshot-location-config region=minio \ --backup-location-config region=minio,s3ForcePathStyle="true",s3Url=http://@

kubectl -n default annotate pod/mysql-b66bbcff-bfldx backup.velero.io/backup-volumes=mysql-pv-claim --overwrite

velero backup create test --wait

velero restore create --from-backup test --wait

Environment:

  • Velero version (use velero version): v1.0.0
  • Kubernetes version (use kubectl version): v1.15.1
  • Kubernetes installer & version: Rancher latest
  • Cloud provider or hardware configuration: Minio
  • OS (e.g. from /etc/os-release): Ubuntu 18.04 LTS

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Comments: 18 (9 by maintainers)

Most upvoted comments

@Loken3 we’re not planning on adding support for hostPath. We do support the “local” PV type, which is intended to be a replacement for hostPath, so you may want to look into that.

time=“2019-07-30T13:57:50Z” level=warning msg=“Volume mysql-claim in pod default/mysql-6d6677d959-tj4js is a hostPath volume which is not supported for restic backup, skipping” backup=velero/test group=v1 logSource=“pkg/restic/backupper.go:148” name=mysql-6d6677d959-tj4js namespace=default resource=pods

Thanks for that explanation @Loken3. I know @skriss is looking at how to better handle retain PVs soon, so hopefully we can address this.