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
When restoring backup data, downloading it locally and then uploading it again is cumbersome.
I would like a feature in the amazee.io dashboard that allows direct backup restoration without the need for local download and upload.
The text was updated successfully, but these errors were encountered:
Thanks for the feature request. We can look into this possibility to be able to restore the backup into the filesystem of a pod somewhere within the environment for restoration by a user.
We won't ever perform the restoration of the data into any system though, that process would have to be performed by a user still.
As a work around though, the Download button is just a link to a signed S3 download which has a short life time. You can right click the download button to get this signed URL and then use a tool like curl to download the file into one of your pods via SSH.
This download URL is short lived, so you have to be relatively quick or you will have to refresh the page to generate a new URL.
Also, the lagoon CLI offers ways to get this download URL
Firstly list the backups for an environment that have been made available for download (or "restored")
Then get the backup using the backup ID, which will return the download URL for the backup. You can then use this URL with curl or other tools to download directly in a running pod via SSH.
You need to be aware of where you are downloading it in the file system, and make sure you handle the data accordingly so you're not accidentally exposing it, or downloading it somewhere where it will then get backed up by another backup.
When restoring backup data, downloading it locally and then uploading it again is cumbersome.
I would like a feature in the amazee.io dashboard that allows direct backup restoration without the need for local download and upload.
The text was updated successfully, but these errors were encountered: