<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Data Corruption Issue Q&amp;A</title>
	<atom:link href="http://mswhs.com/2008/03/10/data-corruption-issue-qa/feed/" rel="self" type="application/rss+xml" />
	<link>http://mswhs.com/2008/03/10/data-corruption-issue-qa/</link>
	<description>A server for the people !!!</description>
	<lastBuildDate>Sat, 21 Nov 2009 16:10:29 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Gregg Keizer</title>
		<link>http://mswhs.com/2008/03/10/data-corruption-issue-qa/#comment-9383</link>
		<dc:creator>Gregg Keizer</dc:creator>
		<pubDate>Sun, 18 May 2008 19:15:13 +0000</pubDate>
		<guid isPermaLink="false">http://mswhs.wordpress.com/2008/03/10/data-corruption-issue-qa/#comment-9383</guid>
		<description>Why doesn&#039;t Microsoft provide some news on the progress being made for their proven data corruption design defect in WHS regarding Microsoft KB 946676?

The only thing being said is how Joel Sider, a senior product manager for WHS, stated that &quot;The server backup functionality won&#039;t include the PC backup database -- a separate data store on Home Server that keeps all the data from the PCs that home server is backing up every night&quot; in WHS PP1 to be released some time ahead (June 2008?).</description>
		<content:encoded><![CDATA[<p>Why doesn&#8217;t Microsoft provide some news on the progress being made for their proven data corruption design defect in WHS regarding Microsoft KB 946676?</p>
<p>The only thing being said is how Joel Sider, a senior product manager for WHS, stated that &#8220;The server backup functionality won&#8217;t include the PC backup database &#8212; a separate data store on Home Server that keeps all the data from the PCs that home server is backing up every night&#8221; in WHS PP1 to be released some time ahead (June 2008?).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Grey Lancaster</title>
		<link>http://mswhs.com/2008/03/10/data-corruption-issue-qa/#comment-9379</link>
		<dc:creator>Grey Lancaster</dc:creator>
		<pubDate>Sun, 18 May 2008 18:43:43 +0000</pubDate>
		<guid isPermaLink="false">http://mswhs.wordpress.com/2008/03/10/data-corruption-issue-qa/#comment-9379</guid>
		<description>Windows XP SP3 Update breaks Windows Home Server Remote Access! -- Chris Keroack, Windows XP SP3 release manager

www.wegotserved.co.uk/2008/05/17/windows-xp-sp3-update-breaks-windows-home-server-remote-access/

HP begs AMD PC owners to put XP SP3 on ICE -- Allen Buckner (Senior Product Manager for the Home Server business within HP) 

www.channelregister.co.uk/2008/05/16/hp_xp_sp3_amd/ 

@Terrence, See Microsoft. KB articles 946676, 939426, 939217, 939427, 939428, 939429 and 939218 all deal with issues relating to setup and backup. Don&#039;t forget 939424, 939425, 939758, 939759 too.

HP Warning about using WHS

&quot;You should not directly open and/or edit files that are stored on the MediaSmart Server while doing any other activity such as large data transfers or media streaming. If you are doing a large data transfer or streaming and need to edit a file on the server, you should first copy the file over to a PC and then open it for editing.

There are a few key applications that Microsoft has identified that can cause this issue when files are opened and edited directly from the server. However to be safe, HP recommends that you not open/edit files directly from the server until this fix is delivered.&quot;</description>
		<content:encoded><![CDATA[<p>Windows XP SP3 Update breaks Windows Home Server Remote Access! &#8212; Chris Keroack, Windows XP SP3 release manager</p>
<p><a href="http://www.wegotserved.co.uk/2008/05/17/windows-xp-sp3-update-breaks-windows-home-server-remote-access/" rel="nofollow">http://www.wegotserved.co.uk/2008/05/17/windows-xp-sp3-update-breaks-windows-home-server-remote-access/</a></p>
<p>HP begs AMD PC owners to put XP SP3 on ICE &#8212; Allen Buckner (Senior Product Manager for the Home Server business within HP) </p>
<p><a href="http://www.channelregister.co.uk/2008/05/16/hp_xp_sp3_amd/" rel="nofollow">http://www.channelregister.co.uk/2008/05/16/hp_xp_sp3_amd/</a> </p>
<p>@Terrence, See Microsoft. KB articles 946676, 939426, 939217, 939427, 939428, 939429 and 939218 all deal with issues relating to setup and backup. Don&#8217;t forget 939424, 939425, 939758, 939759 too.</p>
<p>HP Warning about using WHS</p>
<p>&#8220;You should not directly open and/or edit files that are stored on the MediaSmart Server while doing any other activity such as large data transfers or media streaming. If you are doing a large data transfer or streaming and need to edit a file on the server, you should first copy the file over to a PC and then open it for editing.</p>
<p>There are a few key applications that Microsoft has identified that can cause this issue when files are opened and edited directly from the server. However to be safe, HP recommends that you not open/edit files directly from the server until this fix is delivered.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Terrence</title>
		<link>http://mswhs.com/2008/03/10/data-corruption-issue-qa/#comment-7990</link>
		<dc:creator>Terrence</dc:creator>
		<pubDate>Sat, 22 Mar 2008 00:22:26 +0000</pubDate>
		<guid isPermaLink="false">http://mswhs.wordpress.com/2008/03/10/data-corruption-issue-qa/#comment-7990</guid>
		<description>I want, no NEED, to feel confident and secure about our data.  backups. My data is no more important than anyone else&#039;s, but my wife&#039;s pro photography catalog is, in my mind, crucial.
I&#039;m cautiously trying to rebuild my confidence, but a couple of my more sardonic, though on-point, posts were deleted from the WHS forum site because I used the &quot;released before ready&quot; criticism MS is so sensitive about.  I wonder why.

I did not go through the year of Beta testing like a lot of you have.  (I think I&#039;ve paid my dues in years past without having volunteered for it.)  I think WHS &lt;strong&gt;is a brilliant &lt;/strong&gt; concept and thought that MS had really &quot;gotten it right&quot; with this one. I bought it once I believed in it.  

I could even wait &#039;til June if I could get a straight answer from the WHS team about whether my data is truly made safe from the bug by following the recommended file management and usage protocols.  It&#039;s a simple question.  

I&#039;m OK with the functionality as is--as long is it&#039;s reliable.  I understand people needing what PowerPack1 promises, particularly 64-bit connector.  I sympathize, but personally, just need the bug fixed and sooner is better.

I&#039;m also confused about so many reports of backup corruption and restore failures while the &quot;file corruption&quot; KB only recommends not using certain applications and not manipulating files whilst on the server.  You know, I don&#039;t even need a straight answer personalized just for me.  Someone please just write down the KB# or forum post that actually gives me the straight answer and I will shut up and make my decision.

I know the WHS team is trying hard.  I know I had praised them enthusiastically after I&#039;d initially evaluated WHS.   I&#039;ve even had to retract recommendations I&#039;d made to friends which is a bit embarrassing.  Thankfully, none had acted upon it yet.  I&#039;m an unlikely defender of the WHS team given my past experiences with MS, but I am trying. I&#039;m still hoping to be impressed with their project, should it live up to the promise.

In the meantime, has anyone come up with a simple and reliable way to test/verify files on the server shares?</description>
		<content:encoded><![CDATA[<p>I want, no NEED, to feel confident and secure about our data.  backups. My data is no more important than anyone else&#8217;s, but my wife&#8217;s pro photography catalog is, in my mind, crucial.<br />
I&#8217;m cautiously trying to rebuild my confidence, but a couple of my more sardonic, though on-point, posts were deleted from the WHS forum site because I used the &#8220;released before ready&#8221; criticism MS is so sensitive about.  I wonder why.</p>
<p>I did not go through the year of Beta testing like a lot of you have.  (I think I&#8217;ve paid my dues in years past without having volunteered for it.)  I think WHS <strong>is a brilliant </strong> concept and thought that MS had really &#8220;gotten it right&#8221; with this one. I bought it once I believed in it.  </p>
<p>I could even wait &#8217;til June if I could get a straight answer from the WHS team about whether my data is truly made safe from the bug by following the recommended file management and usage protocols.  It&#8217;s a simple question.  </p>
<p>I&#8217;m OK with the functionality as is&#8211;as long is it&#8217;s reliable.  I understand people needing what PowerPack1 promises, particularly 64-bit connector.  I sympathize, but personally, just need the bug fixed and sooner is better.</p>
<p>I&#8217;m also confused about so many reports of backup corruption and restore failures while the &#8220;file corruption&#8221; KB only recommends not using certain applications and not manipulating files whilst on the server.  You know, I don&#8217;t even need a straight answer personalized just for me.  Someone please just write down the KB# or forum post that actually gives me the straight answer and I will shut up and make my decision.</p>
<p>I know the WHS team is trying hard.  I know I had praised them enthusiastically after I&#8217;d initially evaluated WHS.   I&#8217;ve even had to retract recommendations I&#8217;d made to friends which is a bit embarrassing.  Thankfully, none had acted upon it yet.  I&#8217;m an unlikely defender of the WHS team given my past experiences with MS, but I am trying. I&#8217;m still hoping to be impressed with their project, should it live up to the promise.</p>
<p>In the meantime, has anyone come up with a simple and reliable way to test/verify files on the server shares?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: A Fix</title>
		<link>http://mswhs.com/2008/03/10/data-corruption-issue-qa/#comment-7861</link>
		<dc:creator>A Fix</dc:creator>
		<pubDate>Tue, 11 Mar 2008 19:09:02 +0000</pubDate>
		<guid isPermaLink="false">http://mswhs.wordpress.com/2008/03/10/data-corruption-issue-qa/#comment-7861</guid>
		<description>http://www.linux-watch.com/news/NS9015653445.html</description>
		<content:encoded><![CDATA[<p><a href="http://www.linux-watch.com/news/NS9015653445.html" rel="nofollow">http://www.linux-watch.com/news/NS9015653445.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Colin P. is Right</title>
		<link>http://mswhs.com/2008/03/10/data-corruption-issue-qa/#comment-7859</link>
		<dc:creator>Colin P. is Right</dc:creator>
		<pubDate>Tue, 11 Mar 2008 18:50:36 +0000</pubDate>
		<guid isPermaLink="false">http://mswhs.wordpress.com/2008/03/10/data-corruption-issue-qa/#comment-7859</guid>
		<description>Colin P. said it best:

When it comes to &#039;features&#039; versus rock-solid, assured, bug-free data storage, I&#039;d push &#039;features&#039; onto the back burner.

The problems at present are -

(a) I don&#039;t know whether my so-far still intact data will suddenly get corrupted.

(There have been many reports of corruption appearing out-of-the-blue.)

(b) There are no guaranteed checks that I can run on my system to clarify whether my data is even vulnerable.

I don&#039;t know if it is vulnerable, and I don&#039;t know that it isn&#039;t vulnerable. That&#039;s in spite of the KB updates, and in spite of my fully understanding the &quot;work-arounds&quot;.

(c) In order to reduce my (possible) vulnerability, I have turned OFF folder sharing / DE on all shares.

(d) As a way of coping with all the above, and to keep my WHS-hopes alive, I&#039;m spending some time each day to progressively verify a portion of my thousands of files.

In the meantime I&#039;m running a handicapped (no duplication) backup server (WHS) with fingers and toes crossed, and unable therefore to reclaim the GB of HDD storage I hoped to release by trusting some of it to WHS.

So ... you bet I want the fix first, earliest, soonest, ASAP, without delay, and I don&#039;t care a monkey&#039;s about any further features or bells or whistles or other boast-worthy extras from the WHS Development Team.

I vote that you get the fundamentals sorted first please!!&quot; - wrote Colin P.</description>
		<content:encoded><![CDATA[<p>Colin P. said it best:</p>
<p>When it comes to &#8216;features&#8217; versus rock-solid, assured, bug-free data storage, I&#8217;d push &#8216;features&#8217; onto the back burner.</p>
<p>The problems at present are -</p>
<p>(a) I don&#8217;t know whether my so-far still intact data will suddenly get corrupted.</p>
<p>(There have been many reports of corruption appearing out-of-the-blue.)</p>
<p>(b) There are no guaranteed checks that I can run on my system to clarify whether my data is even vulnerable.</p>
<p>I don&#8217;t know if it is vulnerable, and I don&#8217;t know that it isn&#8217;t vulnerable. That&#8217;s in spite of the KB updates, and in spite of my fully understanding the &#8220;work-arounds&#8221;.</p>
<p>(c) In order to reduce my (possible) vulnerability, I have turned OFF folder sharing / DE on all shares.</p>
<p>(d) As a way of coping with all the above, and to keep my WHS-hopes alive, I&#8217;m spending some time each day to progressively verify a portion of my thousands of files.</p>
<p>In the meantime I&#8217;m running a handicapped (no duplication) backup server (WHS) with fingers and toes crossed, and unable therefore to reclaim the GB of HDD storage I hoped to release by trusting some of it to WHS.</p>
<p>So &#8230; you bet I want the fix first, earliest, soonest, ASAP, without delay, and I don&#8217;t care a monkey&#8217;s about any further features or bells or whistles or other boast-worthy extras from the WHS Development Team.</p>
<p>I vote that you get the fundamentals sorted first please!!&#8221; &#8211; wrote Colin P.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Donald</title>
		<link>http://mswhs.com/2008/03/10/data-corruption-issue-qa/#comment-7820</link>
		<dc:creator>Donald</dc:creator>
		<pubDate>Mon, 10 Mar 2008 22:45:34 +0000</pubDate>
		<guid isPermaLink="false">http://mswhs.wordpress.com/2008/03/10/data-corruption-issue-qa/#comment-7820</guid>
		<description>I&#039;ve got to be honest... This makes me pretty upset.  I am now the proud owner of a faulty server that could possibly corrupt my data!  The workarounds are fantastic to boot.  

I really liked the idea of WHS and backups were a snap.  However, data integrity is paramount and this is just completely unacceptable.   

Looks like I&#039;ll be migrating my data to a more reliable server configuration.

On the bright side, at least they aren&#039;t manufacturing planes!  &lt;1% !?!? nope, still don&#039;t like those odds.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve got to be honest&#8230; This makes me pretty upset.  I am now the proud owner of a faulty server that could possibly corrupt my data!  The workarounds are fantastic to boot.  </p>
<p>I really liked the idea of WHS and backups were a snap.  However, data integrity is paramount and this is just completely unacceptable.   </p>
<p>Looks like I&#8217;ll be migrating my data to a more reliable server configuration.</p>
<p>On the bright side, at least they aren&#8217;t manufacturing planes!  &lt;1% !?!? nope, still don&#8217;t like those odds.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken</title>
		<link>http://mswhs.com/2008/03/10/data-corruption-issue-qa/#comment-7814</link>
		<dc:creator>Ken</dc:creator>
		<pubDate>Mon, 10 Mar 2008 21:06:18 +0000</pubDate>
		<guid isPermaLink="false">http://mswhs.wordpress.com/2008/03/10/data-corruption-issue-qa/#comment-7814</guid>
		<description>This is a good development, not a bad one.  The issue is reproduceable, they have a fix that they are testing, and they FINALLY offered an update.  I think promising a date sooner than they could conservatively test the fix would have been foolish.</description>
		<content:encoded><![CDATA[<p>This is a good development, not a bad one.  The issue is reproduceable, they have a fix that they are testing, and they FINALLY offered an update.  I think promising a date sooner than they could conservatively test the fix would have been foolish.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Skandy</title>
		<link>http://mswhs.com/2008/03/10/data-corruption-issue-qa/#comment-7805</link>
		<dc:creator>Skandy</dc:creator>
		<pubDate>Mon, 10 Mar 2008 18:29:12 +0000</pubDate>
		<guid isPermaLink="false">http://mswhs.wordpress.com/2008/03/10/data-corruption-issue-qa/#comment-7805</guid>
		<description>I wrote thos message on microsoft forum.. it&#039;s been deleted with another user&#039;s post complaining about the KB update. What a shame!

I&#039;ve just bought an OEM copy of french WHS (after spending a month testing the 120 days trial) hoping that this Monday KB update will offer us a fix.. June 2008?! Come on! you&#039;re kidding me!

I&#039;m really upset, i&#039;ll have to wait three months (at least) using a single HDD without duplicating my data. Great! I have to deal with 500Go of very precious (i mean emotional value) non duplicated family media!

WHS = Bakup your backups.. maybe using a &quot;real&quot; server solution (how about linux?)

I&#039;m really thinking about returning my WHS dvd without even opening it and contact a consumer rights defense association.</description>
		<content:encoded><![CDATA[<p>I wrote thos message on microsoft forum.. it&#8217;s been deleted with another user&#8217;s post complaining about the KB update. What a shame!</p>
<p>I&#8217;ve just bought an OEM copy of french WHS (after spending a month testing the 120 days trial) hoping that this Monday KB update will offer us a fix.. June 2008?! Come on! you&#8217;re kidding me!</p>
<p>I&#8217;m really upset, i&#8217;ll have to wait three months (at least) using a single HDD without duplicating my data. Great! I have to deal with 500Go of very precious (i mean emotional value) non duplicated family media!</p>
<p>WHS = Bakup your backups.. maybe using a &#8220;real&#8221; server solution (how about linux?)</p>
<p>I&#8217;m really thinking about returning my WHS dvd without even opening it and contact a consumer rights defense association.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
