Technology
Which posts fit here?
Anything that is at least tangentially connected to the technology, social media platforms, informational technologies and tech policy.
Post guidelines
[Opinion] prefix
Opinion (op-ed) articles must use [Opinion] prefix before the title.
Rules
1. English only
Title and associated content has to be in English.
2. Use original link
Post URL should be the original link to the article (even if paywalled) and archived copies left in the body. It allows avoiding duplicate posts when cross-posting.
3. Respectful communication
All communication has to be respectful of differing opinions, viewpoints, and experiences.
4. Inclusivity
Everyone is welcome here regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
5. Ad hominem attacks
Any kind of personal attacks are expressly forbidden. If you can't argue your position without attacking a person's character, you already lost the argument.
6. Off-topic tangents
Stay on topic. Keep it relevant.
7. Instance rules may apply
If something is not covered by community rules, but are against lemmy.zip instance rules, they will be enforced.
Companion communities
!globalnews@lemmy.zip
!interestingshare@lemmy.zip
Icon attribution | Banner attribution
If someone is interested in moderating this community, message @brikox@lemmy.zip.
view the rest of the comments
Not too surprising. Data backups need to be with different providers. The article seems to think it's not "putting all your eggs in one basket" because the provider had redundancy. But that's not much different from storing physical backups locally because they were stored in a fire-proof safe. Sure you made backups, but by storing them in the same building as the servers means the same disaster that could take out the servers could take out the backups. A "fire-proof" safe will protect it from some things that won't protect the servers, but there are still types of disasters that could take out both, like a big enough bomb rather than just a fire.
What if AWS went bankrupt and the servers were repossessed and sold off with the data spread across all the different new owners of the disparate data centers? What if Amazon just decided AWS was no longer profitable and shut it all down.
Sure that's not going to happen to AWS right now because it's hugely profitable, but a serious US market crash combined with a major escalation by the current administration in the increasing surveillance state in the US which could kill the trust in the company, cause a massive migration to EU based companies and cause the subsidiary company that holds the data to go bankrupt without necessarily killing Amazon as a whole. Those subsidiaries often "run at a loss" even with extremely high income in order to divert profit to shareholders, claim tax breaks on "losses", and eliminate liability to the main company.
The legal proceedings of bankruptcy or other events could put the data in legal limbo for years before it's accessible again.
First of all, the main backup should be on a system you own yourself. Preferably one you have at home, physically.
If this was a self-hosted forum, yes, that's an option. But for professional purposes, a dedicated off-site backup provider is better than having storage at an office site.
In any case, I would still make regular backups of everything to a local storage.
Local storage backups (local to the servers wherever that is, so "relatively local") should be the initial backup, then those backups should be what's synced to the off-site/third-party provider, generally. But it really depends on the types of tech and how those backups are generated.