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."
"I'm not exactly what the point is in having a home server if you can't back up files on it."
Profit
They can't copy files to anywhere...
.... If there's a user friendly alternative to Windows server for Joe Enduser? I run a Debian box with Samba on a computer that does hardware RAID 1 for my file sharing needs (I also have an SCP turned on so I can shove files onto it from outside my network too). But that's not something that I can suggest to my friends and family. So what can I suggest to them that is as "user friendly" as Windows Server?
This is my opinion. To make sure you don't steal it, it's covered by the DMCA.
Microsoft Home Server Converts Files to a Secure Format for Your Security.
Microsoft will gladly sell you a one use un-convert license when you need to see the data.
The blurb says that it corrupts files on the backup when you try to edit them...
Isn't part of the point of a backup that you DON'T edit the backup media?
I can look at this two ways... MS didn't test this enough because it didn't occur to them someone might do something so ridiculous...
OR...
Not only did MS create the misfeature that is editing backups, but they screwed it up too...
Am I still feeling charitable from the holiays? Hmm...
So I read TFA thinking, so there's a glitch when windows has virus X on wednesdays only, and only in regions that have the chinese language pack, and only on systems with 64-bit version installed with a sound blaster driver installed.
But for the first time ever, slashdot's title isn't sensationalist. Microsoft simply states, yeah, for no apparent reason, files are getting corrupt using our operating system.
Jeebus F'n H Chroist! You had one job to do, and you screwed it up royally.
It's one thing when some obscure feature doesn't work correctly. It's another thing when a fundamental operation of your software hasn't worked for A YEAR since it came out.
IT'S AN OPERATING SYSTEM. Your job is to interface the hardware with the user and software.
*sigh* Bring on the "my linux-distro of choice doesn't do that, that makes me right all along" comments.
Belief? Hope? Preference?The Existential Vortex
Everyone knows you have to wait until at least version 3.1 to get anything useful out of Microsoft.
If someone says he and his monkey have nothing to hide, they almost certainly do.
According to the MS knowledge base entry:
;-)
"Make sure that you have a backup copy of any important program files before you store these files on a system that is running Windows Home Server."
In other words, use something else to backup the files first if you intend to backup them with Windows Home Server
A dvd-writer isn't feasible to backup nearly 300gb.
Gone!
Similar setup here, too.
In fact, running a Linux + Samba + SSH/SFTP/SCP + RAID ( + Optionally NFS ) seems the best solution available.
You can't suggest them to install and configure Debian all by themselves.
BUT
There are virtually hundred of "network enclosure" : Small empty external cases, with a 1Gbps ethernet and a small ARM chip running Linux+Samba+Apache, almost ready to use, you only need to buy disks and mount them in (several computer part shop even propose you to sell a pre-assembled such solution).
Linksys, D-Link and Netgear are a few of the constructor whose name jump to my mind right now, but there are virtually hundreds of them.
The best part is :
- These box have Linux pre-installed on their flash memory. So no difficult configuration is required for the average users. Maybe just help them to configure secure access and configure the router if they also want to have access to the files from outside home. The computer part shop often can do the hard-drive mounting and deliver a ready-to-use product.
- Almost any of those box runs Linux, so their firmware is modifiable and you can find several guides explaining how to run external software or even installing additional software into the firmware. MLDonkey is such an open source eD2K / Bittorrent / etc. client which is also precompiled for embed Linux.
Not only the enclosure is useful for average user, it may be useful for lazy power-users who don't want to assemble their own server or prefer silent and energy efficient servers.
- A lot of those boxes have USB2 "Host" connectors, so you can connect additional HDD to the server. But as it is Linux, a lot of different and interesting usage can be found be power users like plugins webcams, or use the box as a print server in addition to a file server.
So yes, you can't easily tell your friends to *install* Debian all by themselves, but you can get them to buy an enclosure with Linux pre-installed. (And if they upgrade their box to a newer one, you can recycle the old one into some fun project thanks to Linux' openness and available USB2 connectors).
"Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
Having come from a DECNet background, when I first encountered PC networking I was completely flummoxed by the situation.
MS-DOS and Windows users seem to take it for granted that a file that is across the network is accessed via different APIs, different user interfaces, and has generally different properties from files that are stored locally. In the MS-DOS days they were always mumbling about The Redirector. Why does a file need to be REdirected across the network? Why isn't it just directed, the way it would be directed to a disk volume or a floppy or what have you?
It isn't so long ago that most Windows programs couldn't even reference cross-network files in a straightforward way in a file open dialog. You first had to assign a "drive letter" and "map a network drive." (And, of course, all references to that file would break if you ever assigned the remote directory to a different drive letter).
And when they finally got around to fixing it in the OS, it only fixed it for new programs that were written to some new API. Existing programs, even things like Visual C++ utilities, continued to go through the mapping tapdance, because apparently the existing OS file dialog routines weren't updated to do things the new way.
The assumption that files across the network are totally differents sorts of thing from local files appeared to be so ingrained in the Windows culture that Windows people don't even understand why it is a criticism of Windows to mention this. They think it has to be that way, because, well, they're across the network. As if there were some physical property of 100-base-T cables that made them intrinsically different from SATA cables.
"How to Do Nothing," kids activities, back in print!
How do you know I'm not just twice as likely to defend my home from a friend or family member?
Computers allow humans to make mistakes at the fastest speeds known, with the possible exception of tequila and handguns
Which do well to explain the reason why, when a $1000 PC is faster than a $1,000,000 mainframe, that businesses still buy the mainframe. And then they stock the washrooms with single-ply toilet paper to cut costs.
Microsoft has made a lot of noise about being "Enterprise class" software, and having "Reliable" servers, but when things like this happen, it just goes to show that Microsoft won't ever be able to touch big iron:
The next time I hear anyone use the term "enterprise class" and Microsoft in the same sentence, I'm simply going to refer them to this bug. Totally unacceptable - even for a gaming OS.
The society for a thought-free internet welcomes you.
I mean really, after the first 6143569056076952107294386875907695350 times maybe it was worthy of a chuckle, but to keep on modding up this joke suggests some form of psychosis.
Wait, I'll put this in a way that you mods can understand:
1. go to slashdot
2. find a story
3. find a comment on that story
4. post a tired, old, lame-ass joke for the 9 billionth time
5. ???????
6. GET MODDED UP!
Ok, I followed the silly meme, where's my +5 Funny?
>>> Except in reality you are twice as likely to shoot a friend or family member than defend your home with your home defense gun.
False conclusion based on faulty data sampling.
A statistic does not get created unless there is a report. Cases where someone gets shot almost always generate a report. Cases where the homeowner's possession of a gun thwarts the crime and nobody gets shot are less likely to be reported.
Guns in the home are not high on the list of dangerous objects for average Americans. Check it out. The fact that drug dealers, thieves, and gang members often shoot their family members and 'friends' is used to make it sound like average people are not capable of defending themselves without endangering their families. It is a false impression intentionally created by lumping repeat criminal offenders in with the general population's statistics in these cases.
If 'the people' in Amendment 2 are 'the state' then Amendments 1, 2, 4, 9, and 10 benefit the state, not you.
It only takes 131+ years to copy 168 MB of pictures, what are you complaining about?
Apple Guy: Hey, PC. Whatcha doing?
PC Guy: Backing up my files.
AG: Wow. That's a lot of stuff - sure you can handle it all?
PC: Oh, sure. I'm using Vista Home Server. It allows me to back up my files by placing them securely in here.
AG: Whoa! What's the noise!?
PC: It's my backup appliance!
AG: Dude! That's a shredder!
PC: What!? Can't hear you!
AG:
Ok, 168 MB is 168*1024*1024 = 176,160,768 bytes.
A Commodore 64's floppy disk, the 1541 runs at 300 baud. So that's 176160768/300 = 587203 seconds for an equivalent copy. That's 9786 minutes, or 163.1 hours. That's 6.796 days.
The same copy will take Vista 131 years. That's 47815 days.
That means that a Commodore 64 w. 1541 drive is roughly 47815/6.796 = 7036 times faster than Windows Vista.
Now, for a human number. An average typist gets about 50-70 wpm according to wiki. So we'll call the average 60wpm. Seems reasonable. That's 60*5 = 300 characters per minute. Since a C64 moves data at 300 characters per second, we can say that a human typist is 60 times slower than the Commodore 64. That means that a human typist is 7036/60 = 117 times faster than a Vista file copy.
Impressive!
Weaselmancer
rediculous.
I am pro gun ownership. I think this whole, "hold at gun point" thing is stupid. I'm sorry, I've always been taught that you only draw your weapon to do one thing, fire it.
I have a few hand guns. Most are locked up safely. I have no kids so I keep on in a desk next to my bed, ready to be loaded. Just slide in the clip, and I'm good to go. We have had a few breakins lately in my area. If you break in, I will not be holding you for the police. I am in my right to kill, and I will kill. To hold at gunpoint is to risk that you might have a gun, or a friend I did not notice. It is stupid and very unsafe. I have a wife to protect, and property to protect. I really think anyone who holds at gunpoint had no intent of using the weapon in the first place. This is bad gun ownership.
You should only draw your weapon when you have identified a target and intend to fire on it. Hesitation might get you killed. The only exception might be in the case of military and police.
Your question is based on a flawed predicate.
The purpose of WHS is not ONLY to be file server. That's one purpose, and as long as you don't edit the file on the server, you're ok.
Another purpose is to create automated remote backup of all computers on the network, basically in such a way that you can create a new image via a restore CD, but also in a way that doesn't duplicate files between images. You can also access individual files in the backup. It's like a hybrid image/file backup with duplicate file consolidation. It's pretty efficient.
Another purpose is a remote access gateway to allow you to log in via terminal services to any computer in your network.
Another purpose is to provide a web based remote access to your files.
WHS is a very useful product, and this is an unfortunate bug, but it doesn't mitigate its entire existence.
If you need web hosting, you could do worse than here
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:
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.
Cause you can't get a tan from an amber monitor. If you do, there is something horribly wrong.