<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
     xmlns:admin="http://webns.net/mvcb/"
     xmlns:content="http://purl.org/rss/1.0/modules/content/"
     xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
	<channel> 

	<title>Comments on: Looking for a bulletproof web host with built-in colocation and failover.</title>
	<link>http://ask.metafilter.com/106466/Looking-for-a-bulletproof-web-host-with-builtin-colocation-and-failover/</link>
	<description>Comments on Ask MetaFilter post Looking for a bulletproof web host with built-in colocation and failover.</description>
	<pubDate>Mon, 10 Nov 2008 15:51:48 -0800</pubDate>
	<lastBuildDate>Mon, 10 Nov 2008 15:51:48 -0800</lastBuildDate>
	<language>en-us</language>
	<docs>http://blogs.law.harvard.edu/tech/rss</docs>
	<ttl>60</ttl>

	<item>
		<title>Question: Looking for a bulletproof web host with built-in colocation and failover.</title>
		<link>http://ask.metafilter.com/106466/Looking-for-a-bulletproof-web-host-with-builtin-colocation-and-failover</link>	
		<description>Looking at setting up a simple web site (no CGI) but needs to be up 24/7 and reasonably disaster proof (earthquake, hurricane, regional fires, etc.).  Hosting company needs to be multisite with automagic failover assuming one site goes down.   &lt;br /&gt;&lt;br /&gt; Updates from primary to failover site can be as slow as hourly, they do not need to be in realtime.  Minimal traffic (less than 2Gb/month).  Don&apos;t care if it&apos;s straight hosting or a whole VPS, proc and memory usage should be minimal.  Dedicated colo hardware would be overkill.&lt;br&gt;
&lt;br&gt;
I realize there are various hand-rolled ways to achieve the same thing (rsync, cron, various DNS tricks spring to mind) but would prefer that the vendor worry about it.  Most of the vendors I&apos;ve found have a single bulletproof site but have no site failover.</description>
		<guid isPermaLink="false">post:ask.metafilter.com,2008:site.106466</guid>
		<pubDate>Mon, 10 Nov 2008 15:33:55 -0800</pubDate>
		<dc:creator>benzenedream</dc:creator>
		
			<category>webhost</category>
		
			<category>hosting</category>
		
			<category>disaster</category>
		
			<category>emergency</category>
		
			<category>preparedness</category>
		
			<category>colocation</category>
		
			<category>bgp</category>
		
	</item> <item>
		<title>By: odinsdream</title>
		<link>http://ask.metafilter.com/106466/Looking-for-a-bulletproof-web-host-with-builtin-colocation-and-failover#1536133</link>	
		<description>You mention that the failover doesn&apos;t have to be realtime. Does it need to be automatic? If not, this is easily achieved by simply hosting multiple copies of your site in various geographic locations, then redirecting DNS at the time of a failure. This is the very purpose of DNS, it&apos;s not esoteric or tricky at all.&lt;br&gt;
&lt;br&gt;
If it needs to be automatic, you can easily script DNS modifications with a DNS host like &lt;a href=&quot;http://www.dyndns.com/&quot;&gt;DynDNS&lt;/a&gt;.</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2008:site.106466-1536133</guid>
		<pubDate>Mon, 10 Nov 2008 15:51:48 -0800</pubDate>
		<dc:creator>odinsdream</dc:creator>
	</item><item>
		<title>By: bonaldi</title>
		<link>http://ask.metafilter.com/106466/Looking-for-a-bulletproof-web-host-with-builtin-colocation-and-failover#1536315</link>	
		<description>&lt;a href=&quot;http://www.akamai.com/&quot;&gt;Akamai&lt;/a&gt; will do this for you and ask &quot;What&apos;s next?&quot;.&lt;br&gt;
