Notices by djsumdog (djsumdog@djsumdog.com), page 39

You can bet the owners cashed out and got to live their sick retirement or tried to gamble on something else while missing the mark

eh, some of them might have. People with those types of type-A personalities cannot sit still for long. They’ll start in on part 2 and 3 .. like gambling addicts they eventually gotta lose everything or learn when to cash out.

One startup I was pulled into on the ground floor was funded by a former CEO of Dallas Semiconductors, who funded the startup with his fucking retirement! Seriously man, just get on a plan and fly for a year! (That’s what I ended up doing after I was let go and I didn’t even have a ton-o-money :blobcatsweat:). He was an annoying-as-fuck Steve Jobs wanna-be too.

That’s what the system encourages. Still, I don’t have that drive .. and without people with that drive we wouldn’t have half the cool shit we do. :blobcatshrug:

What if you accidentally rm -rf the drive? What if you get hit by a ransomware attack and it encrypts both of the RAID 1 drives. What if you accidentally delete an entire folder? What if your server catches on fire?

RAID 1 is NOT a backup. I once had a RAID5 array and the power supply failed, marking two of the drives as bad. I lost a good chunk of that data.

Versioned file systems or auto snapshots can be helpful for accidentally deletes, but they won’t help in the case of a fire or if someone breaks into your house and steals your NAS.

You should always have a separate backup drive, that you hook up occasionally, and then unhook and place in a closet or fire proof safe. Create a calendar notice so you are reminded to do this a couple of times a year. If you ever have a failure or a hack or a fire, you’re only going to lose a few weeks or months work of stuff depending on your backup schedule.

You could also use Backblaze and Duplicity if you wanted to have off-site backups on a hosted server (be sure you save off your Duplicity encryption keys and test the restores occasionally).