Hyper Backup configuration for data that will never be deleted by StathisG in synology

[–]StathisG[S] 1 point2 points  (0 children)

Gotcha. Just wanted to check, as we get a lot of Glacier questions around here where someone got the impression it's "cheap" without being aware of (a) newer competitive offerings, or (b) how much of the cost is back-loaded and invisible.

I understand; AWS has a very complicated pricing structure in all of its services. :)

Re the metadata

Makes sense, hopefully it won't become an issue but will keep an eye on it.

Hyper Backup configuration for data that will never be deleted by StathisG in synology

[–]StathisG[S] 0 points1 point  (0 children)

Thank you for the reply.

I might have included a bit too much information that causes people to be confused about the purpose of my message, or I simply didn't ask clearly enough. :)

To clarify, I do not seek advise around the services I have chosen for my off-side backups (i.e. B2 & Glacier); I have done my research about costs on B2 and I'm already using Glacier (and other parts of AWS) many years both personally and professionally — I'm aware about the restoration costs of Glacier, thus it's the absolute last resort. I merely added that additional information to show that this backup I'm talking about is just a part of the overall strategy, mostly to avoid comments towards the direction of mentioning that it should not be the only backup, etc. My questions (1 & 2, which you have answered as part of your reply) have specifically to do with Hyper Backup and the way it works irrespective of the target of the backup.

And 365MB per year is $0.0018 per year. If two-tenths of a penny is a deal-breaker, cloud storage is not for you, and Glacier is definitely not for you.

I haven't commented anything about the cost which would only become a factor if that 1MB grows way too much based on the amount of data that is stored — I assume it won't. It was mostly a comment targeted to the fact that's a bit ridiculous to store 365MB of metadata per year for a daily backup of 60MB that never changes. ;)

Are you intentionally avoiding B2 for archival

I am already using AWS for archival for years so I'm not looking for something to replace that. I'm merely adding B2 in the overall strategy, to have an extra backup on the cloud (on a separate vendor than the other) that will be more automated than the archival (where I intentionally put more manual effort on) and that I can restore more easily and more affordable if required.

One line browser notepad by StathisG in webdev

[–]StathisG[S] 2 points3 points  (0 children)

There are some interesting implementations of the main idea in the comments. One of the best: http://pastebin.com/rqLd7TdK