




Microsoft details that the following file types are among those affected:

  • Photos
  • Office Outlook files (2007)
  • Office OneNote files (2003/2007)
  • Microsoft Money files
  • Quicken files
  • QuickBooks files
  • Torrent files





Comments     Threshold


RE: HP's Home Server Includes the OS
By afkrotch on 12/31/2007 12:01:58 PM , Rating: 2
The model you described would be an utter failure if there were more than one computer in the network.

Let's say we have 4 computers and one WHS. There are 4 users each accessing file blah.bmp. Each have a copy of the file locally. Each make completely different edits to the file. Exactly what happens when WHS backs up the file? Who's copy gets backed up? Does it attempt to merge the files and corrupt them?

WHS is nothing more than a business product put into homes. WHS is Windows 2003 Server, stripped down of course. I have my own file server at home. It runs Win2k Pro and is on 24/7. I sometimes transfer files locally to the server. Other times I'll save directly to it. WHS is a home product and it should be built around what home users will do.

RE: HP's Home Server Includes the OS
By kkwst2 on 12/31/2007 10:38:40 PM , Rating: 2
Actually, no. It has nothing to do with how many computers are on the network, only how many potential simultaneous users there are. It all depends on the usage model and your goal. For a business share obviously this doesn't make any sense. However, it might make great sense for a home share.

If we're talking about a home product, how likely is it that 4 users are going to use it at once? For me, it would be almost never. My wife, my son, and I would actually never be editing the same file.

However, it is frequently the case that I would want to access a file when I don't have internet access - for instance when I'm on a plane with my laptop. I would want any changes synced to the file server when I get back. To answer the question, if there were multiple copies saved locally, both would be saved, with tags appended to the file name designating which user or computer edited it.

It is certainly based on Windows 2003 but it's not the same product.

At any rate, I guess my comments suggested that I somehow think it's OK that it corrupts files. That's not the case, just that it would not interfere with how I use the product. Of course a product that is designed to back up your files shouldn't corrupt them. While I did suggest that perhaps it wasn't how the product was intended to be used, I wasn't trying to imply that it was OK for files to be corrupted.

I have different ideas than you about what WHS should do and how it should operate. After reading about it, I think it will do what I want. In my original post, I was just trying to clarify what situations the corruption was occurring because I was planning to purchase it and didn't think it would apply to how I would use it. I still think I'll wait until these problems are resolved, but it doesn't look like the current bug would affect me.


Related Articles
