|
Oddhair posted:WHS is one of the best things to come out of Redmond. True that. It's sad that so many of their slam runs are minority products. SQL Server, Visual Studio, Windows Home Server, Windows Server (I think?) are all home dunks. But then I think of Windows Vista/7, the Zune, and their overall marketing strategy... It's just so sad... I kinda want to invest in them but they're pretty terrible. If I could somehow invest in only the teams that have great products, I would.
|
#
¿
Apr 18, 2010 07:02
|
|
|
|
| # ¿ Apr 26, 2024 01:17 |
|
|
Replacing drives is physically easy. The only thing you might want to be worried about is doing the math about how redundancy plays out if you remove a drive. You might be setting yourself up for a window of no redundancy. All you have to do is give the OS a heads up that a drive is decommissioned or no longer for pool use. I'm not sure if the approval process for that is instant or if it will rebalance then tell you it's okay. So you wait, then pop out the drive, and then add the new one into the pool. So easy.
|
|
#
¿
Apr 19, 2010 19:53
|
|
|
Nope, you would have to reinstall the OS on a new disk using recovery mode or whatever. It would inherit the existing pool (which is duplicated). You can back up your server settings I think. But not the OS itself.
|
|
#
¿
Apr 22, 2010 12:45
|
|
|
That's how it works, for folders you've marked for duplication. You can have it store single copies of files if you want. Also, this approach has certain advantages over RAID. RAID arrays generally can't grow in size and may have strict requirements on what size the participating partitions have to be. WHS can grow however with whatever. Also, RAID needs the RAID controller to stay alive to read the data. WHS drives today can be read by any NTFS reader even if it blows up.
|
|
#
¿
Apr 28, 2010 04:30
|
|
|
No, I don't think so. In the next version of WHS, the innards are a lot more intimate, so maybe. But in today's version, it's a pretty dumb service. Edit: One of the only smart things it does is if you move a batch of files over to the server (like an album's worth of music) it will try to keep all of those files together. So it assumes they'll be read together later.
|
|
#
¿
Apr 28, 2010 05:12
|
|
|
|
| # ¿ Apr 26, 2024 01:17 |
|
|
I love how Windows Home Server has this weird, super active community backing it. It's so unlike Microsoft. 
|
|
#
¿
May 21, 2010 01:57
|
|