&lt;br&gt;
Then they&apos;ll send a bill. But if the content must stay up, see them.</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2008:site.106466-1536315</guid>
		<pubDate>Mon, 10 Nov 2008 18:40:43 -0800</pubDate>
		<dc:creator>bonaldi</dc:creator>
	</item><item>
		<title>By: Brian Puccio</title>
		<link>http://ask.metafilter.com/106466/Looking-for-a-bulletproof-web-host-with-builtin-colocation-and-failover#1536660</link>	
		<description>Do you really mean &lt;a href=&quot;http://en.wikipedia.org/wiki/Bulletproof_hosting&quot; title=&quot;Bulletproof hosting - Wikipedia, the free encyclopedia&quot;&gt;bulletproof hosting&lt;/a&gt;?</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2008:site.106466-1536660</guid>
		<pubDate>Tue, 11 Nov 2008 02:02:20 -0800</pubDate>
		<dc:creator>Brian Puccio</dc:creator>
	</item><item>
		<title>By: benzenedream</title>
		<link>http://ask.metafilter.com/106466/Looking-for-a-bulletproof-web-host-with-builtin-colocation-and-failover#1537053</link>	
		<description>BP:  Errr, no need to host exotic content in Russia.  &lt;br&gt;
&lt;br&gt;
Odinsdream: We already use Neustar for DNS services, they have a service called SiteBacker which does monitoring and failover.  I&apos;ll check them out as well as DynDNS.  A nightly scp cron job could do the rest.  Since this is a DR site I was hoping to keep the number of vendors and contact numbers down.&lt;br&gt;
&lt;br&gt;
Bonaldi:  Is the price for Akamai an order of magnitude higher?</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2008:site.106466-1537053</guid>
		<pubDate>Tue, 11 Nov 2008 09:59:13 -0800</pubDate>
		<dc:creator>benzenedream</dc:creator>
	</item><item>
		<title>By: Brian Puccio</title>
		<link>http://ask.metafilter.com/106466/Looking-for-a-bulletproof-web-host-with-builtin-colocation-and-failover#1537477</link>	
		<description>OK, then I&apos;d second the DNS idea. Set your TTL low (and hope ISPs; caching servers don&apos;t ignore it).</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2008:site.106466-1537477</guid>
		<pubDate>Tue, 11 Nov 2008 15:43:34 -0800</pubDate>
		<dc:creator>Brian Puccio</dc:creator>
	</item><item>
		<title>By: benzenedream</title>
		<link>http://ask.metafilter.com/106466/Looking-for-a-bulletproof-web-host-with-builtin-colocation-and-failover#1544220</link>	
		<description>So, I checked out a few other &quot;grid computing&quot; options that have somewhat distributed infrastructure for hosting.&lt;br&gt;
&lt;br&gt;
Amazon - overkill for simple html hosting, but does offer possibility of multisite hosting as an option for EC3.&lt;br&gt;
GoGrid - single building hosting in SF&lt;br&gt;
Mosso - cool company with multiple sites in Texas, but no failover across sites (failover within sites is built in)&lt;br&gt;
&lt;br&gt;
Akamai has multisite failover built in at a minimum of $1500/month, which is over our budget.&lt;br&gt;
&lt;br&gt;
I will likely go the failover DNS TTL route as Brian suggested and get two medium price hosts with a nightly mirroring rsync script.</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2008:site.106466-1544220</guid>
		<pubDate>Mon, 17 Nov 2008 15:35:57 -0800</pubDate>
		<dc:creator>benzenedream</dc:creator>
	</item><item>
		<title>By: benzenedream</title>
		<link>http://ask.metafilter.com/106466/Looking-for-a-bulletproof-web-host-with-builtin-colocation-and-failover#1569142</link>	
		<description>&lt;a href=&quot;http://www.dnsmadeeasy.com/s0306/price/dns.html&quot;&gt;DNSmadeEasy&lt;/a&gt; hosts DNS records with auto failover for reasonably cheap prices.  We will likely go with them as a first pass.</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2008:site.106466-1569142</guid>
		<pubDate>Thu, 11 Dec 2008 02:15:26 -0800</pubDate>
		<dc:creator>benzenedream</dc:creator>
	</item>
	</channel>
</rss>
