My home fileserver died (XP-based) which worked great, had a great backup strategy, etc. I thought, hey... why spend the money rebuilding the thing, when I could just get a 1TB HP WHS.

Fast forward 24 hours. I've loaded all my files onto the WHS and start using quicken. About an hour into it, Quicken starts giving me corruption errors.... crap. 8 years of financials in danger.

First search on Google pulls up the corruption issue. Fast forward 24 hours, I have rebuilt my file server and am debating whether or not to wait for a patch or just return the thing and try again in a year.

Overall happy with the device... except for the fact you can't use it as a fileserver... doh!

No wonder Vista is so bad, they still haven't gotten basic file sharing functionality down yet.

I predicted it prematurely in 1999 but Windows 2000 turned out quite good. However Microsoft has hit quality free-fall. While I use XP and generally like it, I would under no circumstances rely on Microsoft these days if I had a business to run. My home file servers run Linux, and I know I can depend on them.

Maybe you should document yourself about how this works before expressing an opinion.

Do you know how exactly Windows Home Server works at the storage level? Based in your statement, it doesn't seem so.

No wonder Vista is so bad, they still haven't gotten basic file sharing functionality down yet

Nice. You have *no idea* what you are talking about. WHS and Vista are not even close to being related. The storage methods used in WHS are completely different than anything MSFT has done before.

This is why I don't use M$.

Do you have any idea how naive that sounds?

Do you honestly think Linux or Apple never has issues with data corruption?

Mac OS X Leopard? that comes to my mind when talking about data corruption.

I haven't seen the bug yet, but I do use Winamp to access my WHS shares. I haven't edited a lot of data, but I've changed a few MP3 tags. No issues as yet, and I have (from memory) 7 drives in the box.

Actually I've been thoroughly impressed with WHS. It's probably one of the only MS products that has really met or exceeded my expectations. My only real gripe with it is the 'Balancing Storage' issue that kills file-copy speed sometimes.

My only real gripe with it is the 'Balancing Storage' issue that kills file-copy speed sometimes.

I despise that.

My WHS only has 3 drives in it ATM, but it still kills the speeds when it's balancing.

...almost to the point I want another system to back it up so I can turn off duplication.

Apple iTunes, Winamp, Windows Media Player 11, Mozilla Thunderbird, Zune Software, Office Excel

....Why would anyone install these apps on a server???

*shakes head*

Alright dude, you bore me. How about reading the KB? "When you use certain programs to edit files on a home computer that uses Windows Home Server, the files may become corrupted when you save them to the home server."

Heh...

So...

Okay.

Skimming the article because you've seen reference to a very similar issue without verifying it's actually the same issue FTW!

Okay, maybe not FTW...but I'm going to go have a cookie anyway.

They didn't... they were using them on client machines to edit files on the server.

*facepalm*

Yeah.

Got that.

Thanks.

*eats cookie*

Heh... There was actually an addendum or warning that came with WHS that alluded to this if I recall correctly.

Basically, you were warned to use the Shared Folders for all file editing, copying, moving, etc...and not to do any of that by manually accessing the server drives or folders, as it bypassed the duplication routines or some such, causing a great deal of problems.

Most folks will probably never encounter this error, but MSFT should definitely have disabled any other means of accessing the shared folders when doing so could cause such problems.

Crossing your fingers and hoping they don't do it just doesn't cut it.

Maybe I am not reading this right but it seems they are saying it happens when you edit IN the shared folders: "This issue occurs if the following conditions are true:• You edit files that are located in a shared folder on the home server."

Under specific circumstance, when customers use programs to directly edit files stored in Shared Folders

I was confusing one issue with another, this line is why. :)

You're thinking of logging into the WHS and editing the files in the standard file system. That is a different issue, and always will be an issue with WHS - it's by design. It's like pulling one drive out of a RAID array, editing files on it and then expecting it to go back into the array without breaking anything. :p

I can tell you from experience that I have hundreds of mp3's corrupted as a result of synchronizing the WHS with my desktop and/or laptop (using SyncToy) as a result of updating the meta data or even adding new files to the WHS share. I'm not a happy camper as I have had to stop the synnchronizing until they come up with a fix, or remove one of the two drives, which defeats the whole purpose of having WHS in the first place.

Don't you mean 'I had hundreds of mp3s...'

"Microsoft urges all Windows Home Server users to back up important data before attempting to store files on the system, which is surely not what potential buyers want to hear."

Yes, this is a complete joke. The point of WHS IS backup.

That's part of WHS, but not the whole point. Just because you store your music there doesn't mean you have a backup of it. Now backups of your PC are stored on the server, but files on the server aren't backed up by anything by default.

That's the purpose of the duplication. :)

...of course, now it's just duplicating corrupted data.

Alright Mr tedious - you switch on replication and it's soft mirrored, which is the whole point. All the other features it offers so far you have included in other windows versions already.

Someone's never used it...

Central backup for all PCs on the network, ability to access the shared files from a specific, free, memorable internet accessible domain name, extensible functionality via plugins for a multitude of additional features....

Already included in other versions?

What brand of crack are you smoking?

Ok so it's soft mirrored. All that means is if one drive on the server goes down it has another copy. That in no means is a good enough backup.

You can put any Win with Terminal Services onto the net, dyndns it, switch the web server on and there you go. In any case - right now the central backup (including PCs and files) seems to be the most worthwhile service. I wished it was based on Server 2008, run a proper hypervisor and offer Terminal Services over HTTPS.

Well, whatever - give me some of those cookies.

You can put any Win with Terminal Services onto the net, dyndns it, switch the web server on and there you go

Hardly that "easy".

Especially for the non-technical.

Sorry. Doesn't cut it. WHS combines ease with home server functionality (Now with Data Corruption!).

If you turn off mirroring (I know that was one of the purposes for buying), will this eliminate the potential problem until a fix is pushed out. You could then turn mirroring back on.

Scooter - all,

I have been thinking about getting WHS and my main concern is this corruption. Am I to believe that if you turn of mirroring (duplication) then this problem goes away completely between multiple harddrives. As am considering trying to use it mainly as a central server for editing and transfering data between two or more machines. I know there are other soltions out there but for an idiot proof - fully featured small but large storage solution for the price it is very tempting option.

in conclusion can this be achieved and bypass the data corruption until a fix is provided as editing is a necessity for me and backup can take a back seat for now.

I believe the answer is no.

You have to have only one drive in the box while editing on the WHS to forgo corruption.

I have been considering the Drobo with the NAS option because I need more temporary space than 1 terabyte (the temporary limit to WHS b4 the fix if you need to edit)

If you prove me wrong, please post. I would love you hear if someone has tried that.

the other option is to get the WHS and leave the files on the PC's and let WHS do backups (which are not effected by the corruption). When the fix comes out by MS, you can move your files to the WHS.