<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>thinking sysadmin &#187; windows</title>
	<atom:link href="http://andyleonard.com/tag/windows/feed/" rel="self" type="application/rss+xml" />
	<link>http://andyleonard.com</link>
	<description>qstat -u aleonard -s z</description>
	<lastBuildDate>Fri, 30 Jul 2010 17:47:40 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Links 7/27/2008: S3 Outage Post-Mortem, Update 2 for VI 3 version 3.5</title>
		<link>http://andyleonard.com/2008/07/27/links-7272008-s3-outage-post-mortem-update-2-for-vi-3-version-35/</link>
		<comments>http://andyleonard.com/2008/07/27/links-7272008-s3-outage-post-mortem-update-2-for-vi-3-version-35/#comments</comments>
		<pubDate>Sun, 27 Jul 2008 15:26:01 +0000</pubDate>
		<dc:creator>Andy</dc:creator>
				<category><![CDATA[link dump]]></category>
		<category><![CDATA[amazon aws]]></category>
		<category><![CDATA[esx]]></category>
		<category><![CDATA[s3]]></category>
		<category><![CDATA[vss]]></category>
		<category><![CDATA[windows]]></category>

		<guid isPermaLink="false">http://andyleonard.com/?p=56</guid>
		<description><![CDATA[
Amazon S3 Availability Event: July 20, 2008 &#8211; Amazon&#8217;s post-mortem on the 7/20 S3 outage.  Excerpt: &#8220;We&#8217;ve now determined that message corruption was the cause of the server-to-server communication problems. More specifically, we found that there were a handful of messages on Sunday morning that had a single bit corrupted such that the message [...]]]></description>
			<content:encoded><![CDATA[<ul>
<li><a href="http://status.aws.amazon.com/s3-20080720.html">Amazon S3 Availability Event: July 20, 2008</a> &#8211; Amazon&#8217;s post-mortem on the 7/20 S3 outage.  Excerpt: &#8220;We&#8217;ve now determined that message corruption was the cause of the server-to-server communication problems. More specifically, we found that there were a handful of messages on Sunday morning that had a single bit corrupted such that the message was still intelligible, but the system state information was incorrect.&#8221;  (Seen first at <a href="http://arstechnica.com/news.ars/post/20080726-week-in-storage-cloud-storage-fumbles-tape-sets-records.html">Ars Technica</a>.)</li>
<li>VMware has released Update 2 for VMware Infrastructure 3 version 3.5 (I think that&#8217;s the Full Official Name That Only A Committee Could Love&#8230;).  <a href="http://blog.scottlowe.org/2008/07/26/vmware-releases-update-2/">Scott Lowe</a> has a good summary; release notes are <a href="http://www.vmware.com/support/vi3/doc/vi3_esx35u2_vc25u2_rel_notes.html">here</a>.  Most notable among the updates is the ability to use VSS to quiesce Windows VMs prior to snapshotting.</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://andyleonard.com/2008/07/27/links-7272008-s3-outage-post-mortem-update-2-for-vi-3-version-35/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>7/25/2008 Links: VMDK File Level Recovery</title>
		<link>http://andyleonard.com/2008/07/25/7252008-links-vmdk-file-level-recovery/</link>
		<comments>http://andyleonard.com/2008/07/25/7252008-links-vmdk-file-level-recovery/#comments</comments>
		<pubDate>Fri, 25 Jul 2008 18:50:43 +0000</pubDate>
		<dc:creator>Andy</dc:creator>
				<category><![CDATA[link dump]]></category>
		<category><![CDATA[backup]]></category>
		<category><![CDATA[nfs]]></category>
		<category><![CDATA[vmware]]></category>
		<category><![CDATA[windows]]></category>

		<guid isPermaLink="false">http://andyleonard.com/?p=53</guid>
		<description><![CDATA[
File Level Recovery from within a VMDK backup &#8211; Nick Triantos of NetApp covers file-level recovery from VMware (Windows) VMDK files again, in more depth than he has before.  Nick notes that it can be a &#8220;a point-and-click process.&#8221;

]]></description>
			<content:encoded><![CDATA[<ul>
<li><a href="http://blogs.netapp.com/storage_nuts_n_bolts/2008/07/file-level-reco.html">File Level Recovery from within a VMDK backup</a> &#8211; Nick Triantos of NetApp covers file-level recovery from VMware (Windows) VMDK files again, in more depth than he has before.  Nick notes that it can be a &#8220;a point-and-click process.&#8221;</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://andyleonard.com/2008/07/25/7252008-links-vmdk-file-level-recovery/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
