<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>The Inquisitr - Latest Comments in Netflix: Faulty Hardware Took Us Down</title><link>http://inquisitr.disqus.com/</link><description></description><language>en</language><lastBuildDate>Wed, 27 Aug 2008 00:01:08 -0000</lastBuildDate><item><title>Re: Netflix: Faulty Hardware Took Us Down</title><link>http://www.inquisitr.com/2635/netflix-faulty-hardware-took-us-down/#comment-1862490</link><description>Awful reporting.  Nowhere did they say that the system crashed.  What they said was that a database corruption issue was detected.  Therefore, the outage was intentional -- they had to shut down the system, migrate a known-good snapshot to new hardware, and replay the logs.  This takes a heck of a lot of time because you're basically provisioning your IT infrastructure from scratch.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tom</dc:creator><pubDate>Wed, 27 Aug 2008 00:01:08 -0000</pubDate></item><item><title>Re: Netflix: Faulty Hardware Took Us Down</title><link>http://www.inquisitr.com/2635/netflix-faulty-hardware-took-us-down/#comment-1829870</link><description>Interesting that they blame one piece of hardware, when it looks like all Netflix's distribution centers were out of commission for a time. Unless they took the others offline until they identified the problem, or they have multiple instances of that one piece of hardware. Still smells like a software issue...</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">davezatz</dc:creator><pubDate>Mon, 25 Aug 2008 15:43:30 -0000</pubDate></item></channel></rss>