restore with longhorn volumes is marked as completed before volume is actually restored #8556
-
I use velero to backup and restore volumes managed with longhorn.
backup schedule spec:
At this moment longhorn reports volumes are not ready since actual restore is yet in progress. Volumes are restored successfully after some time, it is only about status of Restore - it is used by argocd health checks, so workloads start to be created before actual volumes restore is finished and fail with timeouts, report degraded state etc since volumes are quite big and take significant time to restore. Not sure if it is an issue of velero, longhorn or snapshot controller, so starting discussion rather than creating an issue |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 3 replies
-
I assume you used the v1.15.0 Velero and the CSI feature is enabled. I suggest using the CSI snapshot data mover function. https://velero.io/docs/v1.15/csi-snapshot-data-movement/ |
Beta Was this translation helpful? Give feedback.
-
Thanks for answering. TBH I'm a bit lost with how it will work with Longhorn that has it's own logic for data restore. Would not velero take data already stored by longhorn in configured backup target and copy to another location thus doubling the space used by backups? So far I've been thinking of having hook in restore that waits for volume to be restored on longhorn side. |
Beta Was this translation helpful? Give feedback.
-
I've finally got it working
in case someone needs it here is the script:
|
Beta Was this translation helpful? Give feedback.
I've finally got it working
in case someone needs it here is the script: