• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

WHS beginner

Can anybody further confirm this? Ockie?
This is true.

Say on drive 1 you have 10gb of movies, and 10gb of pictures. You hit duplication on the pictures folder. So now Drive 2 has 10gb of pictures on it due to duplication. Drive 1 fails. You lose 10gb of movies, but WHS knows that pictures on drive 1 is duplicated, so it now points to drive 2 instead of drive 1.

However, it will not automatically reduplicate 10gb of pictures from Drive 2 to Drive 3 unless you explicitly tell it to.
 
Can anybody further confirm this? Ockie?

What you have bolded is true.

If everything is duplicated no data is lost in the event of a drive failure. If not everything is duplicated then only what is not duplicated AND exists on the drive that failed would be lost.

Duplication is on a per share basis.
 
If a drive is duplicated and fails the failed drive shows up in the console as failed (or not present, missing, or something - I forget the exact terminology WHS uses). My understanding is that data is not re-duplicated at this point. It's as if WHS is expecting the drive to be 'fixed' and it will find the data intact and go on about it's business.

If you highlight the drive and remove it, only then it will re-duplicate info to a different drive. Is this correct?
 
[LYL]Homer;1033564074 said:
If a drive is duplicated and fails the failed drive shows up in the console as failed (or not present, missing, or something - I forget the exact terminology WHS uses). My understanding is that data is not re-duplicated at this point. It's as if WHS is expecting the drive to be 'fixed' and it will find the data intact and go on about it's business.

If you highlight the drive and remove it, only then it will re-duplicate info to a different drive. Is this correct?
yes, although I am unsure what happens if there is insufficient room for full reduplication.
 
yes, although I am unsure what happens if there is insufficient room for full reduplication.

If you dont have enough room for all the duplication you will recieve an info message and the security icon will turn yellow alerting you to the issue. The drive willl be removed but not all your data will be duped.
 
If you dont have enough room for all the duplication you will recieve an info message and the security icon will turn yellow alerting you to the issue. The drive willl be removed but not all your data will be duped.
is it all or nothing? or will it duplicate what it can until it runs out of room then stops?
 
is it all or nothing? or will it duplicate what it can until it runs out of room then stops?

From what I remember from the whitepaper it does what it can then stops.
And how do you know what was and what was not? Seems like a valid question.

To see what is duplicated/where it is duplicated you will need to use the duplication info addin.
 
I thought the general consensus was to use the largest drive you have for the OS. That's what I did when I set up my WHS in my new Norco case. I used a 1TB WD Black for the OS and currently have 3 additional 1TB WD Greens. It is kind of weird looking at the storage pool and seeing my 1TB OS drive only 23% full while the others are all over 70%, but at least I know I will probably never run into problem with the OS drive being too small.
 
I have mine on a 74GB Raptor.

You have found no issues with space or other problems? I treated this build the same as I do for my desktop. Smaller drive for the OS so as little, to no, data for easy fixes if I need to reinstall the OS.
 
You have found no issues with space or other problems? I treated this build the same as I do for my desktop. Smaller drive for the OS so as little, to no, data for easy fixes if I need to reinstall the OS.

Great minds think alike! :D

I've had no problems because of the drive size. It seems to be 69GB after formatting and WHS uses 73% of the drive space.
 
I used a 80gb raptor at first.....even when it was in beta and had no problems.

I now run 1tb with a 250gb os partition

Only reason I changed is so I could have a large system partition for WSUS, VM's, and some other stuff.
 
i went back to server 2008 from WHS because i wanted an OS that would take full advantage of my 6gb of memory.
 
Back
Top