Friendly reminder to regularly make backups of your stuff

Attached: 1539858478990.png (854x655, 630K)

mainly cause if you get pwnd by ransomware you definitely don't want to pay up to those fuckers

Naw, also because HDDs and even SSDs love to suddenly crap out.
In case of the SSD you're lucky when shit is still readable but they also really love to crap out completely which usually is its controller which failed. Then you either can try to transplant a controller from a similar one and save your shit or nothing works and you're fucked.

Yes that too ofcourse.

>ransomware waits until you connect your backup drives and then encrypts them too

i got hit by the Fosshub malware campagin (Classic Shell Menu .exe was replaced by hackers because a FossHub admin had his logins stolen)

lost porn that I literally paid a subscription for to siterip

I use KDEringan to steal this dog for Neon

Attached: A7314CDC-41D2-43EF-9B31-6B6991DE6CDF.png (1200x1200, 153K)

Uh? Install KDE neon?

uwu thanks :3 I hawe rsync set up to backup locally and to server

>he thinks I have data worthy of being backed up

ehehe

Yes

Attached: FA7C5850-976D-421D-A126-5CC4212AAFD3.png (478x456, 407K)

I wish you were a girl cow girl poster

Lol I haven’t backed up data in a decade. Literally don’t I’ve a fuck. If everything got wiped I might even enjoy that.

But alas, I’m not a fucking brainlet and can survive without being a backup Jew

>to steal this dog

Don't you fucking dare

Attached: 1541149750664.png (934x841, 947K)

I have triple redundancy of my data so I'm good. My desktop gets backed up once a day.

The only way I can lose it all is if my house burns. Which the chance of that happening is way low. I have bigger risk of getting in auto accident than my house burning. (which I hope don't happen either).

House fires aren't that uncommon, and there's many other kinds of natural disasters. Most people do get in auto accidents at some point so not a great comparison.

Attached: tornado-damage.jpg (790x411, 76K)

>triple redundancy
>stores it all in one place
so you have one backup

>implying car accidents are uncommon

I want to start a ROM/ISO database.

What's a good place to start?
Thinking about storing it all on a machine with raid 10, 4 drives. It's looking to be about 10 TB of data I need to store, as well. I am also thinking of using SQLite to curate it.

Question is, what kind of hard drives should I grab for it?

this
>get bored
>welp, time to reinstall everything to pass the time
>oh, forgot to save documents... ah well, if its important ill remake them

how depressing

thanks based doggo

t. Wangblows user

way ahead of you based doggo

Attached: ss-small.png (433x247, 46K)

Backups are for pussies

This is how I almost lost all my shit.

I had a raid0 array with two disks using btrfs (with its own partition table). I had another hard drive (the same size as each one of the other discs) where I kept backups. But I realized I didn't do backups regularly enough and I really didn't want to lose any of my data. That wouldn't be good form.
So I thought I'd buy another drive and convert the whole thing to a safe raid10 with 4 drives. So I did. I plugged in the drive, wiped the backup drive and added both to the raid0 pool and started the conversion from raid0 to raid10.*
Some time into this operation one of the original drives started throwing read errors and everything stopped working.
I checked some logs and the SMART data on the drive, bought another drive, lost it in the mail, bought another drive and used ddrescue to copy the failing device to the new one, losing only 65KB of data. I did not have enough SATA ports for all the drives in the array, the boot drive and the new drive so I temporarily unplugged a good drive from the raid array (double checking all the serial numbers which should match the smartctl output of the device).
I hooked up the clone in place of the failing drive and it booted up, the fs worked but could not proceed converting the raid0 profile to raid10 because of checksum errors. This was fixed by performing a scrub, the btrfs equivalent of a chkfs, and deleting the corrupted files (which thankfully was just system data in /nix/store so running my package managers' repair tool downloaded the missing files from the web.
All of this shit takes a long time, even longer baked, and has to be done under fear that you fucked it up and your data is unrecoverable. Drives fail, be ready.

Okay dog, don't shoot.

One to one backup is the most stable, you just need to make it one-click with backup software. There's no reason to deal with the complexity and the hidden failure rate of RAID. But I know the reason why. Because Jow Forums can't deal with wasting 2x space for 1x space, so they waste more money building themselves a raid system while still increasing failure rates.

The only thing I care about on my hard drive is memes and half the fun is finding them

Raid 10 is literally just doubling up drives. It's fault tolderant, I'm not using a controller and there is no "hidden failure rate" as was demonstrated by replacing a failed drive with a copy successfully. Traditional backups are better in other ways. They protect against data being overwritten or erased, with a careless command or unexpected behavior for example. Even if you have raid, deleted files are gone forever.

>They protect against data being overwritten or erased, with a careless command or unexpected behavior for example
I count that as hidden failure rate.