<?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"
	>
<channel>
	<title>Comments on: When updating problems occur.</title>
	<atom:link href="http://blog.cmsmadesimple.org/2007/03/15/when-updating-problems-occur/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.cmsmadesimple.org/2007/03/15/when-updating-problems-occur/</link>
	<description>Bits From The CMSMS Community</description>
	<pubDate>Mon, 08 Sep 2008 01:09:26 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Bob</title>
		<link>http://blog.cmsmadesimple.org/2007/03/15/when-updating-problems-occur/#comment-526</link>
		<dc:creator>Bob</dc:creator>
		<pubDate>Sat, 21 Apr 2007 02:40:19 +0000</pubDate>
		<guid isPermaLink="false">http://blog.cmsmadesimple.org/2007/03/15/when-updating-problems-occur/#comment-526</guid>
		<description>SO what are the best steps in regards to backups? 

I'm assuming doing a regular MySQL dump (which is pretty easy on control panels supplied by my hosts) is the best thing to do first.
What about backups of all the files from the server (like using an FTP Client and copying all the files locally)... is that necessary/overkill or good practice? 

I plan on using CMSMS for all my clients and employer because it is a great CMS, and I think easy to use and teach others (editors for instance) to use, but I just want to be sure the best way to keep the sites up and running and properly backed up.</description>
		<content:encoded><![CDATA[<p>SO what are the best steps in regards to backups? </p>
<p>I&#8217;m assuming doing a regular MySQL dump (which is pretty easy on control panels supplied by my hosts) is the best thing to do first.<br />
What about backups of all the files from the server (like using an FTP Client and copying all the files locally)&#8230; is that necessary/overkill or good practice? </p>
<p>I plan on using CMSMS for all my clients and employer because it is a great CMS, and I think easy to use and teach others (editors for instance) to use, but I just want to be sure the best way to keep the sites up and running and properly backed up.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stefan</title>
		<link>http://blog.cmsmadesimple.org/2007/03/15/when-updating-problems-occur/#comment-436</link>
		<dc:creator>Stefan</dc:creator>
		<pubDate>Fri, 06 Apr 2007 18:36:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.cmsmadesimple.org/2007/03/15/when-updating-problems-occur/#comment-436</guid>
		<description>A wonderful tool for making database backups is MySQLDumper. It even can backup (and of course restore) large databases if you have a 30 second time limit for scripts like on most shared servers. It just splits the dumpfile automatically into parts. Many people have problems with PhpMyAdmin to restore databases containing special characters like German umlauts. They will often find an "?" instead of the character after restoring the database. MySQLDumper prevents this by checking wich coding is running on the MySQL-server, e.g. latin1 etc.! It also allows automated backups through cronjob, send dumpfiles via FTP to another server or by email and much more.
I use this tool since years and it's by far the most useful backup scripts I know. 
It's freeware and Open Source, you can find it here: 
http://www.mysqldumper.de/en/</description>
		<content:encoded><![CDATA[<p>A wonderful tool for making database backups is MySQLDumper. It even can backup (and of course restore) large databases if you have a 30 second time limit for scripts like on most shared servers. It just splits the dumpfile automatically into parts. Many people have problems with PhpMyAdmin to restore databases containing special characters like German umlauts. They will often find an &#8220;?&#8221; instead of the character after restoring the database. MySQLDumper prevents this by checking wich coding is running on the MySQL-server, e.g. latin1 etc.! It also allows automated backups through cronjob, send dumpfiles via FTP to another server or by email and much more.<br />
I use this tool since years and it&#8217;s by far the most useful backup scripts I know.<br />
It&#8217;s freeware and Open Source, you can find it here:<br />
<a href="http://www.mysqldumper.de/en/" rel="nofollow">http://www.mysqldumper.de/en/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vin</title>
		<link>http://blog.cmsmadesimple.org/2007/03/15/when-updating-problems-occur/#comment-343</link>
		<dc:creator>Vin</dc:creator>
		<pubDate>Sun, 25 Mar 2007 17:50:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.cmsmadesimple.org/2007/03/15/when-updating-problems-occur/#comment-343</guid>
		<description>There are some backup modules in the forge - http://dev.cmsmadesimple.org/softwaremap/trove_list.php?form_cat=324</description>
		<content:encoded><![CDATA[<p>There are some backup modules in the forge - <a href="http://dev.cmsmadesimple.org/softwaremap/trove_list.php?form_cat=324" rel="nofollow">http://dev.cmsmadesimple.org/softwaremap/trove_list.php?form_cat=324</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dhtml12345</title>
		<link>http://blog.cmsmadesimple.org/2007/03/15/when-updating-problems-occur/#comment-252</link>
		<dc:creator>dhtml12345</dc:creator>
		<pubDate>Thu, 15 Mar 2007 19:33:43 +0000</pubDate>
		<guid isPermaLink="false">http://blog.cmsmadesimple.org/2007/03/15/when-updating-problems-occur/#comment-252</guid>
		<description>I'm always afraid to update.

I would like to see a comprehensive backup system integrated into CMSMS.  phpmyadmin is very difficult to use and it's hard to be sure that the backup settings are correct.</description>
		<content:encoded><![CDATA[<p>I&#8217;m always afraid to update.</p>
<p>I would like to see a comprehensive backup system integrated into CMSMS.  phpmyadmin is very difficult to use and it&#8217;s hard to be sure that the backup settings are correct.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
