<?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: cPanel Automated Backups</title>
	<atom:link href="http://blog.patspam.com/2008/cpanel-automated-backups/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.patspam.com/2008/cpanel-automated-backups</link>
	<description>patspampatspampatspampatspam</description>
	<pubDate>Tue, 02 Dec 2008 06:42:28 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Patrick</title>
		<link>http://blog.patspam.com/2008/cpanel-automated-backups#comment-356</link>
		<dc:creator>Patrick</dc:creator>
		<pubDate>Tue, 18 Mar 2008 23:27:58 +0000</pubDate>
		<guid isPermaLink="false">http://blog.patspam.com/2008/03/18/cpanel-automated-backups/#comment-356</guid>
		<description>Yikes! 9GB compressed? I guess a lot of that is 230+ duplicate copies of the Joomla install? I'm not familiar with Joomla but does it have some sort of "user uploads" or "user data" directory that you could focus on backing up instead? On some CMS' you can run multiple sites off a single codebase (which makes updates easier for a start) - looks like Joomla doesn't support that yet (http://forum.joomla.org/viewtopic.php?f=428&#038;t=199298&#038;st=0&#038;sk=t&#038;sd=a&#038;sid=32d602120d27cae9b33d743db74b4b28) but hopefully one day it will to make your life easier (and your cPanel backups smaller).

Have you thought about setting up a cron job to take care of the daily tarring/rotating of the sql files?

Patrick</description>
		<content:encoded><![CDATA[<p>Yikes! 9GB compressed? I guess a lot of that is 230+ duplicate copies of the Joomla install? I&#8217;m not familiar with Joomla but does it have some sort of &#8220;user uploads&#8221; or &#8220;user data&#8221; directory that you could focus on backing up instead? On some CMS&#8217; you can run multiple sites off a single codebase (which makes updates easier for a start) - looks like Joomla doesn&#8217;t support that yet (http://forum.joomla.org/viewtopic.php?f=428&#038;t=199298&#038;st=0&#038;sk=t&#038;sd=a&#038;sid=32d602120d27cae9b33d743db74b4b28) but hopefully one day it will to make your life easier (and your cPanel backups smaller).</p>
<p>Have you thought about setting up a cron job to take care of the daily tarring/rotating of the sql files?</p>
<p>Patrick</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: damon</title>
		<link>http://blog.patspam.com/2008/cpanel-automated-backups#comment-355</link>
		<dc:creator>damon</dc:creator>
		<pubDate>Tue, 18 Mar 2008 22:33:49 +0000</pubDate>
		<guid isPermaLink="false">http://blog.patspam.com/2008/03/18/cpanel-automated-backups/#comment-355</guid>
		<description>Pat, this is a very timely post.

I am going through a similar quandry here at work. We have a dedicated server that we host all our websites on. Before my involvement in this project, the main account on the server was set up with 230+ subdomains, all with their own Joomla install, but all running off the one SQL database. How efficient do you reckon a 14,000+ table SQL database is?! but that's another story.

So, back to the backups. The cPanel backup that runs every night, creates a daily/weekly/monthly set of all accounts, public_html, sql etc, but the daily set is replaced the very next day. That wasn't acceptable to me, because you could easily need to restore back more than one day, but less than one week. So I was SSHing to the server with PuTTY to tar the sql folder every morning. At least this would allow for a data/sql restoration even if we needed to find the public_html stuff from another source. The reason I don't archive the full daily cPanel backup? - it's 9GB Big!

Now I need to spend time to split all those sub domains into their own accounts, with their own database just to make things more manageable. Joy.</description>
		<content:encoded><![CDATA[<p>Pat, this is a very timely post.</p>
<p>I am going through a similar quandry here at work. We have a dedicated server that we host all our websites on. Before my involvement in this project, the main account on the server was set up with 230+ subdomains, all with their own Joomla install, but all running off the one SQL database. How efficient do you reckon a 14,000+ table SQL database is?! but that&#8217;s another story.</p>
<p>So, back to the backups. The cPanel backup that runs every night, creates a daily/weekly/monthly set of all accounts, public_html, sql etc, but the daily set is replaced the very next day. That wasn&#8217;t acceptable to me, because you could easily need to restore back more than one day, but less than one week. So I was SSHing to the server with PuTTY to tar the sql folder every morning. At least this would allow for a data/sql restoration even if we needed to find the public_html stuff from another source. The reason I don&#8217;t archive the full daily cPanel backup? - it&#8217;s 9GB Big!</p>
<p>Now I need to spend time to split all those sub domains into their own accounts, with their own database just to make things more manageable. Joy.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
