-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Download for S3 Glacier Archive is not functional. #29
Comments
Dear @Vetavize-Robert, We are currently experiencing a partial service downgrade due to recent infrastructure changes. To resolve this issue, we will be shutting down the entire site today. We will notify you as soon as the issue is resolved. Additionally, you can check the service health reports on the status page: |
Dear @Vetavize-Robert, the maintenance is done. the system is fully operational, please check |
The issue with S3 Glacier Archive downloads is unrelated to maintenance. The problem is due to an incorrect error message being displayed. Please note that retrieving an S3 Glacier Archive can take up to 48 hours, so instant downloads are not supported for this type of storage. We are currently working on a fix to display the correct message. |
The fix is implemented, please check |
Dear @Vetavize-Robert, thank you for understanding the nature of the S3 Glacier and the associated download delays. The current setup doesn’t allow for downloads, and we’re sorry for any inconvenience this causes. To better assist you, please provide more details on how you plan to use the download feature and why the S3 Glacier dashboard does not meet your needs. |
S3 Glacier offers the lowest storage cost for our backups that are still 100% under our control. While we only anticipate downloading in an emergency event, we do need to test that our processes work from time to time. We would like to download the file, recover it to a new GitHub, and check to make sure that everything works. Since the zip file is password protected (your service has the password), I would expect that the download would queue, then when the download is ready we would get a link to the zip file with the appropriate password. |
To address the password issue, we can add a "Send password via email" option to the "Cannot download backup archive" dialog, as a quick fix. Please let us know if that will work for you. To address the testing needs, you can restore the backup to a new test repository to ensure everything works as expected, instead of downloading the archive manually. Also, please note that in case of an emergency, initiating the download process from S3 Glacier can take up to 48 hours, which might not be ideal for urgent situations. |
Adding the password via email is a good stopgap solution. The likelihood that an event would occur that would require us to get a backup from your solution is unlikely, so keeping our storage costs as low as possible is our goal. The idea behind S3 was that if your service ever went down, we have a copy under our control that we can restore. This does bring up the point that we should probably store the backup in S3 without a password just in case your service goes down and we cannot get the password. Here is our backup mentality with your service:
Initially we thought that composite storage would allow us to select Cloudback as the Primary and S3 as the secondary. It does not allow us to do that, so for the time being I am just going to take S3 snapshots manually. |
Thank you for providing the details. We will allow Cloudback-managed storage to serve as a primary target in a composite storage setup. Consequently, we anticipate the release of two new features:
We will notify you once these features are available. |
Thank you! You are doing an excellent job. |
Dear @Vetavize-Robert, A "send password" link for S3 Glacier will be released within a month. We will let you know as soon as it is released. |
The new composite configuration is great and works as intended. Thank you for the enhancement. |
Dear @Vetavize-Robert, |
Download works, Slight translation issue:
Should be:
Thinking about it more you may want something like this for clarity:
The received email has the minimum necessary information for the filename and password. It may be nice to also have the repo name. If your user has a few repos and requests in a row, the repo name will help untangle things. |
Dear @Vetavize-Robert, We have implemented the suggested changes. Please review them. We greatly appreciate your contribution. |
Describe the bug
I get an error if I try and download an archive from S3 Glacier.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Archive downloads
Screenshots
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: