Jump to content
Phishing Emails & YouTube Messages - Fake Giveaway Read more... ×
Search In
  • More options...
Find results that contain...
Find results in...

Argus97

Member
  • Content Count

    3
  • Joined

  • Last visited

Awards


This user doesn't have any awards

About Argus97

  • Title
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Argus97

    Just HOW fragile are Raid 1 and 0?

    I'm definitely interested in backblaze. More concerned about the privacy though, reading through their privacy section I'm not a huge fan of decrypting the data on their end to give to me. For backups, would you recommend just the built in windows backup tool? And does that do incremental backups/delta backups? Or would I have to go through the entirety of the drives every time I backup? Right, no I know Raid is for redundancy. I know if I delete a file on one part of a Raid 1 array, it's gone on the other. I'd treat it as just having 1 drive, and still backup to external drives. My big question comes back to, is it more volatile than a normal drive? Should I not be seeing it as a normal drive, for Raid 1 or 0. Like, is there a chance with a normal drive for a bluescreen or sudden cut of power to just corrupt the entire thing? And does that chance increase moderately with Raid? I want to use Raid 1 so in the case something happens to a drive, I don't need to go through the entire windows set up process again, set up all my stuff, ect. That's the reason I'd go with Raid 1, I know it isn't a backup. For Raid 0, yeah, I'll be storing important files on it. But if I have something like backblaze running, and if I backup every so often to an external hard drive, is that an okay circumstance to have important files on a Raid 0?
  2. Argus97

    Just HOW fragile are Raid 1 and 0?

    Okay, well would you suggest not having Raid 1 on the OS drive? It's not vital to me to have Raid on that one, and I'm assuming the OS drive does a lot more tiny writes randomly when using windows. Writing to Appdata, and general windows files and stuff.
  3. I figured this was the best place to ask. I'm getting a new computer soon with 4 drives, 2 M.2's and 2 Sata SSD's. I was going to set the two M.2's to be the OS drive and have Raid 1 just do if something happens the important stuff will be safe. And I was going to set the two Sata SSD's to run in raid 0, not just for performance, but because I'm super OCD about file origination and I've got about 5TB's of files, and splitting them between two drives and not just having the whole folder tree is going to bother me. But EVERYTHING I read about Raid makes it seem like if you sneeze near a computer with it, or look at it funny it'll break. I was under the assumption that the ONLY thing that breaks a Raid was one of the drives breaking. That's the ONLY way to lose all of the data. But now I keep hearing about if the power is suddenly cut, or if the computer blue screens, ect, THAT breaks it too? The system won't have a battery for the raid controller, and the most I know about the controller from the manufacturer is it's a "Intel Raid Controller." But they said there is no internal battery for it. I assumed if the computer blue screened, or power was cut, it would just act like a normal drive, where if something was being written to it, maybe THAT file would be corrupt, but I keep hearing that the entire array and all of it's data will be lost? I'll definitely be backing up my computer, probably every other week. But at this point I don't know if Raid is even safe, it sounds like not just raid 0, but also raid 1 if the system blue screens will just break. I don't need Raid 0 for the speed, that's just a bonus. I want it so there are less drives in "My Computer" to go through, so it's just 1 drive with everything on it. Is there anything else that isn't as dangerous as Raid 0 to do to combine two drives? And Just HOW fragile are Raid 1 and 0?
×