Transcript:
10 things that block your Happiness
- Self-hatred
- Not being able to let go of the past.
- Not being able to forgive yourself.
- Not being able to value who you are.
- Assuming RAID is backup.
- Not making backups.
- Not verifying backups and finding out restore time.
- Needing other people to validate you.
- Letting other people define who you are.
- Trying to be perfect and to please everyone.
RAID 0 is the best way to ensure data redundancy. It’s what we use at every Fortune500 company and there’s not an issue.
But it’s still not a backup strategy. You should always have a second partition on the server that you sync your data over to. For performance reasons this partition should be on the same RAID 0 array.
Backing up to a different partition on the same RAID array sounds like a good way to lose all your data.
The backup should be physically separate from the original.
Yes, and it should use another type of media, like tape, glass, stone tablets or optical media
We have a bard travel accross the lands and carry out our data by singing epics about it.
That’s a valid backup because it’s a different media, correct?
oral traditions have survived an astoundingly long time, albeit with some bitrot
It shall live on through the generations
As long as you are fine with corruption.
NEVER test your backups. It wears out the tapes faster.
This guy RAIDs
Preferably something geographically separated from the server as well in case of some kind of physically destructive event like a fire.
Most people don’t know this but RAID6 is also a fire deterrent
It also is excellent at keeping out ants.
You rarely see ants in datacenters and its because of all the RAID.
I prefer RAID -1, which is like RAID 0 except that you routinely yank one of the drives so that only the fittest of the bits survive, greatly improving the quality of your data!
Evolution in practice!
what? 🤨
You made me doubt a second
Don’t forget being forced into the office
RAID with parity is technically a backup, just a mostly ineffective one. It’s a backup that allows you to recover from exactly one scenario, single (or double) device hardware failure.
But I definitely understand the mantra “RAID is not a backup”. It’s not what most people think of when they say “backup”.
Validate your backups, do not let them validate you!
Pro tip: Copying a Postgres database while live transactions are interacting with it frequently results in a corrupt backup.
Thankfully I test my Luanti backups.
Edit: I should clarify - My dangerous backup method was a naive file copy. I’m sure there’s a different correct way to do a live backup. I just haven’t checked into it yet, since stopping my Luanti server for a backup is no big deal.
İirc they say dont do live backups as file copying but also docs say you could use filesystem snapshots
Yeah. I knew better, but it just didn’t occur to me until I was confirming my backups later.
Yikes! Thanks for the tip. I’m just starting to learn about Postgres. Think I’ll stick with MySQL or SQLite for now… :o
Choosing to not use something is not a good way to learn how to use it.
In this particular instance, the lesson is to either a) use the provided database tools (e.g.
pg_dumpall) for live backup, or b) bring the database cluster down before you backup the raw data folder.
Seriously? Dammit
- Social media
excuse me but my raid is going to be a backup just to comply with rule 10.
I have read these bullshit self-help self-affirmation and similar posts so often, my brain refuses to read anything related anymore. Had to do like 3 takes until I noticed.
I recently changed my hosting provider and wanted to install the new server from the backups I’ve been creating daily for the last four years. Well, it turned out the backup process got stuck on a lock file in July, 2021. And the email process that should have notified me was broken too. I was so happy I didn’t find this out in an emergency and spent more time testing the email notification this time.
If only my happiness supported non-blocking I/O
