201
Living Room / Re: Talents and talent shows
« on: August 22, 2014, 03:21 PM »
I'm onboard with all that 40hz. ![cheesy :D](https://www.donationcoder.com/forum/Smileys/fun/biggrin.gif)
- Oshyan
![cheesy :D](https://www.donationcoder.com/forum/Smileys/fun/biggrin.gif)
- Oshyan
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
It's like selling 3D content that plays in a regular TV, but is way better in a 3D TV, that may never be produced.-Renegade (September 26, 2013, 09:58 AM)
Just compare RAID to any other backup tool (online cloud, "realtime" file synchronization, etc.), and imagine a case where you are dealing with critical data being generated/processed at a high volume.Which is exactly what makes it suitable and potentially necessary for enterprise environments and *not* for home users. How many home users do you know of that fit that criteria, "data being generated/processed at high volume"? I am one of the most demanding computer users I know and even I don't think RAID is worthwhile on my system, and I spent more than $3000 for it, so easily could have afforded it. If by "data" you're talking about lots of small files (e.g. you're a coder), then I'd still advocate a software solution in that case, because you can use a realtime local versioning system (*not* a DVCS), which accomplishes the same goal *and* improves your work by providing back versions.
Sometimes the greater the level of protection afforded, the greater the problems created should it ever fail.(and other stuff 40hz said)
Or as a friend of mine once put it: Slay one monster and it's only a matter of time before a bigger monster take its place.
Rebuilding a RAID array does degrade performance to a mildly noticeable degree...but restoring from backup - especially an image backup - completely annihilates it. Progress and performance are both exactly zero as you sit about twiddling you thumbs waiting a few hours to get on with your life. And that's only after you get back from the hard drive store (with the replacement) which will hopefully still be open at whatever ungodly hour the thing decides to go poof at.Unless you keep a spare drive around in the RAID scenario, you'll run in degraded mode until you replace the drive, which is riskier. You could keep a spare drive around for recovery in both scenarios. Also, RAID on the boot volume? Another complication. I was sort of assuming we're RAIDing our critical data store, and thus "full system image" backup isn't necessary. Use a simple sync "backup", your backup drive is then a 1:1 copy of your data, and you can just flip it over to primary if your main data store disk fails. In other words, the issues you point out - if they are even really issues for the home user - can be mostly dealt with using simple software and configuration strategies. That being said, I would still contend that downtime concerns of that significance are really fairly exclusive to enterprise use. After all, what home user can't just go out for a movie while their backup restores?