<?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/"
		>
<channel>
	<title>Comments on: The importance of backing up!</title>
	<atom:link href="http://www.communityspark.com/power-outage/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.communityspark.com/power-outage/</link>
	<description>Community Building</description>
	<lastBuildDate>Fri, 30 Jul 2010 08:46:18 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: What are your contingency plans? &#187; Online Community Building</title>
		<link>http://www.communityspark.com/power-outage/comment-page-1/#comment-2057</link>
		<dc:creator>What are your contingency plans? &#187; Online Community Building</dc:creator>
		<pubDate>Thu, 07 Jun 2007 17:00:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.communityspark.com/power-outage/#comment-2057</guid>
		<description>[...] few months ago, I wrote about the importance of backing up your site so that should your hosting fail, you have a copy of your site to restore. This article [...]</description>
		<content:encoded><![CDATA[<p>[...] few months ago, I wrote about the importance of backing up your site so that should your hosting fail, you have a copy of your site to restore. This article [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Always keep your software &#8216;kind of&#8217; updated &#187; Community Building Blog</title>
		<link>http://www.communityspark.com/power-outage/comment-page-1/#comment-1176</link>
		<dc:creator>Always keep your software &#8216;kind of&#8217; updated &#187; Community Building Blog</dc:creator>
		<pubDate>Sat, 19 May 2007 11:42:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.communityspark.com/power-outage/#comment-1176</guid>
		<description>[...] I think we lost around 100,000 posts and 1,000 members overnight. Of course, I had no backups either at that time. Don&#8217;t repeat my mistake - keep on top of security upgrades and always keep backups. [...]</description>
		<content:encoded><![CDATA[<p>[...] I think we lost around 100,000 posts and 1,000 members overnight. Of course, I had no backups either at that time. Don&#8217;t repeat my mistake &#8211; keep on top of security upgrades and always keep backups. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://www.communityspark.com/power-outage/comment-page-1/#comment-8</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Tue, 13 Mar 2007 08:28:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.communityspark.com/power-outage/#comment-8</guid>
		<description>Definitely good advice here. As the weeks, months, and years roll by, it can be all too easy to be lured into a false sense of security. Time passes by without incident; and the need for timely backups becomes apparently less urgent. Daily backups become weekly backups, which over time become monthly backups, and so on. Though you should be making backups more frequently as your community grows, that&#039;s not always how it happens in reality. Eventually you may even stop making them entirely. All is well and nothing ever goes wrong anyways, right?

This blog entry hits close to home for me. Power outages and server crashes are not the only cases where a recent backup can be a lifesaver. Sometimes complete and utter negligence on the part of your hosting provider gives need for that backup you made last night... You did make a backup last night, right?

This is what happened to one of my partner&#039;s websites when the host had decided to migrate over to a brand spanking new server... Without making a backup of all of the websites they host. Oh, sure, they had a backup of my partner&#039;s website. That backup was over 6 months old.

The real loss was not the flatfiles or scripts, which we both had offline backups of ourselves. The real tragedy here was the loss of the database. 6 months of forum posts and member registrations. Our own backup was a few months old itself. It was a harsh lesson to be learned. And the lesson? Always make frequent backups of your databases yourself; never rely on your webhost to do it for you!</description>
		<content:encoded><![CDATA[<p>Definitely good advice here. As the weeks, months, and years roll by, it can be all too easy to be lured into a false sense of security. Time passes by without incident; and the need for timely backups becomes apparently less urgent. Daily backups become weekly backups, which over time become monthly backups, and so on. Though you should be making backups more frequently as your community grows, that&#8217;s not always how it happens in reality. Eventually you may even stop making them entirely. All is well and nothing ever goes wrong anyways, right?</p>
<p>This blog entry hits close to home for me. Power outages and server crashes are not the only cases where a recent backup can be a lifesaver. Sometimes complete and utter negligence on the part of your hosting provider gives need for that backup you made last night&#8230; You did make a backup last night, right?</p>
<p>This is what happened to one of my partner&#8217;s websites when the host had decided to migrate over to a brand spanking new server&#8230; Without making a backup of all of the websites they host. Oh, sure, they had a backup of my partner&#8217;s website. That backup was over 6 months old.</p>
<p>The real loss was not the flatfiles or scripts, which we both had offline backups of ourselves. The real tragedy here was the loss of the database. 6 months of forum posts and member registrations. Our own backup was a few months old itself. It was a harsh lesson to be learned. And the lesson? Always make frequent backups of your databases yourself; never rely on your webhost to do it for you!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
