News for hackers. Stuff that matters.

A comment on Run Database in GitHub Actions, Persisting Data to S3, and Access It Publicly. Parent comment

Re:Run Database in GitHub Actions, Persisting Data to S3, an... by thrw42A8N on Thursday December 12, 2024 @05:30AM (#42397986)
You can't rely on VPS disk - backups, data retention and recovery is all up to you in case of node failure. There are other much more expensive and much slower products (external networked volumes) that do offer guarantees, but that's additional charge.
[ Parent | on HN ]
Re:Run Database in GitHub Actions, Persisting Data to S3, an... by justinclift on Thursday December 12, 2024 @06:34AM (#42398300)
> backups

Just to point out, if the data is important you'll want backups anyway. Even with S3.

Just in case. :D

[ Parent | on HN ]
Re:Run Database in GitHub Actions, Persisting Data to S3, an... by vbezhenar on Thursday December 12, 2024 @06:54AM (#42398420)
Why would you want backups for S3? Were there data loss incidents?
[ Parent | on HN ]
Re:Run Database in GitHub Actions, Persisting Data to S3, an... by indigo945 on Thursday December 12, 2024 @07:02AM (#42398462)
Well, Amazon might fail as a company at some point and then all your data will be gone. Theoretically.

Much more likely, though, is that you, or some sysadmin at your company, or even some user will accidentally hit the "delete" button on something important, and then without a backup, you can't get it back. Which is honestly the thing that people usually need their backups for, anyway. This is what most "data loss incidents" are: people just messing up and deleting things they shouldn't have. Wetware is much more prone to failure than hardware, after all.

[ Parent | on HN ]
Re:Run Database in GitHub Actions, Persisting Data to S3, an... by vbezhenar on Thursday December 12, 2024 @07:23AM (#42398568)
There are ways to protect against delete or overwrite, for example by using versions.
[ Parent | on HN ]
Re:Run Database in GitHub Actions, Persisting Data to S3, an... by justinclift on Thursday December 12, 2024 @11:52PM (#42406006)
Does that work when the sysadmin fat fingers the deletion of a bucket or account?
[ Parent | on HN ]
Re:Run Database in GitHub Actions, Persisting Data to S3, an... by justinclift on Thursday December 12, 2024 @11:51PM (#42406005)
> Why would you want backups for S3?

In case something goes wrong. ie your account has a problem unexpectedly, or if they do indeed have a data loss/corruption problem, etc.

[ Parent | on HN ]
Re:Run Database in GitHub Actions, Persisting Data to S3, an... by jeltz on Thursday December 12, 2024 @05:38AM (#42398029)
Most VPS providers offer a backup solution.
[ Parent | on HN ]
Re:Run Database in GitHub Actions, Persisting Data to S3, an... by sigio on Thursday December 12, 2024 @07:28AM (#42398591)
Yes, and you never use those, because if the VPS company fails, your backups are gone. So use the backup services of a second (and third) company if you value your data.
[ Parent | on HN ]
Re:Run Database in GitHub Actions, Persisting Data to S3, an... by thrw42A8N on Thursday December 12, 2024 @07:30AM (#42398603)
As I said, that's an additional charge.
[ Parent | on HN ]