<?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: In Case of Security &#8211; Planning for Blogging Disasters</title>
	<atom:link href="http://www.problogger.net/archives/2006/01/03/in-case-of-security-planning-for-blogging-disasters/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.problogger.net/archives/2006/01/03/in-case-of-security-planning-for-blogging-disasters/</link>
	<description>Make Money Online</description>
	<lastBuildDate>Sun, 22 Nov 2009 12:19:19 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Stupidity branches out - Homeland Security or Homeland Stupidity</title>
		<link>http://www.problogger.net/archives/2006/01/03/in-case-of-security-planning-for-blogging-disasters/comment-page-1/#comment-205884</link>
		<dc:creator>Stupidity branches out - Homeland Security or Homeland Stupidity</dc:creator>
		<pubDate>Sat, 07 Jan 2006 04:47:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.problogger.net/?p=1981#comment-205884</guid>
		<description>[...] In the last week or so I&#8217;ve managed to guest blog two posts at two different blogs which you may be interested in reading (or may not care at all about.)The first, which was written before Christmas but only posted this week, deals with business continuity for professional bloggers. In other words, what happens when disaster strikes? I learned firsthand how important it is to prepare for disasters, both small and large, and shared some of what I know. It&#8217;s primarily through planning that I was able to survive losing my computer and continue writing this site (and my others), albeit at a much reduced capacity. If you intend to make a business of blogging, it&#8217;s a must-read, and must-act-upon. [...]</description>
		<content:encoded><![CDATA[<p>[...] In the last week or so I&#8217;ve managed to guest blog two posts at two different blogs which you may be interested in reading (or may not care at all about.)The first, which was written before Christmas but only posted this week, deals with business continuity for professional bloggers. In other words, what happens when disaster strikes? I learned firsthand how important it is to prepare for disasters, both small and large, and shared some of what I know. It&#8217;s primarily through planning that I was able to survive losing my computer and continue writing this site (and my others), albeit at a much reduced capacity. If you intend to make a business of blogging, it&#8217;s a must-read, and must-act-upon. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ANLAT</title>
		<link>http://www.problogger.net/archives/2006/01/03/in-case-of-security-planning-for-blogging-disasters/comment-page-1/#comment-205377</link>
		<dc:creator>ANLAT</dc:creator>
		<pubDate>Sat, 07 Jan 2006 00:09:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.problogger.net/?p=1981#comment-205377</guid>
		<description>Thanks for all.</description>
		<content:encoded><![CDATA[<p>Thanks for all.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: YWAM Information Technology</title>
		<link>http://www.problogger.net/archives/2006/01/03/in-case-of-security-planning-for-blogging-disasters/comment-page-1/#comment-205227</link>
		<dc:creator>YWAM Information Technology</dc:creator>
		<pubDate>Fri, 06 Jan 2006 20:42:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.problogger.net/?p=1981#comment-205227</guid>
		<description>&lt;strong&gt;Now that we have the ability, let&#039;s blog well...&lt;/strong&gt;

Blogs in YWAM are starting to pop up little by little. Jeff Neely just launched his over at neelys.org and I spoke to someone at the coffee machine who is interested in starting one up as well.
</description>
		<content:encoded><![CDATA[<p><strong>Now that we have the ability, let&#8217;s blog well&#8230;</strong></p>
<p>Blogs in YWAM are starting to pop up little by little. Jeff Neely just launched his over at neelys.org and I spoke to someone at the coffee machine who is interested in starting one up as well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave</title>
		<link>http://www.problogger.net/archives/2006/01/03/in-case-of-security-planning-for-blogging-disasters/comment-page-1/#comment-203122</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Wed, 04 Jan 2006 18:37:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.problogger.net/?p=1981#comment-203122</guid>
		<description>&lt;i&gt;Great suggestions on testing your backups, but what would be an easy way to test them?&lt;/i&gt;

Two choices that I use, there are probably more. First, I have a dedicated server with my host so I can log in and do whatever I want. I create a new folder (or sub-domain or whatever technique you like) and copy up the source code. Then I create a new database (since I don&#039;t want to overwrite my production one) and alter the wordpress config file to point to this copy of the database. Then I restore the database backup. As long as paths are &quot;relative&quot; (meaning not hard-coded to your full domain) then everything should work.

I also maintain a linux server in my home office, and I can restore my source code / database backups to that server and test without affecting my &quot;production&quot; server.</description>
		<content:encoded><![CDATA[<p><i>Great suggestions on testing your backups, but what would be an easy way to test them?</i></p>
<p>Two choices that I use, there are probably more. First, I have a dedicated server with my host so I can log in and do whatever I want. I create a new folder (or sub-domain or whatever technique you like) and copy up the source code. Then I create a new database (since I don&#8217;t want to overwrite my production one) and alter the wordpress config file to point to this copy of the database. Then I restore the database backup. As long as paths are &#8220;relative&#8221; (meaning not hard-coded to your full domain) then everything should work.</p>
<p>I also maintain a linux server in my home office, and I can restore my source code / database backups to that server and test without affecting my &#8220;production&#8221; server.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Hampton</title>
		<link>http://www.problogger.net/archives/2006/01/03/in-case-of-security-planning-for-blogging-disasters/comment-page-1/#comment-202733</link>
		<dc:creator>Michael Hampton</dc:creator>
		<pubDate>Wed, 04 Jan 2006 03:35:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.problogger.net/?p=1981#comment-202733</guid>
		<description>And in what I could only call a cruel twist of fate, the unthinkable just did happen to me a few hours ago. &lt;a href=&quot;http://www.ioerror.us/2006/01/03/its-dead-jim/&quot; rel=&quot;nofollow&quot;&gt;My laptop bit the dust.&lt;/a&gt; I&#039;m now on my contingency plans where I&#039;m using a web-based feedreader (again), webmail, and essentially working from others&#039; computers and public terminals.</description>
		<content:encoded><![CDATA[<p>And in what I could only call a cruel twist of fate, the unthinkable just did happen to me a few hours ago. <a href="http://www.ioerror.us/2006/01/03/its-dead-jim/" rel="nofollow">My laptop bit the dust.</a> I&#8217;m now on my contingency plans where I&#8217;m using a web-based feedreader (again), webmail, and essentially working from others&#8217; computers and public terminals.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: miscblogger</title>
		<link>http://www.problogger.net/archives/2006/01/03/in-case-of-security-planning-for-blogging-disasters/comment-page-1/#comment-202314</link>
		<dc:creator>miscblogger</dc:creator>
		<pubDate>Tue, 03 Jan 2006 23:13:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.problogger.net/?p=1981#comment-202314</guid>
		<description>you article just prompted ,me to backup my blog. thanks!</description>
		<content:encoded><![CDATA[<p>you article just prompted ,me to backup my blog. thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cary</title>
		<link>http://www.problogger.net/archives/2006/01/03/in-case-of-security-planning-for-blogging-disasters/comment-page-1/#comment-202196</link>
		<dc:creator>Cary</dc:creator>
		<pubDate>Tue, 03 Jan 2006 22:24:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.problogger.net/?p=1981#comment-202196</guid>
		<description>Great suggestions on testing your backups, but what would be an easy way to test them? I currently backup my WordPress blogs by backing up all the files on the server, and the DB is e-mailed to me each night via the WP Backup plugin...

Is there a simple way for the not-so-database-literate to test that their DBs are good?</description>
		<content:encoded><![CDATA[<p>Great suggestions on testing your backups, but what would be an easy way to test them? I currently backup my WordPress blogs by backing up all the files on the server, and the DB is e-mailed to me each night via the WP Backup plugin&#8230;</p>
<p>Is there a simple way for the not-so-database-literate to test that their DBs are good?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave</title>
		<link>http://www.problogger.net/archives/2006/01/03/in-case-of-security-planning-for-blogging-disasters/comment-page-1/#comment-202108</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Tue, 03 Jan 2006 19:09:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.problogger.net/?p=1981#comment-202108</guid>
		<description>I used to work in the tech support department for a software company (now long gone) that made what was, at the time, the premium backup utlity. You can&#039;t imagine how many tech support calls that I fielded from folks that were backing up religiously but had never tested their backups! The comment earlier about testing your restore process is absolutely just as important as running the backup process.

I&#039;m paranoid. :-) I back up source code only after changes. There&#039;s no point in wasting bandwidth on backing up something that has not changed. But I back up every database on my server (via a cron job run by &quot;root&quot;) every night. Later that night I have my home server (gotta love linux) ftp to my production server and download the resulting backup files. These files are copied to a RAID device. It&#039;s only a mirror, but it still has two hard-drives instead of just one.

At any given point in time my most recent database backup is on the server. In the event of a data corruption event on the server, I can restore with at most a 23 hour 59 minute &quot;lost data&quot; window. If the server craters, I can upload the most recent source code / restore the most recent database and be up and running in about twenty minutes. I know this, because I&#039;ve tested it.

Test your backups. In a few months, test them again. It&#039;s like your smoke detector; it doesn&#039;t do you any good if it doesn&#039;t work.</description>
		<content:encoded><![CDATA[<p>I used to work in the tech support department for a software company (now long gone) that made what was, at the time, the premium backup utlity. You can&#8217;t imagine how many tech support calls that I fielded from folks that were backing up religiously but had never tested their backups! The comment earlier about testing your restore process is absolutely just as important as running the backup process.</p>
<p>I&#8217;m paranoid. :-) I back up source code only after changes. There&#8217;s no point in wasting bandwidth on backing up something that has not changed. But I back up every database on my server (via a cron job run by &#8220;root&#8221;) every night. Later that night I have my home server (gotta love linux) ftp to my production server and download the resulting backup files. These files are copied to a RAID device. It&#8217;s only a mirror, but it still has two hard-drives instead of just one.</p>
<p>At any given point in time my most recent database backup is on the server. In the event of a data corruption event on the server, I can restore with at most a 23 hour 59 minute &#8220;lost data&#8221; window. If the server craters, I can upload the most recent source code / restore the most recent database and be up and running in about twenty minutes. I know this, because I&#8217;ve tested it.</p>
<p>Test your backups. In a few months, test them again. It&#8217;s like your smoke detector; it doesn&#8217;t do you any good if it doesn&#8217;t work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: herb</title>
		<link>http://www.problogger.net/archives/2006/01/03/in-case-of-security-planning-for-blogging-disasters/comment-page-1/#comment-201598</link>
		<dc:creator>herb</dc:creator>
		<pubDate>Tue, 03 Jan 2006 10:29:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.problogger.net/?p=1981#comment-201598</guid>
		<description>I have now rendered the list harmless to viewers. This list was found by using MSN search engine. I was &#039;backtracking&#039; some of my stuff when I came accross this. I felt that there are many people and sites that want to correct the problem (s) created by this person. So I posted the list. It now has inserted into it a 3 digit number in each of the URL &#039;s to prevent them from activation. Please do not remove the numbers unless you can with the &quot;bugs&quot; created. The list is at http://www.robertbenjamin.com/hackedlist/hacked.htm</description>
		<content:encoded><![CDATA[<p>I have now rendered the list harmless to viewers. This list was found by using MSN search engine. I was &#8216;backtracking&#8217; some of my stuff when I came accross this. I felt that there are many people and sites that want to correct the problem (s) created by this person. So I posted the list. It now has inserted into it a 3 digit number in each of the URL &#8217;s to prevent them from activation. Please do not remove the numbers unless you can with the &#8220;bugs&#8221; created. The list is at <a href="http://www.robertbenjamin.com/hackedlist/hacked.htm" rel="nofollow">http://www.robertbenjamin.com/hackedlist/hacked.htm</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: herb</title>
		<link>http://www.problogger.net/archives/2006/01/03/in-case-of-security-planning-for-blogging-disasters/comment-page-1/#comment-201500</link>
		<dc:creator>herb</dc:creator>
		<pubDate>Tue, 03 Jan 2006 07:06:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.problogger.net/?p=1981#comment-201500</guid>
		<description>I better make it clearer ... the page I posted the list on is ok... just not the url&#039;s in the list...</description>
		<content:encoded><![CDATA[<p>I better make it clearer &#8230; the page I posted the list on is ok&#8230; just not the url&#8217;s in the list&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: herb</title>
		<link>http://www.problogger.net/archives/2006/01/03/in-case-of-security-planning-for-blogging-disasters/comment-page-1/#comment-201493</link>
		<dc:creator>herb</dc:creator>
		<pubDate>Tue, 03 Jan 2006 06:59:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.problogger.net/?p=1981#comment-201493</guid>
		<description>I just found a list of sites that were hacked ...posted it at ...
http://www.robertbenjamin.com/hackedlist/hacked.htm
I DO NOT advise going to any of the sites listed</description>
		<content:encoded><![CDATA[<p>I just found a list of sites that were hacked &#8230;posted it at &#8230;<br />
<a href="http://www.robertbenjamin.com/hackedlist/hacked.htm" rel="nofollow">http://www.robertbenjamin.com/hackedlist/hacked.htm</a><br />
I DO NOT advise going to any of the sites listed</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Mount</title>
		<link>http://www.problogger.net/archives/2006/01/03/in-case-of-security-planning-for-blogging-disasters/comment-page-1/#comment-201216</link>
		<dc:creator>Peter Mount</dc:creator>
		<pubDate>Tue, 03 Jan 2006 01:52:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.problogger.net/?p=1981#comment-201216</guid>
		<description>With protecting your files on the hard drive it&#039;s a good idea to keep them in a seperate partition from the Operating System. With Windows we were taught to create a seperate partition on the hard drive specifically for the data files. That way it is easier to back up the files, plus if Windows gets corrupted and needs re-installing the data files don&#039;t get lost because they are in that seperate partition.

One good tool to have is a copy of Knoppix Linux on CD ROM. This is available for free download at: 

http://www.knoppix.com/

Knoppix is a distrobution of Linux that can be booted from the CD Drive (as long as your computer is set up to allow this in the BIOS). If the Windows Operating System crashes you have the option of booting up Knoppix from the CD Drive and then be able to copy your files to an external device like a usb drive.

Have fun</description>
		<content:encoded><![CDATA[<p>With protecting your files on the hard drive it&#8217;s a good idea to keep them in a seperate partition from the Operating System. With Windows we were taught to create a seperate partition on the hard drive specifically for the data files. That way it is easier to back up the files, plus if Windows gets corrupted and needs re-installing the data files don&#8217;t get lost because they are in that seperate partition.</p>
<p>One good tool to have is a copy of Knoppix Linux on CD ROM. This is available for free download at: </p>
<p><a href="http://www.knoppix.com/" rel="nofollow">http://www.knoppix.com/</a></p>
<p>Knoppix is a distrobution of Linux that can be booted from the CD Drive (as long as your computer is set up to allow this in the BIOS). If the Windows Operating System crashes you have the option of booting up Knoppix from the CD Drive and then be able to copy your files to an external device like a usb drive.</p>
<p>Have fun</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: wb42</title>
		<link>http://www.problogger.net/archives/2006/01/03/in-case-of-security-planning-for-blogging-disasters/comment-page-1/#comment-200814</link>
		<dc:creator>wb42</dc:creator>
		<pubDate>Mon, 02 Jan 2006 22:01:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.problogger.net/?p=1981#comment-200814</guid>
		<description>A couple of thoughts about bloglines - I use it for its interface with the Elicit blogging software.  I make a quick run through bloglines, saving only the posts I think I&#039;ll want to incorporate into my blog.  Elicit has what they call a &quot;docklet&quot; that snags all the saved posts from bloglines.  Then, you just highlight the portion you want, and drag it from the docklet into the edit window.  Actually pretty slick.  Elicit has similar docklets for Amazon, Chitika, Yahoo, Google, Technorati, etc. Using it that way, bloglines serves me well, although I do have FeedBurner still around for those times bloglines takes a dive.
Doug</description>
		<content:encoded><![CDATA[<p>A couple of thoughts about bloglines &#8211; I use it for its interface with the Elicit blogging software.  I make a quick run through bloglines, saving only the posts I think I&#8217;ll want to incorporate into my blog.  Elicit has what they call a &#8220;docklet&#8221; that snags all the saved posts from bloglines.  Then, you just highlight the portion you want, and drag it from the docklet into the edit window.  Actually pretty slick.  Elicit has similar docklets for Amazon, Chitika, Yahoo, Google, Technorati, etc. Using it that way, bloglines serves me well, although I do have FeedBurner still around for those times bloglines takes a dive.<br />
Doug</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ray</title>
		<link>http://www.problogger.net/archives/2006/01/03/in-case-of-security-planning-for-blogging-disasters/comment-page-1/#comment-200800</link>
		<dc:creator>Ray</dc:creator>
		<pubDate>Mon, 02 Jan 2006 21:33:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.problogger.net/?p=1981#comment-200800</guid>
		<description>Jon, have you read the first paragraph and seen what&#039;s going on here at ProBlogger the past week? Darren didn&#039;t write this.</description>
		<content:encoded><![CDATA[<p>Jon, have you read the first paragraph and seen what&#8217;s going on here at ProBlogger the past week? Darren didn&#8217;t write this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Hampton</title>
		<link>http://www.problogger.net/archives/2006/01/03/in-case-of-security-planning-for-blogging-disasters/comment-page-1/#comment-200798</link>
		<dc:creator>Michael Hampton</dc:creator>
		<pubDate>Mon, 02 Jan 2006 21:32:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.problogger.net/?p=1981#comment-200798</guid>
		<description>I don&#039;t use bloglines if I can avoid it. I prefer to have my feeds close at hand on my computer, and I&#039;m VERY picky about how my feedreader works. With hundreds or even thousands of entries to look through in any given day, I have to have something that lets me work with them fast, and web-based feedreaders, by and large, do not.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t use bloglines if I can avoid it. I prefer to have my feeds close at hand on my computer, and I&#8217;m VERY picky about how my feedreader works. With hundreds or even thousands of entries to look through in any given day, I have to have something that lets me work with them fast, and web-based feedreaders, by and large, do not.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jon</title>
		<link>http://www.problogger.net/archives/2006/01/03/in-case-of-security-planning-for-blogging-disasters/comment-page-1/#comment-200791</link>
		<dc:creator>jon</dc:creator>
		<pubDate>Mon, 02 Jan 2006 20:56:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.problogger.net/?p=1981#comment-200791</guid>
		<description>I thought you used bloglines for your feedreader?</description>
		<content:encoded><![CDATA[<p>I thought you used bloglines for your feedreader?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: IO ERROR</title>
		<link>http://www.problogger.net/archives/2006/01/03/in-case-of-security-planning-for-blogging-disasters/comment-page-1/#comment-200787</link>
		<dc:creator>IO ERROR</dc:creator>
		<pubDate>Mon, 02 Jan 2006 19:02:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.problogger.net/?p=1981#comment-200787</guid>
		<description>Automating backups is the only way to fly. I&#039;m considering making automated backups of all my files to my iPod (since it has more space!) whenever I plug it in to the computer.

But just as important (and usually quite neglected) is: restoring! If the worst happens, you have to be able to restore all your data quickly. Make sure your backups are valid and contain the data you intended them to, and that you know how to restore them in the event of a disaster. The backup is completely useless if, when the time comes to use it, you can&#039;t.</description>
		<content:encoded><![CDATA[<p>Automating backups is the only way to fly. I&#8217;m considering making automated backups of all my files to my iPod (since it has more space!) whenever I plug it in to the computer.</p>
<p>But just as important (and usually quite neglected) is: restoring! If the worst happens, you have to be able to restore all your data quickly. Make sure your backups are valid and contain the data you intended them to, and that you know how to restore them in the event of a disaster. The backup is completely useless if, when the time comes to use it, you can&#8217;t.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ingoal</title>
		<link>http://www.problogger.net/archives/2006/01/03/in-case-of-security-planning-for-blogging-disasters/comment-page-1/#comment-200781</link>
		<dc:creator>Ingoal</dc:creator>
		<pubDate>Mon, 02 Jan 2006 16:49:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.problogger.net/?p=1981#comment-200781</guid>
		<description>I guess everyone with a site who has ever encountered similiar stuff (db-server error, webhosting error, etc) can feel the pain and the potential devastating loss of critical data such as (web)content and email - whether it was caused by own faults (i.e. updates with broken files, accidently deleting stuff, etc) or by a system failure. Everyone who has encountered something  like that should have learned his lesson and I guess most people have - doing a backup or two. 

It&#039;s human nature though to forget about things (again) rather quickly and hence the only way to stay ahead on such a critical task IMO is automation (to a certain degree). I decided that this was and is the only practical solution for myself. After moving (most of) my content to my own dedicated server I wrote a little backup (shell) script which will do the following:

1. backup all homeshares including the document-roots and all subdirectories of all hosted websites
2. dump all databases
3. backup all mails (I use imap so this is especially critical as there are minimal to none local versions)
4. zip all files generated in 1.-3. encoded with syntax (name.Weekday.file-extension) and save them to the second hdd of the server AND a remote backup location (a special backup-server in another facility of my host)
5. (not automated) I manually copy one of the files (usually the friday&#039;s copy of any given week to a special &quot;old&quot; folder)..

This script is executed via cronjob every night, so I&#039;ve got a current backup which will be valid for one week for every day of the week and with 5. a file history of more than x weeks...

People not familiar with shell scripts (linux) can have a look at my &lt;a href=&quot;http://www.ingoal.info/archives/2005/12/28/postchristmas-update/&quot; rel=&quot;nofollow&quot;&gt;original post&lt;/a&gt; where I posted the source of my backup script.</description>
		<content:encoded><![CDATA[<p>I guess everyone with a site who has ever encountered similiar stuff (db-server error, webhosting error, etc) can feel the pain and the potential devastating loss of critical data such as (web)content and email &#8211; whether it was caused by own faults (i.e. updates with broken files, accidently deleting stuff, etc) or by a system failure. Everyone who has encountered something  like that should have learned his lesson and I guess most people have &#8211; doing a backup or two. </p>
<p>It&#8217;s human nature though to forget about things (again) rather quickly and hence the only way to stay ahead on such a critical task IMO is automation (to a certain degree). I decided that this was and is the only practical solution for myself. After moving (most of) my content to my own dedicated server I wrote a little backup (shell) script which will do the following:</p>
<p>1. backup all homeshares including the document-roots and all subdirectories of all hosted websites<br />
2. dump all databases<br />
3. backup all mails (I use imap so this is especially critical as there are minimal to none local versions)<br />
4. zip all files generated in 1.-3. encoded with syntax (name.Weekday.file-extension) and save them to the second hdd of the server AND a remote backup location (a special backup-server in another facility of my host)<br />
5. (not automated) I manually copy one of the files (usually the friday&#8217;s copy of any given week to a special &#8220;old&#8221; folder)..</p>
<p>This script is executed via cronjob every night, so I&#8217;ve got a current backup which will be valid for one week for every day of the week and with 5. a file history of more than x weeks&#8230;</p>
<p>People not familiar with shell scripts (linux) can have a look at my <a href="http://www.ingoal.info/archives/2005/12/28/postchristmas-update/" rel="nofollow">original post</a> where I posted the source of my backup script.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: A.H</title>
		<link>http://www.problogger.net/archives/2006/01/03/in-case-of-security-planning-for-blogging-disasters/comment-page-1/#comment-200691</link>
		<dc:creator>A.H</dc:creator>
		<pubDate>Mon, 02 Jan 2006 15:21:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.problogger.net/?p=1981#comment-200691</guid>
		<description>Very helpful and awareness-rising, even though i don&#039;t live in the U.S, i know my host&#039;s servers are there and they&#039;re not stable anyway, time to back up i guess =)



A.H</description>
		<content:encoded><![CDATA[<p>Very helpful and awareness-rising, even though i don&#8217;t live in the U.S, i know my host&#8217;s servers are there and they&#8217;re not stable anyway, time to back up i guess =)</p>
<p>A.H</p>
]]></content:encoded>
	</item>
</channel>
</rss>
