Remix.run Logo
bob1029 7 hours ago

I've always had a relatively bad experience with NAS hardware. Not necessarily due to anything the hardware manufacturer could have done. I have lost entire enclosures to lightning strikes on more than one occasion. Everyone thinks their IT skills are hot shit until they wake up to a closet full of burned hardware in the morning. It is quite a humbling experience if you've never been through it before. There isn't any kind of semiconductor process tech, file system design or RAID configuration that can save you from this. An off-site backup is the only thing that would count, which brings me to my next point.

These days I just store my files in S3. Whether or not this actually costs me more money becomes a very irrelevant shade of grey once I factor in the value of my time and sanity. I prefer having the capability to store and retrieve large files, not spending time maintaining this capability. This is also my "off-site" backup. I am paying for my operational NAS and its backup effectively at the same time. No one doing DIY is remotely close to 99.999999999% durability, even with all the kings horses and men put together.

I often see this urgency with total control pushing tech people into the very systems of oppression they seek to avoid. Putting your bits in some blob storage provider like AWS is not "losing the game" unless you frame it that way in your head. You can frame it as "getting one over on the bad guys" if you are a little bit clever with how you approach the problem. You can compel Amazon host any kind of bits with a sprinkle of AES256 on the client. I've been a customer with them for over 15 years and not once have they rug pulled me. I've never seen a NAS-style solution survive that long without intervention.

throwawayffffas 4 hours ago | parent | next [-]

I don't know dude I am running a NAS for my home, it has taken minimal maintenance. The main benefit is it's local on my LAN, so speed and latency are dictated by the drives and my switch not whatever is happening outside my home.

yjftsjthsd-h 6 hours ago | parent | prev | next [-]

> Everyone thinks their IT skills are hot shit until they wake up to a closet full of burned hardware in the morning. It is quite a humbling experience if you've never been through it before.

> I've been a customer with them for over 15 years and not once have they rug pulled me.

I actually tend to agree with the thrust of your argument, but how is your view of getting your account banned different than others' view of managing a NAS?

10000truths 5 hours ago | parent | prev | next [-]

> I have lost entire enclosures to lightning strikes on more than one occasion. Everyone thinks their IT skills are hot shit until they wake up to a closet full of burned hardware in the morning. It is quite a humbling experience if you've never been through it before. There isn't any kind of semiconductor process tech, file system design or RAID configuration that can save you from this.

A power surge protector?

stavros 7 hours ago | parent | prev [-]

I have a NAS at home with ZFS snapshots and nightly offsite backups. What's so hard about that, or how is it less durable than your S3 solution?

throwawayffffas 4 hours ago | parent | next [-]

Nightly? what happens in between and how many different sites? What happens if your Internet goes down one night? How many parity drives do you have? Will the array survive replacing a drive or will another one die during the sync will you lose data if that happens?

S3 takes replication seriously to a professional level, when you upload a file to S3 the chance of s3 losing it is capped by the chance of a civilization killing asteroid hitting the earth.

stavros 4 hours ago | parent [-]

Yes. Nothing, one site. The backup gets taken the next night. One. Yes. Yes.

What happens if your drive dies just as you're uploading the file to S3? Why are we comparing the durability of S3 to the reliability of my Internet connection, instead of to the durability of rsync.net?

esikich 5 hours ago | parent | prev | next [-]

How often are you testing those backups? What kind of monitoring do you have? Do you pay attention to it? Skip any of those and it's just a prayer.

nubinetwork 4 hours ago | parent | next [-]

They're zfs snapshots, assuming you're actually taking them, a send/recv shouldn't cause any problems... (ignoring the hole_birth and encryption bugs from the 0.6.x days - to my knowledge, they should both be resolved by now)

stavros 5 hours ago | parent | prev [-]

Every day, healthchecks.io, yes.

bob1029 7 hours ago | parent | prev [-]

How much do you pay for offsite backups? How durable are they?

PunchyHamster an hour ago | parent | next [-]

the answer is always "durable enough", purely because the chance of 2 independent backup copies failing at same time is vanishingly small

stavros 5 hours ago | parent | prev [-]

I think around $50/yr for around a TB? It's rsync.net, so I think very durable.