<?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: Always Backup Your Work</title>
	<atom:link href="http://www.emediastrategist.com/blog/always-backup-your-work/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.emediastrategist.com/blog/always-backup-your-work/</link>
	<description>Personal blog of Eric Shanfelt, Online Business Strategist</description>
	<lastBuildDate>Wed, 06 Jul 2011 13:57:16 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Nik</title>
		<link>http://www.emediastrategist.com/blog/always-backup-your-work/comment-page-1/#comment-44</link>
		<dc:creator>Nik</dc:creator>
		<pubDate>Thu, 08 Jun 2006 16:02:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.emediastrategist.com/blog/?p=12#comment-44</guid>
		<description>Eric, years ago, I added this command to my web host&#039;s crontab to run daily around 1:15 AM. (I try to avoid running stuff at midnight, since my host runs backups at that time):

mysqldump -u [username] -p [password] [databasename]  &#124; gzip  &gt; db.sql.gz

Just creates a full database dump as a gzipped file every day. Saved me a zillion times.

I eventually made this a bit fancier and did a backup each day of the week (numbered 0-7 so as to recycle the backup) and a monthly backup as well (for the times when things were broken more than a week). That&#039;s plenty of protection, provided you have the disk space to store it.</description>
		<content:encoded><![CDATA[<p>Eric, years ago, I added this command to my web host&#8217;s crontab to run daily around 1:15 AM. (I try to avoid running stuff at midnight, since my host runs backups at that time):</p>
<p>mysqldump -u [username] -p [password] [databasename]  | gzip  &gt; db.sql.gz</p>
<p>Just creates a full database dump as a gzipped file every day. Saved me a zillion times.</p>
<p>I eventually made this a bit fancier and did a backup each day of the week (numbered 0-7 so as to recycle the backup) and a monthly backup as well (for the times when things were broken more than a week). That&#8217;s plenty of protection, provided you have the disk space to store it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric</title>
		<link>http://www.emediastrategist.com/blog/always-backup-your-work/comment-page-1/#comment-14</link>
		<dc:creator>Eric</dc:creator>
		<pubDate>Mon, 15 May 2006 15:05:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.emediastrategist.com/blog/?p=12#comment-14</guid>
		<description>Hi Tony. Yes, I believe that was the case. WP dropped the entire database instead of just the tables. VB did warn me, but I thought they&#039;d only drop their tables, not the entire database. Just a minor clarification in their warning would have been enough to help me. Nonetheless, I should have known better to back up my site before installing a major piece of software. That was just stupid on my part and I&#039;ve certainly learned that lesson ... again.</description>
		<content:encoded><![CDATA[<p>Hi Tony. Yes, I believe that was the case. WP dropped the entire database instead of just the tables. VB did warn me, but I thought they&#8217;d only drop their tables, not the entire database. Just a minor clarification in their warning would have been enough to help me. Nonetheless, I should have known better to back up my site before installing a major piece of software. That was just stupid on my part and I&#8217;ve certainly learned that lesson &#8230; again.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tony Angelo</title>
		<link>http://www.emediastrategist.com/blog/always-backup-your-work/comment-page-1/#comment-12</link>
		<dc:creator>Tony Angelo</dc:creator>
		<pubDate>Fri, 12 May 2006 15:57:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.emediastrategist.com/blog/?p=12#comment-12</guid>
		<description>Eric, If your WordPress database was shared by your vBulletin database, but seperated with only prefixes, such as wp_ and vb_, the vBulletin install app may not have been able to differenciate between the two. Was that the case? If so, and if that is &lt;em&gt;still&lt;/em&gt; the case, you may want to consider seperating your MySQL databses for each application if your host allows. If that wasn&#039;t the case, you should really tell Jelsoft... even though they &lt;em&gt;did&lt;/em&gt; warn you.</description>
		<content:encoded><![CDATA[<p>Eric, If your WordPress database was shared by your vBulletin database, but seperated with only prefixes, such as wp_ and vb_, the vBulletin install app may not have been able to differenciate between the two. Was that the case? If so, and if that is <em>still</em> the case, you may want to consider seperating your MySQL databses for each application if your host allows. If that wasn&#8217;t the case, you should really tell Jelsoft&#8230; even though they <em>did</em> warn you.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

