You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using Talos on intel NUCs, which unfortunately does not currently have a way of using lvm that does not break updates, leaving file thin as the only option.
The piraeus snapshot doc says file thin is supported, but it looks like shipping is not supported for file thin :
'The storage pool kind FILE_THIN does not support snapshot shipping' next error: Message: 'Backup shipping of resource 'pvc-e57930e5-6772-41e4-8c98-99105b77970a' cannot be started since there is no node available that supports backup shipping.'
I get this when trying to simply send them to an S3 compatible bucket.
What exactly does that imply, where can those snapshot be stored ? Can they be exported in some other way from wherever they get created ?
Is there any other way to remotely backup those volumes (snapshot or not), short of injecting sidecars into every pod with a pvc to manually rsync files over at night ?
Thanks !
The text was updated successfully, but these errors were encountered:
Looks like LINSTOR does not implement the necessary logic for reading the snapshot data and sending to to S3. You could open an issue on the linstor-server project to see if there is any chance of implementing that.
You could use "regular" snapshots, i.e. not sending them to remote locations. That should work with the FILE_THIN pool (assuming you are using XFS as backing FS). You could then have a daemon set watching the directory where LINSTOR stores the volume data and uploading the snapshot files automatically to S3.
Restores would involve a lot of manual work in that case, but should be doable.
Hi,
I'm using Talos on intel NUCs, which unfortunately does not currently have a way of using lvm that does not break updates, leaving file thin as the only option.
The piraeus snapshot doc says file thin is supported, but it looks like shipping is not supported for file thin :
I get this when trying to simply send them to an S3 compatible bucket.
What exactly does that imply, where can those snapshot be stored ? Can they be exported in some other way from wherever they get created ?
Is there any other way to remotely backup those volumes (snapshot or not), short of injecting sidecars into every pod with a pvc to manually rsync files over at night ?
Thanks !
The text was updated successfully, but these errors were encountered: