Windows Home Server Corrupts Files

crustymonkey points out a ComputerWorld article which says that "Microsoft Corp. has warned Windows Home Server users not to edit files stored on their backup systems with several of its programs, including Vista Photo Gallery and Office's OneNote and Outlook, as well as files generated by popular finance software such as Quicken and QuickBooks." Crustymonkey asks Don't back up your files to Windows Home Server, as recommended by Microsoft themselves? I'm not exactly sure what the point is in having a home server if you can't back up files on it."

Comments

Re:Curious...

[UnknowingFool]

From what I understand from the article is that if you save certain file types to a Home Server for backup purposes from a workstation, you can corrupt them if you edit the original files and try to back them up onto the server again. Well that defeats the whole purpose of having a backup system. Like photos for example. If I backup all my photos onto the Home Server, then I decide to change the contrast on a few of them on my everyday PC, I can corrupt the ones I've saved on the Home Server if I save over the original backups. Then if I decide I need space on my PC and delete the ones saved there, my edited photos are inaccessible if I didn't save them anywhere else.

Re:Curious...

[phuul]

Well since the article NEVER mentions backup I'm trying to figure out why the blurb and everyone is going on about backups being corrupted. What is actually happening is that there is a bug in WHS folder sharing. If you edit files with particular programs that exist on a WHS share the files will be corrupted.

Here is the KB article http://support.microsoft.com/default.aspx/kb/946676/en-us?spid=12624

It too doesn't mention using WHS to backup but does say that you should backup the possible affected files before storing them on WHS.

Sharing was the focus of WHS, not backup.

[Mage...]

First off, the problem is:

You are editing a file that is saved directly to a shared folder on WHS, which WHS accepts and gives the A-OK signal to your software, then later has a problem writing the file, and tells you about it, with no chance of recovering the file at that time. Since this can happen after you have exited your software, you have no way of recovering the file.

The problem is not:

• You make backup files, then try to edit them directly on the WHS share folder.
• Your backup files get corrupted.
• You are doing something that WHS was not intended for.

The third one is the trickiest. See, if you go to the current WHS Discover site (click Help and How-To's) you will see that the big thing is Remote Access, Media Sharing, and Computer Backup. This would lead people to believe that any other use, is not what it was meant for, and when something goes wrong, you should have known better.

But, one only needs to look back at previous pages for WHS to see that Sharing was a central feature. Yes, full sharing, not just Media Sharing. Even the Overview of that page focuses on sharing first, and backup (protection) was third. The first overview item was Sharing, and that is simply what this problem is about, shared folders. Either for your own use as a networked server, or to share with other users.

Now, if you go to Eric Bott's blog, you will see the explanation that the largest factor is "a home server is under extreme load." Well, I'm sorry, but if the touted role, even at the beginning and not right now, was acting as a share folder to save your stuff to, then by damn it better do that. If the server gets loaded down, it should not pretend it got the file and tell you later that it didn't, it should just either not respond (and your software would have to let you know it couldn't do it) or it should give an error response (your software's problem now).

Honestly, this product was marketed as a home server for storing and sharing your files, with acting as a backup server making 3rd on the list of features. Now, they want to change that and say that it is for backup first, file sharing from special locations and under special conditions, and not really for file storage.