Ending Amazon backup?
Does it make sense to continue Amazon back up - is backup in this manner needed? is there a better UW solution? eg lolo
Overall, I think it's worth it to at least have an archive of important raw data.
I think the biggest downside to using Amazon Glacier in the way that we're currently using it is that syncing/retrieval relies on Synology's system to do so. For example, if we decided to switch NAS manufacturers, I don't think we'd be able to actually "open" data in the Glacier archive that was put there by the Synology service.
We could/should certainly explore a means by which to perform the data syncing without relying on the Synology package. This would apply to using Lolo, as well.
Anyway, I'll look into a price comparison of the two.
We are paying out 70/month for amazon.. does it make sense to consider other option?
Possibly. That backup has terabytes of data backed up, so pricing for that amount of data is costly.
Maybe we just buy another "small" Synology NAS and backup Owl to that? We'd probably break even on the costs in 2 -3 yrs?
but is that backup of terabytes necessary?- and/or why not just sync to gannet?
I think the priority is/was backing up nightingales. That's 14.05TB of data.
Gannet has ~50TB of available space. So, we could definitely sync to Gannet...
lets go ahead and end this
FYI - I'm actively working on this. Turns out, you can't just delete Glacier vaults if they contain any archives.
Buuuuut, you can't easily delete archives! You have to interact with the vaults via the aws command line and delete individual archives. Once all the archives in a vault have been deleted, then you can delete the vault...
Anyway, one of our backups has > 3 million archives. Trying to identify, and subsequently delete, all of these results in my job getting killed because it's using up all the available resources in the AWS CloudShell. So, I'm now trying to do this using a free EC2 Instance.
It's all a huge, time-consuming hassle...
Easier to just cancel / renew credit card # :)
On Mon, Apr 7, 2025 at 6:10 PM kubu4 @.***> wrote:
FYI - I'm actively working on this. Turns out, you can't just delete Glacier vaults if they contain any archives.
Buuuuut, you can't easily delete archives! You have to interact with the vaults via the aws command line and delete individual archives. Once all the archives in a vault have been deleted, then you can delete the vault...
Anyway, one of our backups has > 3 million archives. Trying to identify, and subsequently delete, all of these results in my job getting killed because it's using up all the available resources in the AWS CloudShell. So, I'm now trying to do this using a free EC2 Instance.
It's all a huge, time-consuming hassle...
— Reply to this email directly, view it on GitHub https://urldefense.com/v3/__https://github.com/RobertsLab/resources/issues/1889*issuecomment-2784743905__;Iw!!K-Hz7m0Vt54!nawOnzpIGetMG3jHiWH7rMpWQplpTrWNiCQqAd45IN4gzv1PQ_q27O83hT1uOC9jh8sBDQipTdwkNMRpt8N6aFY$, or unsubscribe https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/ABB4PN3MZTL7X7GW4PODAVL2YLZVNAVCNFSM6AAAAAB2HV53VOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOBUG42DGOJQGU__;!!K-Hz7m0Vt54!nawOnzpIGetMG3jHiWH7rMpWQplpTrWNiCQqAd45IN4gzv1PQ_q27O83hT1uOC9jh8sBDQipTdwkNMRpur8EIMw$ . You are receiving this because you authored the thread.Message ID: @.***> [image: kubu4]kubu4 left a comment (RobertsLab/resources#1889) https://urldefense.com/v3/__https://github.com/RobertsLab/resources/issues/1889*issuecomment-2784743905__;Iw!!K-Hz7m0Vt54!nawOnzpIGetMG3jHiWH7rMpWQplpTrWNiCQqAd45IN4gzv1PQ_q27O83hT1uOC9jh8sBDQipTdwkNMRpt8N6aFY$
FYI - I'm actively working on this. Turns out, you can't just delete Glacier vaults if they contain any archives.
Buuuuut, you can't easily delete archives! You have to interact with the vaults via the aws command line and delete individual archives. Once all the archives in a vault have been deleted, then you can delete the vault...
Anyway, one of our backups has > 3 million archives. Trying to identify, and subsequently delete, all of these results in my job getting killed because it's using up all the available resources in the AWS CloudShell. So, I'm now trying to do this using a free EC2 Instance.
It's all a huge, time-consuming hassle...
— Reply to this email directly, view it on GitHub https://urldefense.com/v3/__https://github.com/RobertsLab/resources/issues/1889*issuecomment-2784743905__;Iw!!K-Hz7m0Vt54!nawOnzpIGetMG3jHiWH7rMpWQplpTrWNiCQqAd45IN4gzv1PQ_q27O83hT1uOC9jh8sBDQipTdwkNMRpt8N6aFY$, or unsubscribe https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/ABB4PN3MZTL7X7GW4PODAVL2YLZVNAVCNFSM6AAAAAB2HV53VOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOBUG42DGOJQGU__;!!K-Hz7m0Vt54!nawOnzpIGetMG3jHiWH7rMpWQplpTrWNiCQqAd45IN4gzv1PQ_q27O83hT1uOC9jh8sBDQipTdwkNMRpur8EIMw$ . You are receiving this because you authored the thread.Message ID: @.***>
Hmmmm... I think I read about someone doing that (due to the challenges faced with deleting vaults, particularly those with a very large number of archives in them), but Amazon still sent notices to them. Not sure we want the bills to end up going to collections or something!
Found a Windows-based GUI (fastglacier) that seems to be working and has been running since yesterday morning. However, it will likely take a few (or many?) days to complete the deletion process.
How is this going?
It's progressing...
To clarify, there's a program running that is deleting files from AWS. Due to the archival nature of Glacier, it is a slow process. With nearly 9TB of data, it will take some time.
https://robertslab.github.io/sams-notebook/posts/2025/2025-08-13-Data-Management---Deletion-of-Amazon-AWS-S3-Glacier-Archives/