<?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: Backup Basics and Different types of backup</title>
	<atom:link href="http://www.debianadmin.com/backup-basics-and-different-types-of-backup.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.debianadmin.com/backup-basics-and-different-types-of-backup.html</link>
	<description>Debian/Ubuntu Linux System Administration Tutorials,Howtos,Tips</description>
	<lastBuildDate>Thu, 19 Nov 2009 13:24:32 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: AJ</title>
		<link>http://www.debianadmin.com/backup-basics-and-different-types-of-backup.html/comment-page-1#comment-2373</link>
		<dc:creator>AJ</dc:creator>
		<pubDate>Mon, 09 Feb 2009 01:37:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.debianadmin.com/backup-basics-and-different-types-of-backup.html#comment-2373</guid>
		<description>how much storage space will I need for a typical full backup?</description>
		<content:encoded><![CDATA[<p>how much storage space will I need for a typical full backup?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pepito</title>
		<link>http://www.debianadmin.com/backup-basics-and-different-types-of-backup.html/comment-page-1#comment-928</link>
		<dc:creator>Pepito</dc:creator>
		<pubDate>Fri, 20 Apr 2007 05:22:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.debianadmin.com/backup-basics-and-different-types-of-backup.html#comment-928</guid>
		<description>&quot;s. Check that you can restore the backup so that all these are preserved.&quot;

That is the only thing I know and why I expected to read. The same applies to almost everything in the article.</description>
		<content:encoded><![CDATA[<p>&#8220;s. Check that you can restore the backup so that all these are preserved.&#8221;</p>
<p>That is the only thing I know and why I expected to read. The same applies to almost everything in the article.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Larry</title>
		<link>http://www.debianadmin.com/backup-basics-and-different-types-of-backup.html/comment-page-1#comment-927</link>
		<dc:creator>Larry</dc:creator>
		<pubDate>Wed, 28 Mar 2007 01:08:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.debianadmin.com/backup-basics-and-different-types-of-backup.html#comment-927</guid>
		<description>(* I think those long options in Chris&#039; note above need double-hyphens *)

Some other commands available in Linux that may be of interest --
  partimage
  rdiff-backup
  copydir (in pkg &quot;mirrordir&quot;)

I still think that dump/restore (through a process pipe) is quite useful
for migrating (populating) a new/local filesystem.  Larry</description>
		<content:encoded><![CDATA[<p>(* I think those long options in Chris&#8217; note above need double-hyphens *)</p>
<p>Some other commands available in Linux that may be of interest &#8211;<br />
  partimage<br />
  rdiff-backup<br />
  copydir (in pkg &#8220;mirrordir&#8221;)</p>
<p>I still think that dump/restore (through a process pipe) is quite useful<br />
for migrating (populating) a new/local filesystem.  Larry</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://www.debianadmin.com/backup-basics-and-different-types-of-backup.html/comment-page-1#comment-926</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Fri, 23 Mar 2007 16:09:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.debianadmin.com/backup-basics-and-different-types-of-backup.html#comment-926</guid>
		<description>You can have the ease of restore of a full backup, with the speed and space efficiency of an incremental backup using rsync and hard links.

Lets say we are backing up everything from / to /backup/

This gives you a full backup in /backup/1: rsync --archive --delete --links --progress --stats --verbose --exclude /backup/ / /backup/1

Then if you run: cp -al /backup/1 /backup/2
You&#039;ll get a hardlinked copy of the full backup.

If you then run:
rsync --archive --delete --links --progress --stats --verbose --exclude /backup/ / /backup/2
Rsync will perform an incremental backup into 2, and only replace updated files.  Thus, in /backup/1 you have the original backup, in /backup/2 you have the updated backup, and common files arn&#039;t duplicated, so it&#039;s nice and space efficient.

To restore, simply copy the most recent backup folder.

Of course, you might want more meaningful folders than /backup/1 and /backup/2.  I use the date as the folder name myself.</description>
		<content:encoded><![CDATA[<p>You can have the ease of restore of a full backup, with the speed and space efficiency of an incremental backup using rsync and hard links.</p>
<p>Lets say we are backing up everything from / to /backup/</p>
<p>This gives you a full backup in /backup/1: rsync &#8211;archive &#8211;delete &#8211;links &#8211;progress &#8211;stats &#8211;verbose &#8211;exclude /backup/ / /backup/1</p>
<p>Then if you run: cp -al /backup/1 /backup/2<br />
You&#8217;ll get a hardlinked copy of the full backup.</p>
<p>If you then run:<br />
rsync &#8211;archive &#8211;delete &#8211;links &#8211;progress &#8211;stats &#8211;verbose &#8211;exclude /backup/ / /backup/2<br />
Rsync will perform an incremental backup into 2, and only replace updated files.  Thus, in /backup/1 you have the original backup, in /backup/2 you have the updated backup, and common files arn&#8217;t duplicated, so it&#8217;s nice and space efficient.</p>
<p>To restore, simply copy the most recent backup folder.</p>
<p>Of course, you might want more meaningful folders than /backup/1 and /backup/2.  I use the date as the folder name myself.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
